all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lin Jian <me@linj.tech>
Cc: 68807@debbugs.gnu.org
Subject: bug#68807: 29.1; Can bindir used for emacsclient(-mail).desktop in Makefile.in be removed?
Date: Tue, 30 Jan 2024 16:25:17 +0200	[thread overview]
Message-ID: <868r463nle.fsf@gnu.org> (raw)
In-Reply-To: <87sf2ekisb.fsf@linj.tech> (message from Lin Jian on Tue, 30 Jan 2024 22:08:47 +0800)

> From: Lin Jian <me@linj.tech>
> Cc: 68807@debbugs.gnu.org
> Date: Tue, 30 Jan 2024 22:08:47 +0800
> 
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Yes, because the Emacs's upstream installation procedure installs
> > emacsclient in ${bindir}.  So "our "make install" wants to make sure
> > the desktop file will reference the correct emacsclient, not the one
> > found first on PATH.
> 
> Since (I think) emacs and emacsclient are installed to the same
> directory, why is not bindir used for emacs in *.desktop files?  Why are
> emacs and emacsclient treated differently in *.desktop files?

I don't know, but people have been committing changes to these files
for many moons, so I guess there is some reason.  If you are really
interested, try looking at the Git history of that, and then look up
discussions here or on emacs-devel near the times of the changes.

> Is this a bug?

Not likely, because this is AFAIK used by many users and distros.





  reply	other threads:[~2024-01-30 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 22:34 bug#68807: 29.1; Can bindir used for emacsclient(-mail).desktop in Makefile.in be removed? Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-30 12:19 ` Eli Zaretskii
2024-01-30 14:08   ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-30 14:25     ` Eli Zaretskii [this message]
2024-02-05 23:36       ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=868r463nle.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68807@debbugs.gnu.org \
    --cc=me@linj.tech \
    /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.