From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: dann@ics.uci.edu, andreas.amann@web.de, emacs-devel@gnu.org
Subject: Re: 23.0.60; emacsclient -t not working within "less"
Date: Fri, 19 Sep 2008 19:30:49 +0300 [thread overview]
Message-ID: <u3ajwqerq.fsf@gnu.org> (raw)
In-Reply-To: <87bpykkuc2.fsf@cyd.mit.edu>
> From: Chong Yidong <cyd@stupidchicken.com>
> Date: Fri, 19 Sep 2008 11:51:09 -0400
> Cc: 427-done@emacsbugs.donarmstrong.com, Andreas Amann <andreas.amann@web.de>,
> emacs-devel@gnu.org
>
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> > You can edebug `server-process-filter'. Doing that shows quickly the
> > problem: emacsclient passes the tty as: -tty /dev/tty.
> > /dev/tty means one thing for emacsclient and another one for emacs...
> >
> > emacsclient.c computes the tty like this:
> >
> > tty_name = ttyname (fileno (stdin));
> >
> > changing it to:
> >
> > tty_name = ttyname (fileno (stdout));
> >
> > gets the right terminal and this problem seems to be fixed.
>
> That seems to work fine for me too. I checked in the fix. Thanks.
Yes, but is this the right fix? The `tty' command prints "/dev/tty"
as well in the situation described by the original bug report. Why
doesn't Emacs DTRT with that name? Can it fail in a similar way with
the name of the device connected to stdout?
next prev parent reply other threads:[~2008-09-19 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 18:36 23.0.60; emacsclient -t not working within "less" Chong Yidong
2008-09-19 6:28 ` Dan Nicolaescu
2008-09-19 15:51 ` Chong Yidong
2008-06-16 10:32 ` bug#427: " Andreas Amann
2008-09-19 16:00 ` bug#427: marked as done (23.0.60; emacsclient -t not working within "less") Emacs bug Tracking System
2008-09-19 16:30 ` Eli Zaretskii [this message]
2008-09-19 6:28 ` bug#427: 23.0.60; emacsclient -t not working within "less" Dan Nicolaescu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u3ajwqerq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andreas.amann@web.de \
--cc=cyd@stupidchicken.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.