all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Randy Taylor <dev@rjt.dev>
Cc: 59979@debbugs.gnu.org
Subject: bug#59979: 30.0.50; dockerfile-ts-mode imenu issue
Date: Mon, 12 Dec 2022 10:28:34 +0200	[thread overview]
Message-ID: <m1359lhvpp.fsf@gmail.com> (raw)
In-Reply-To: <lQ6h_YSxTGOxDyIEGMFZU0NsIcCphtLsnand76B9BgjDNlPa1MFxb9y6oBq3a4tPe5Hdgirl2voiwKlxXQJsN9adWUTVQzVASwwPkaXFVkQ=@rjt.dev> (Randy Taylor's message of "Mon, 12 Dec 2022 02:30:28 +0000")

Randy Taylor <dev@rjt.dev> writes:

> On Sunday, December 11th, 2022 at 18:57, Randy Taylor <dev@rjt.dev> wrote:
>
> I didn't notice this because I use conult-imenu, which will add an
> index for any duplicates. imenu doesn't do this, and for other modes
> like c-mode, c++-mode, org-mode, etc., only the first entry gets
> shown.
>
> I've attached a patch which will use the stage name if it's available,
> otherwise use the base image.

Great :) That's certainly an improvement.

I still maintain that using the base image as an identifier of the build
stage is not that useful, it doesn't really identify the stage in any
way, like identifying functions their arguments doesn't make a lot of
sense.  I do see how in practice that'll probably be fine in most cases.





  reply	other threads:[~2022-12-12  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 20:39 bug#59979: 30.0.50; dockerfile-ts-mode imenu issue Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-11 23:57 ` Randy Taylor
2022-12-12  2:30   ` Randy Taylor
2022-12-12  8:28     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-12 20:16       ` Randy Taylor
2022-12-12 22:59 ` Yuan Fu
2022-12-13  0:41   ` Randy Taylor

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=m1359lhvpp.fsf@gmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59979@debbugs.gnu.org \
    --cc=dev@rjt.dev \
    --cc=me@eshelyaron.com \
    /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.