From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org, bug-gnu-emacs@gnu.org,
ueno@unixuser.org, 1688@emacsbugs.donarmstrong.com
Subject: bug#1688: 23.0.60; ttname returned by system-process-attributes points to nonexisting file
Date: Mon, 12 Jan 2009 16:04:50 -0500 [thread overview]
Message-ID: <jwvskno1bmb.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <u7i50coxg.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Jan 2009 21:19:39 +0200")
>> --- sysdep.c.~1.328.~ 2009-01-03 07:04:59.000000000 -0800
>> +++ sysdep.c 2009-01-13 01:09:56.000000000 -0800
>> @@ -3322,7 +3322,7 @@
>>
>> if (MINOR (rdev) >= minor_beg && MINOR (rdev) <= minor_end)
>> {
>> - sprintf (name + strlen (name), "%lu", MINOR (rdev));
>> + sprintf (name + strlen (name), "/%lu", MINOR (rdev));
>> break;
>> }
> It's not that simple: what happens if `name' is something like "ptys"
> or "tty"? We need to generate "ptys2" and "tty39" for them, not
> "ptys/2" and "tty/39".
Indeed, it's pretty messy. Even just procfs_ttyname in itself is pretty
messy (not its implementation, but the need to go through those hoops).
> Faced with this difficulty, I decided not to bother, since the value
> of `ttname' is not documented to return a valid file name.
> Perhaps some Linux guru (which I ain't) can suggest an easy solution.
I think it's OK for now. When we really need something better, we'll
just look at the `ps' code.
Stefan
next prev parent reply other threads:[~2009-01-12 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 6:28 bug#1688: 23.0.60; ttname returned by system-process-attributes points to nonexisting file Daiki Ueno
2009-01-12 17:17 ` richardeng
2009-01-12 19:19 ` Eli Zaretskii
2009-01-12 21:04 ` Stefan Monnier [this message]
2009-01-16 10:22 ` richardeng
2009-01-16 21:00 ` Stefan Monnier
2009-01-17 11:51 ` richardeng
2009-01-18 20:57 ` Stefan Monnier
2011-07-10 14:36 ` Lars Magne Ingebrigtsen
2009-01-12 18:00 ` richardeng
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=jwvskno1bmb.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1688@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=ueno@unixuser.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.