From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 1298@emacsbugs.donarmstrong.com, Juanma Barranquero <lekktu@gmail.com>
Subject: bug#1298: allow 'emacsclient -a "emacs --daemon && emacsclient -c"'
Date: Thu, 11 Dec 2008 09:08:54 -0800 (PST) [thread overview]
Message-ID: <200812111708.mBBH8seW000410@mothra.ics.uci.edu> (raw)
In-Reply-To: <jwvoczi7jtx.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Thu, 11 Dec 2008 11:37:13 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > As you well know my taste is exactly not to add such #defines. There's
> > not such #define in the daemon implementation in src, the new macro in
> > undocumented, and your move was just designed as a provocation.
>
> Please, let's calm down.
>
> I generally agree that it's better to use "#ifdef <FEATURE>" than
> "#ifdef <PLATFORM>" (tho it always depends on the specifics), so to
> a large extent I prefer Juanma's code in this case. But in any case,
> when it's a question of taste, the one who wrote the code (Juanma in
> this case, even if it touched the code you wrote) gets to choose.
> Only ever change someone else's code when it's uncontroversial, or only
> after a discussion here concluded it's better to change it. In this
> case, it's clearly controversial.
I think you got it wrong here. I wrote the code, Juanma just sprinkled
a few #ifdefs to simply disable it on windows, nothing else. He knew
clearly well what my taste is. Given that I get to fix bugs in the
code, I prefer for it to be done in the way I think it's right.
next prev parent reply other threads:[~2008-12-11 17:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812112123.mBBLNGpI001493@mothra.ics.uci.edu>
2008-11-02 18:18 ` bug#1298: allow 'emacsclient -a "emacs --daemon && emacsclient -c"' Dan Nicolaescu
2008-11-18 8:22 ` Dan Nicolaescu
2008-11-18 16:36 ` Stefan Monnier
2008-11-18 18:17 ` Dan Nicolaescu
2008-11-18 21:34 ` Stefan Monnier
2008-11-18 22:19 ` Dan Nicolaescu
2008-11-18 23:01 ` Stefan Monnier
2008-11-18 23:27 ` Dan Nicolaescu
2008-11-19 2:21 ` Stefan Monnier
2008-12-08 7:54 ` Dan Nicolaescu
2008-12-08 16:44 ` Stefan Monnier
2008-12-08 17:09 ` Dan Nicolaescu
2008-12-08 20:07 ` Stefan Monnier
2008-12-08 20:20 ` Dan Nicolaescu
2008-12-08 21:48 ` Stefan Monnier
2008-12-09 18:58 ` Dan Nicolaescu
2008-12-09 19:30 ` Juanma Barranquero
2008-12-09 20:07 ` Stefan Monnier
2008-12-10 7:58 ` Dan Nicolaescu
2008-12-10 9:49 ` Juanma Barranquero
2008-12-10 15:03 ` Dan Nicolaescu
2008-12-10 15:10 ` Juanma Barranquero
2008-12-10 15:29 ` Dan Nicolaescu
2008-12-10 15:32 ` Juanma Barranquero
2008-12-10 15:43 ` Dan Nicolaescu
2008-12-10 15:55 ` Juanma Barranquero
2008-12-11 16:37 ` Stefan Monnier
2008-12-11 17:08 ` Dan Nicolaescu [this message]
2008-12-11 19:05 ` Juanma Barranquero
2008-12-11 19:06 ` Stefan Monnier
2008-12-11 19:08 ` Juanma Barranquero
2008-12-11 19:28 ` Dan Nicolaescu
2008-12-11 19:58 ` Juanma Barranquero
2008-12-11 20:39 ` Dan Nicolaescu
2008-12-11 20:48 ` Juanma Barranquero
2008-12-11 20:58 ` Stefan Monnier
2008-11-18 23:01 ` Andreas Schwab
2008-11-18 19:43 ` Eli Zaretskii
2008-12-11 21:25 ` bug#1298: marked as done (allow 'emacsclient -a "emacs --daemon && emacsclient -c"') Emacs bug Tracking System
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=200812111708.mBBH8seW000410@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=1298@emacsbugs.donarmstrong.com \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).