all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: p.stephani2@gmail.com, 31929@debbugs.gnu.org, kaushal.modi@gmail.com
Subject: bug#31929: [PATCH] Install emacs-module.h (Bug#31929)
Date: Tue, 16 Oct 2018 05:29:47 +0300	[thread overview]
Message-ID: <83pnwasjxg.fsf@gnu.org> (raw)
In-Reply-To: <1x1s8rf02m.fsf@fencepost.gnu.org> (message from Glenn Morris on Mon, 15 Oct 2018 16:04:49 -0400)

> From: Glenn Morris <rgm@gnu.org>
> Cc: 31929@debbugs.gnu.org,  p.stephani2@gmail.com,  kaushal.modi@gmail.com
> Date: Mon, 15 Oct 2018 16:04:49 -0400
> 
> > Lastly, we name the file explicitly in the documentation.
> 
> The documentation also names eg the "emacs" and "emacslient"

I mean the examples in which there's an #include statement.  It's not
the same as naming executables, IMO.

I think we should wait until we hear real-life use cases where the
fixed name is a problem, before we decide on a solution.





  reply	other threads:[~2018-10-16  2:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21 16:04 bug#31929: 27.0.50; Have make install copy the emacs-module.h to the destination install dir Kaushal Modi
2018-09-21 13:27 ` bug#31929: [PATCH] Install emacs-module.h (Bug#31929) Philipp Stephani
2018-09-21 13:45   ` Eli Zaretskii
2018-09-21 16:56     ` Philipp Stephani
2018-09-21 15:36   ` Glenn Morris
2018-09-21 16:57     ` Philipp Stephani
2018-10-03 20:02   ` Philipp Stephani
2018-10-03 20:51     ` Glenn Morris
2018-10-06 10:19       ` Eli Zaretskii
2018-10-15 20:04         ` Glenn Morris
2018-10-16  2:29           ` Eli Zaretskii [this message]
2018-10-04 16:16     ` Eli Zaretskii
     [not found] ` <handler.31929.D31929.153859694712784.notifdone@debbugs.gnu.org>
2018-10-03 20:27   ` bug#31929: closed (Re: [PATCH] Install emacs-module.h (Bug#31929)) Kaushal Modi
2018-10-03 20:49     ` Glenn Morris

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=83pnwasjxg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31929@debbugs.gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=p.stephani2@gmail.com \
    --cc=rgm@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.