From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Dan Nicolaescu" <dann@ics.uci.edu>
Cc: Ulrich Mueller <ulm@gentoo.org>,
emacs-devel@gnu.org, Nick Roberts <nickrob@snap.net.nz>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: bug in server-start
Date: Tue, 16 Dec 2008 20:46:42 +0100 [thread overview]
Message-ID: <f7ccd24b0812161146t6241eab4v8ffd4d711ea2cd1b@mail.gmail.com> (raw)
In-Reply-To: <200812161928.mBGJSQo1004840@mothra.ics.uci.edu>
On Tue, Dec 16, 2008 at 20:28, Dan Nicolaescu <dann@ics.uci.edu> wrote:
> Then PLEASE STOP making statements about what I said when that is
> clearly not true.
Then PLEASE STOP trying to turn this discussion into another confrontation.
> (display-warning 'server (format "Server %S is already running" server-name))
>
> Given that the 23.1 behavior is different than what happened before,
> this will not help users easily find out what is wrong.
What will help the users find out what is wrong? Not giving them a warning?
> PLEASE STOP making statements here about what I do or do not, when you
> have no information to support your suppositions. Thank you.
PLEASE STOP using that tone, and PLEASE LOOK for "perhaps" in a dictionary.
> There's a strong hint in the fact that server-name is a defvar with no
> docstring (not a defcustom).
Nonsense. The manual clearly says that you can run several servers
provided that you use different names, and before --daemon (and even
now, on Windows) there's no user command to set the server-name. If
anything, perhaps it should be a defcustom, or at the very least have
a docstring.
> I designed --daemon to be very easy to use, I want the error messages to
> be easy to understand/debug too.
And the difference between
Could not start daemon
and
Could not start daemon "server"
(or, 'Could not start daemon named "server"')
makes the error messages difficult to understand/debug? How so?
Juanma
next prev parent reply other threads:[~2008-12-16 19:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 9:00 bug in server-start Nick Roberts
2008-12-15 10:29 ` Juanma Barranquero
2008-12-15 10:50 ` Sven Joachim
2008-12-15 11:03 ` Juanma Barranquero
2008-12-15 11:04 ` Nick Roberts
2008-12-15 11:10 ` Juanma Barranquero
2008-12-15 11:26 ` Juanma Barranquero
2008-12-15 11:59 ` Juanma Barranquero
2008-12-15 15:25 ` Stefan Monnier
2008-12-15 17:24 ` Dan Nicolaescu
2008-12-15 18:27 ` Juanma Barranquero
2008-12-15 19:16 ` Romain Francoise
2008-12-15 20:00 ` Dan Nicolaescu
2008-12-16 7:03 ` Ulrich Mueller
2008-12-16 9:38 ` Juanma Barranquero
2008-12-16 11:49 ` Ulrich Mueller
2008-12-16 12:15 ` Juanma Barranquero
2008-12-16 13:43 ` Ulrich Mueller
2008-12-16 15:40 ` Stefan Monnier
2008-12-16 16:01 ` Ulrich Mueller
2008-12-16 16:01 ` Dan Nicolaescu
2008-12-16 16:07 ` Juanma Barranquero
2008-12-16 16:15 ` Dan Nicolaescu
2008-12-16 16:20 ` Juanma Barranquero
2008-12-16 16:31 ` Dan Nicolaescu
2008-12-16 16:42 ` Juanma Barranquero
2008-12-16 17:00 ` Dan Nicolaescu
2008-12-16 18:28 ` Juanma Barranquero
2008-12-16 18:51 ` Dan Nicolaescu
2008-12-16 19:00 ` Juanma Barranquero
2008-12-16 19:28 ` Dan Nicolaescu
2008-12-16 19:46 ` Juanma Barranquero [this message]
2008-12-16 19:58 ` Dan Nicolaescu
2008-12-16 20:33 ` Juanma Barranquero
2008-12-16 20:59 ` Dan Nicolaescu
2008-12-16 21:05 ` Juanma Barranquero
2008-12-16 20:56 ` Chong Yidong
2008-12-16 21:12 ` Juanma Barranquero
2008-12-16 23:44 ` Stefan Monnier
2008-12-15 20:12 ` Stefan Monnier
2008-12-16 14:55 ` Dan Nicolaescu
2008-12-16 15:36 ` Stefan Monnier
2008-12-16 15:56 ` 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
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=f7ccd24b0812161146t6241eab4v8ffd4d711ea2cd1b@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nickrob@snap.net.nz \
--cc=ulm@gentoo.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).