all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 24218@debbugs.gnu.org, matthew@mattleach.net, lomov.vl@gmail.com
Subject: bug#24218: 25.1.50; server-name, server-socket-dir and daemon start through, systemd socket
Date: Mon, 08 Jan 2018 21:14:53 +0200	[thread overview]
Message-ID: <83mv1o6u36.fsf@gnu.org> (raw)
In-Reply-To: <3750e2ed-122d-759c-660f-8be3d777809f@cs.ucla.edu> (message from Paul Eggert on Mon, 8 Jan 2018 10:42:28 -0800)

> Cc: matthew@mattleach.net, 24218@debbugs.gnu.org, lomov.vl@gmail.com
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 8 Jan 2018 10:42:28 -0800
> 
> On 01/08/2018 10:33 AM, Eli Zaretskii wrote:
> > this
> > variable's purpose is inconsistent with its being for internal use
> > only.
> 
> What purpose do you see for the variable, other than its use in Emacs's 
> own Lisp code?

How many seconds do you think it will take Emacs hackers (in the good
meaning of the word) to discover this variable and start (ab)using it?





  reply	other threads:[~2018-01-08 19:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13 16:35 bug#24218: 25.1.50; server-name, server-socket-dir and daemon start through systemd socket Vladimir Lomov
2016-08-15  2:25 ` Paul Eggert
2018-01-07 21:55 ` bug#24218: 25.1.50; server-name, server-socket-dir and daemon start through, " Paul Eggert
2018-01-08  3:50   ` Eli Zaretskii
2018-01-08  4:24     ` Paul Eggert
2018-01-08 18:33       ` Eli Zaretskii
2018-01-08 18:42         ` Paul Eggert
2018-01-08 19:14           ` Eli Zaretskii [this message]
2018-01-08 19:23             ` Paul Eggert
2018-01-09 19:53     ` Matthew Leach
2018-01-24 23:00       ` Paul Eggert
2018-01-25 19:34         ` Matthew Leach
2018-02-10 16:07           ` Paul Eggert
2018-02-12 14:24             ` Matthew Leach
2018-02-12 20:58               ` 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

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

  git send-email \
    --in-reply-to=83mv1o6u36.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24218@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=lomov.vl@gmail.com \
    --cc=matthew@mattleach.net \
    /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.