From: Ruijie Yu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 63480@debbugs.gnu.org
Subject: bug#63480: 30.0.50; [BUG] unimplemented logic regarding read-symbol-shorthands
Date: Sat, 13 May 2023 13:37:37 +0800 [thread overview]
Message-ID: <sdvr0rkzt9a.fsf@netyu.xyz> (raw)
In-Reply-To: <sdvv8gwztqt.fsf@netyu.xyz>
Ruijie Yu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> writes:
> While trying out João's breadcrumb package, I noticed a few issues
> regarding `read-symbol-shorthands'. Searching this variable on debbugs
> yields zero results, so I figured maybe I should at least let the
> bugtracker know about them.
Sorry, correction: I guess one cannot just search for keywords on
debbugs. I searched on bug archive just now and found out that there
are 29 threads on this variable.
--
Best,
RY
next prev parent reply other threads:[~2023-05-13 5:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 5:27 bug#63480: 30.0.50; [BUG] unimplemented logic regarding read-symbol-shorthands Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13 5:37 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-06 11:03 ` Stefan Kangas
2023-09-06 14:02 ` João Távora
2023-09-06 20:17 ` Stefan Kangas
2023-11-29 7:45 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-29 8:12 ` João Távora
2024-04-18 20:01 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-18 20:24 ` João Távora
2024-04-18 20:52 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-23 21:38 ` Joseph Turner 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
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=sdvr0rkzt9a.fsf@netyu.xyz \
--to=bug-gnu-emacs@gnu.org \
--cc=63480@debbugs.gnu.org \
--cc=ruijie@netyu.xyz \
/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).