From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
890@emacsbugs.donarmstrong.com
Cc: find lulu <tpeplt@gmail.com>
Subject: bug#890: Problem using `etc/emacs.bash' with EmacsW32
Date: Sat, 06 Sep 2008 22:11:52 +0200 [thread overview]
Message-ID: <48C2E408.6090606@gmail.com> (raw)
In-Reply-To: <jwv63p93vzg.fsf-monnier+emacsbugreports@gnu.org>
Stefan Monnier wrote:
>>>> * I am attempting to use the shell script `emacs.bash' that is provided*
>>> Could you explain why you don't ust use emacsclient directly (together
>>> with its -a argument)?
>> Your question prompts the question "Why does `etc/emacs.bash' exist at all?"
>
> Indeed, it's part of the question ;-)
> IIUC emacs.bash was written before emacsclient got its -a argument and
> it should either be removed or changed to use emacsclient's -a argument.
>
> But for that, we need someone (e.g. you) to test the replacement.
Or, in the a bit longer perspective perhaps, emacsclient should be
enhanced to start Emacs itself when needed. (As you know there is code
for this available.)
next prev parent reply other threads:[~2008-09-06 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 15:39 bug#890: Problem using `etc/emacs.bash' with EmacsW32 find lulu
2008-09-06 12:53 ` Lennart Borgman (gmail)
2008-09-06 19:41 ` Stefan Monnier
2008-09-06 20:11 ` Lennart Borgman (gmail) [this message]
2008-09-06 20:33 ` Juanma Barranquero
2008-09-06 21:46 ` Lennart Borgman (gmail)
2008-09-06 22:06 ` Juanma Barranquero
2011-03-03 6:45 ` Glenn Morris
2008-09-06 21:20 ` martin rudalics
2008-09-07 4:03 ` find lulu
2008-09-07 9:37 ` martin rudalics
2008-09-07 22:01 ` find lulu
-- strict thread matches above, loose matches on Subject: below --
2008-09-04 19:55 Anonymous Sender
2008-09-05 3:55 ` Stefan Monnier
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=48C2E408.6090606@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=890@emacsbugs.donarmstrong.com \
--cc=monnier@iro.umontreal.ca \
--cc=tpeplt@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).