From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Liang Wang <netcasper@gmail.com>
Cc: 9942-done@debbugs.gnu.org
Subject: bug#9942: 24.0.91; Bad link for explicit tags in *Tags List* buffer
Date: Thu, 22 Mar 2012 10:47:45 -0400 [thread overview]
Message-ID: <jwvmx7866cr.fsf-monnier+gnus-read-ephemeral-bug@gnu.org> (raw)
In-Reply-To: <877h3i2djh.fsf@lwang1.i-did-not-set--mail-host-address--so-tickle-me> (Liang Wang's message of "Thu, 03 Nov 2011 09:35:46 +0800")
> - (setq tag-info (save-excursion (funcall snarf-tag-function t))
> + (setq tag-info (save-excursion (funcall snarf-tag-function nil))
Hmm... looks like this was broken at least since Emacs-22.
Installed, thanks,
Stefan
prev parent reply other threads:[~2012-03-22 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 1:35 bug#9942: 24.0.91; Bad link for explicit tags in *Tags List* buffer Liang Wang
2012-03-22 14:47 ` Stefan Monnier [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
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=jwvmx7866cr.fsf-monnier+gnus-read-ephemeral-bug@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9942-done@debbugs.gnu.org \
--cc=netcasper@gmail.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 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).