unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Choi <akochoi@shaw.ca>
Subject: Re: Prompt display in Panther build
Date: Fri, 31 Oct 2003 09:46:18 -0700	[thread overview]
Message-ID: <m2r80tbbj9.fsf@owlbear.local> (raw)
In-Reply-To: <m31xstzj4o.fsf@seneca.benny.turtle-trading.net>

Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de> writes:

>> When I run 'sql-postgres' to start the interactive SQL mode (to
>> connect to a local pgsql server) the behavior differs between the
>> command line invocation and the Carbon build. In particular, on the
>> command line, everything is (or seems) as it is supposed to be; on
>> the Carbon build, there is no prompt. If I enter commands (despite
>> the lack of prompt) everything behaves normally (it transforms the
>> text to boldface and writes the query results, as usual), but I
>> still don't get any prompt showing up.
>
> There are (or at least there used to be) problems with pseudo-ttys
> (ptys) on Mac OS X, therefore ptys are disabled for some (all?)
> operations.  I think the variable process-connection-type controls
> this, so you could try to tweak that.

I believe the pty problem has been fixed in Panther/Darwin 7.0 (unless
someone can tell me otherwise).

If behavior differs in terminal and GUI mode, perhaps it is useful to
check environment variable settings passed to `psql' that are different
in the two cases (value of process-environment).  Also you may want to
check what arguments are used when psql is called (by stopping at
start-process (?)) in both cases.

  reply	other threads:[~2003-10-31 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 16:17 Prompt display in Panther build Matt Tenenbaum
2003-10-31 12:28 ` Benjamin Riefenstahl
2003-10-31 16:46   ` Andrew Choi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-31 18:17 Michael Mauger
2003-11-01 21:09 Michael Mauger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2r80tbbj9.fsf@owlbear.local \
    --to=akochoi@shaw.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).