From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: 2864@debbugs.gnu.org
Subject: bug#2864: running emacsclient uninstalled
Date: Sat, 12 Feb 2022 08:15:54 +0100 [thread overview]
Message-ID: <87v8xk4kt1.fsf@gnus.org> (raw)
In-Reply-To: <E1LpSMu-0005RY-1b@fencepost.gnu.org> (Alfred M. Szmidt's message of "Thu, 02 Apr 2009 15:14:28 -0400")
"Alfred M. Szmidt" <ams@gnu.org> writes:
> There are a few problems with emacsclient in CVS, first one is that
> one cannot run emacsclient from the build directory, you can do this
> with emacs just fine. But emacsclien gets confused as to where things
> are, and you must do a `make install' to be able to use emacsclient
> properly.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
This has been fixed in the decade since this was reported.
> The second one is that the handling of -a/--alternative-editor is
> problematic,
>
> $ emacs/lib-src/emacsclient -a -c
> emacs/lib-src/emacsclient: file name or argument required
> Try `emacs/lib-src/emacsclient --help' for more information
>
> According to the docstring, the argument to -a is optional, but one
> must supply a empty string explicitly for things to work as
> advertised.
The -a argument is not optional now, at least.
So it looks like both things in this bug report are fixed, and I'm
therefore closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-02-12 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 19:14 bug#2864: emacsclient bugs Alfred M. Szmidt
2009-04-02 19:50 ` Dan Nicolaescu
2009-04-02 20:12 ` Alfred M. Szmidt
2009-04-02 20:25 ` Dan Nicolaescu
2009-04-02 20:35 ` Alfred M. Szmidt
2009-04-02 21:14 ` Dan Nicolaescu
2009-04-02 21:23 ` Alfred M. Szmidt
2009-04-02 21:41 ` Dan Nicolaescu
2009-04-02 22:06 ` Alfred M. Szmidt
2009-04-03 0:51 ` Stefan Monnier
2022-02-12 7:15 ` Lars Ingebrigtsen [this message]
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=87v8xk4kt1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=2864@debbugs.gnu.org \
--cc=ams@gnu.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 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.