From: Nicolas Goaziou <email@example.com>
To: Achilles Yuce <firstname.lastname@example.org>
Subject: Re: 28.0.50; [bug] Inside help buffers escaped symbol[s] causing a problem.
Date: Sun, 26 Apr 2020 10:39:49 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Achilles Yuce's message of "Sun, 26 Apr 2020 04:01:57 +0300")
Achilles Yuce <email@example.com> writes:
> After using `org-store-link`; i was expecting to jump back to what i
> stored which is the buffer to see after evaluating (describe-symbol '\`)
> but instead i got an `user-error` as you can see in [Recent messages:]
> section in this report. I believe this shouldn't be the case. My exact
> steps included in [Losage:] section.
> FWIW I somehow managed to fix it by removing the '\'s from the captured
> string defined in lisp/org/ol.el file. Also adding diff output.
It looks like a bug in Emacs, doesn't it? Why would Info buffer display
"\`" when you write "`"? I suggest to report it to Emacs developers.
Meanwhile, I pushed a work around. Thank you.
next prev parent reply other threads:[~2020-04-26 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 1:01 28.0.50; [bug] Inside help buffers escaped symbol[s] causing a problem Achilles Yuce
2020-04-26 8:39 ` Nicolas Goaziou [this message]
2020-04-26 16:32 ` Achilles Yuce
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).