From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 19438@debbugs.gnu.org, Leo Liu <sdl.web@gmail.com>
Subject: bug#19438: 24.4; system-name bad cache
Date: Sat, 27 Dec 2014 10:13:43 -0500 [thread overview]
Message-ID: <jwviogxi16l.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <549DDE50.7020402@cs.ucla.edu> (Paul Eggert's message of "Fri, 26 Dec 2014 14:16:48 -0800")
>> Why not get rid of the variable system-name? It seems what it provides
>> can be easily achieved without it.
> It's documented so we shouldn't just remove it; we'd need to mark it
> as obsolescent.
> Its documented behavior is "you can set the variable @code{system-name} in
> case Emacs is confused about the name of your system". I've never found
> this feature to be useful, though I understand it was useful for others long
> ago. Perhaps some people still find it useful? Anyway, if there's
> consensus to mark the variable as obsolescent I can prepare a patch along
> those lines.
Maybe we could mark it obsolete, tho I'm not completely sure what
replaces it. Random thoughts:
- "it" is unclear, since currently the var and the function are just identical.
- this not-very-useful functionality occasionally causes 30s wait at
startup time, so it would be good to get rid of the DNS lookup.
Maybe we could make the system-name function return the same as
`hostname` (and do it dynamically).
> How about the attached patch? The idea is that (system-name) actually
> inquires for the current system name, and system-name caches the result.
> If an Emacs lisp program assigns to system-name, though, it's no longer
> updated thereafter.
Sounds OK.
Stefan
next prev parent reply other threads:[~2014-12-27 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 10:21 bug#19438: 24.4; system-name bad cache Leo Liu
2014-12-26 3:57 ` Stefan Monnier
2014-12-26 16:07 ` Paul Eggert
2014-12-26 22:10 ` Leo Liu
2014-12-26 22:16 ` Paul Eggert
2014-12-27 15:13 ` Stefan Monnier [this message]
2014-12-27 23:30 ` Leo Liu
2014-12-28 1:11 ` Stefan Monnier
2014-12-28 2:03 ` Leo Liu
2014-12-29 20:47 ` Paul Eggert
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=jwviogxi16l.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19438@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=sdl.web@gmail.com \
/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).