unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Smith <psmith@gnu.org>
Cc: 42411@debbugs.gnu.org
Subject: bug#42411: Bug with M-x compile
Date: Sun, 26 Jul 2020 16:55:29 +0300	[thread overview]
Message-ID: <83r1sybctq.fsf@gnu.org> (raw)
In-Reply-To: <alpine.NEB.2.21.2007260053210394.24631@sdf.lonestar.org> (message from Gregory Heytings on Sat, 25 Jul 2020 23:29:09 +0000)

> Date: Sat, 25 Jul 2020 23:29:09 +0000
> From: Gregory Heytings <ghe@sdf.org>
> cc: Eli Zaretskii <eliz@gnu.org>
> 
> > And there could be other situations as well.  I'm not an expert; if we 
> > want to review all the possible use cases, perhaps we should ask Paul 
> > Smith, the GNU Make maintainer, to join this discussion and help us 
> > enumerate the possible cases.
> >
> 
> I'm not an expert either, so yes, please ask Paul Smith for advice on 
> this.  I do think that the way to compute completion candidates should be 
> improved.
> 
> There will always be exceptional cases (for example, for GNU Make, 
> .RECIPEPREFIX with which it is possible to use another prefix character 
> instead of TAB can apparently be used multiple times), but for something 
> like 99.9% cases, a line starting with a TAB is a recipe element and not a 
> target, a line starting with a '#' is a comment, and a line starting with 
> a '.' sets a special variable.  The current regexp correctly excludes the 
> last two, but includes the first one.

Paul, could you please chime in and share your views on this?  If you
want to read the discussion from the beginning, you can find it at

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42411

or, if you prefer to read all of it in your MUA, you can download all
the messages in the mbox format:

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42411;mbox=yes

TIA





  reply	other threads:[~2020-07-26 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18  9:01 bug#42411: Bug with M-x compile Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-25  7:24 ` Eli Zaretskii
2020-07-25 23:29   ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-26 13:55     ` Eli Zaretskii [this message]
2020-07-31 18:20       ` Paul Smith
2020-07-31 18:42         ` Eli Zaretskii
2020-07-31 18:58           ` Paul Smith
2020-08-21 10:45 ` Lars Ingebrigtsen

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=83r1sybctq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42411@debbugs.gnu.org \
    --cc=psmith@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 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).