From: "find lulu" <tpeplt@gmail.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: bug-gnu-emacs@gnu.org
Subject: bug#890: Problem using `etc/emacs.bash' with EmacsW32
Date: Sun, 7 Sep 2008 18:01:21 -0400 [thread overview]
Message-ID: <6bb3db200809071501g4464b661ycd649814a9609e83@mail.gmail.com> (raw)
In-Reply-To: <jwv63p93vzg.fsf-monnier+emacsbugreports@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
I have installed the newly announced EmacsW32, version 22.3 and attempted to
start Emacs with the following command at the Cygwin `bash' prompt:
$ mv ~/.emacs ~/keep.emacs # preserve init. file while testing
$ emacsclient --version
emacsclient 22.3
$ emacsclient --alternate-editor=emacs ~/.bashrc
emacsclient.exe: connect: No connection could be made because the target
machine actively refused it.
However, despite the error message, Emacs starts as expected. Within Emacs,
I ran the command M-x server-start
to start the Emacs server. A subsequent `emacsclient' command works as
expected:
$ emacsclient --alternate-editor=emacs ~/keep.emacs
Waiting for Emacs...
If the changes I suggested earlier for Emacs 22's `lisp/server.el' are made,
then the error message is not displayed after the initial invocation of
`emacsclient'. The reason the error message is displayed is the same,
namely, that when Emacs is shutting down and calls `(server-start -1)', the
code in `server-start' does not remove the server file
~/.emacs.d/server/server.
On Sat, Sep 6, 2008 at 3:41 PM, Stefan Monnier <monnier@iro.umontreal.ca>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.
>
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 2224 bytes --]
next prev parent reply other threads:[~2008-09-07 22:01 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)
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 [this message]
-- 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=6bb3db200809071501g4464b661ycd649814a9609e83@mail.gmail.com \
--to=tpeplt@gmail.com \
--cc=890@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--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).