pg_config isn't installed by default on many systems, and is usually
part of postgresql-libs-devel or some such, leading to needless
"pg_config not found" errors on completion.
The ~/.psqlrc may alter the output. In particular, I have '\timing on'
in there to add timings. This is useful when using psql, but not when
relying on it in scripts.
For example:
psql -Aqt -c "select n.nspname \
from pg_catalog.pg_namespace n \
where n.nspname "'!~'" '^pg_' \
and n.nspname <> 'information_schema' \
order by 1;" postgres 2>/dev/null
Gives the output:
public
Time: 1.882 ms
Whereas with -X it gives the standard output:
public
Having a vim modeline or emacs local variable line somewhere in the
middle of the file isn't really helpful. By default, vim will only
check the first and last 5 lines of a file for a modeline (assuming the
modeline option is enabled). Emacs is even more strict about the type
of local variable line that was in use, it will only check the first
line of the file or the second line if the first line specifies a script
interpreter (which isn't the case here).
Move the vim modeline to the end of the file so that it can actually be
found by vim but is out of the way for editing. For emacs more work is
required, convert that to the more verbose Local Variables syntax which
emacs will look for starting 3000 characters from the end of the file.
Also there is no zsh mode for emacs (according to
zsh-users/zsh-completions#75), use the "Shell-Script" mode instead.
This seems to automatically detect that the files are for zsh.
I'm not an emacs user, so I haven't tested that portion much. But, this
does at least improve the syntax highlighting there.
Shohei YOSHIDA
Martin Tournoij
Dimitris Apostolou
J Smith
Julien Nicoulaud
Stefano Zacchiroli
Felix Bünemann
Daniel Serodio
Aaron Schrab