unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: csant <csant@csant.info>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Device 0 is not a termcap terminal device
Date: Tue, 1 Sep 2009 22:27:54 +0000	[thread overview]
Message-ID: <20090901222754.GA5211@muc.de> (raw)
In-Reply-To: <m2ws4is65y.fsf@igel.home>

Good evening, Andreas!

On Tue, Sep 01, 2009 at 11:31:53PM +0200, Andreas Schwab wrote:
> Alan Mackenzie <acm@muc.de> writes:

> > The CC Mode test suite uses `send-string-to-terminal' in batch mode

> This is your problem.

Do you mean that `send-string-to-terminal' shouldn't have to work in
batch mode?

The documentation of the function in the Elisp manual for Emacs 22 just
said that the string is sent to "the terminal", which presumable means
stdout.  

In Emacs 23's Elisp, it says the string goes to "the selected frame's
terminal", which is clearly undefined in batch mode.

This change wasn't in the "incompatible changes" section of NEWS, so it
would appear to be a bug.

> Use princ instead.

This doesn't work.  In place of the smoothly updating line produced by
send-string-to-terminal, princ sputters, leaves the line partially
blank, updating fragments of it every few seconds.

princ is the wrong function - it's purpose is to convert lisp objects to
human reabable strings, so it'll be doing something wierd with the
control characters in the output strings, or buffering them
inappropriately, or whatever.

The strings being output are terminal specific, therefore they need an
"raw output to terminal" function, such as send-string-to-terminal.  I
think I was right.  :-)

> Andreas.

-- 
Alan Mackenzie (Nürnberg).




  reply	other threads:[~2009-09-01 22:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 17:55 Device 0 is not a termcap terminal device csant
2008-10-03 10:07 ` Alan Mackenzie
2008-10-03 16:14   ` Chong Yidong
2008-10-04 22:27     ` Alan Mackenzie
2009-02-04 22:45       ` moboyle79
2009-02-05  7:15         ` Dan Nicolaescu
2008-10-03 16:25   ` Dan Nicolaescu
2009-09-01 20:08     ` Alan Mackenzie
2009-09-01 21:31       ` Andreas Schwab
2009-09-01 22:27         ` Alan Mackenzie [this message]
2009-09-01 22:36           ` Andreas Schwab
2009-09-01 23:02             ` Alan Mackenzie
2009-09-02  9:14               ` Andreas Schwab
2009-09-02  9:57                 ` Alan Mackenzie
2009-09-02 10:11                   ` Andreas Schwab
2009-09-01 23:20       ` Stefan Monnier
2009-09-02  9:43         ` Alan Mackenzie
2009-09-02 17:48           ` Stefan Monnier
2009-09-11 20:36             ` Alan Mackenzie

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=20090901222754.GA5211@muc.de \
    --to=acm@muc.de \
    --cc=csant@csant.info \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.org \
    /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).