Re: BUG #11986: psql uses pager inside Emacs shell buffer (not a terminal)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ed Avis <eda(at)waniasset(dot)com>
Cc: "'bruce(at)momjian(dot)us'" <bruce(at)momjian(dot)us>, "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #11986: psql uses pager inside Emacs shell buffer (not a terminal)
Date: 2014-12-05 18:57:19
Message-ID: 20090.1417805839@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ed Avis <eda(at)waniasset(dot)com> writes:
>> Many shell scripts run from cron have a 'dumb' terminal value.

> And these scripts should output directly and not run a pager -- so matching what is being suggested for 'dumb'.

> In fact they already run without pager because their stdout is not a
> tty.

Right. It only matters when we think stdout is a tty.

> What is being discussed here is what psql should do when it is writing to a tty, so interactive in some sense, but with TERM=dumb. Decades ago that would have meant a teleprinter terminal (or, perhaps, some ancient serial terminal or Minix 1.0). Nowadays it means running inside emacs or some other management program, so there is no need to run a pager.

I am pretty hesitant about extending the emacs example to apply to *every*
context where TERM=dumb, especially given the complete lack of field
complaints in this area. I'm good with putting in a special hack for when
we're sure we're inside emacs, but I don't think an adequate case has been
made for assuming TERM=dumb means the opposite of what it appears to mean
on its face. Especially not if there won't be a way for the user to
override the choice.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ed Avis 2014-12-05 19:08:33 Re: BUG #11986: psql uses pager inside Emacs shell buffer (not a terminal)
Previous Message Ed Avis 2014-12-05 18:37:47 Re: BUG #11986: psql uses pager inside Emacs shell buffer (not a terminal)