Search Postgresql Archives

Re: Finding error in long input file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Finding error in long input file
From: Rich Shepard <rshepard@xxxxxxxxxxxxxxx>
Date: Wed, 10 Jul 2024 10:06:52 -0700 (PDT)
In-reply-to: <2FC694EE-8B33-4AC8-9CB6-29D4400A151A@gmail.com>
References: <2aeaece1-9533-638c-7b21-26c92f6d829b@appl-ecosys.com> <2FC694EE-8B33-4AC8-9CB6-29D4400A151A@gmail.com>

On Wed, 10 Jul 2024, Rob Sargent wrote:

I'm an emacs user too. Do you have show-paren enabled? This would show
that your file was ill-formed. M-p and M-n go previous/next matching
parentheses of all types.


Rob,

No, I haven't enabled show-paren.

Thanks for the tip,

Rich

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Re: Finding error in long input file
  - From: Rich Shepard

Prev by Date: Re: [EXTERNAL] Re: SSPI Feature Request
Next by Date: Re: can stored procedures with computational sql queries improve API performance?
Previous by thread: Re: Finding error in long input file
Next by thread: Re: Finding error in long input file
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux