From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 20090@debbugs.gnu.org
Subject: bug#20090: improperly closed
Date: Sun, 03 Dec 2017 22:21:23 +0100 [thread overview]
Message-ID: <87d13va4oc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20171203190840.eqaju3peslti3w6n@E15-2016.optimum.net> (Boruch Baum's message of "Sun, 3 Dec 2017 14:09:40 -0500")
Boruch Baum <boruch_baum@gmx.com> writes:
> Bug report 20090 was perfunctorily closed today:
> 1] without the person who performed the action consulting with the bug
> reporter;
You're free to re-open the bug or create another one if you disagree.
For the record, I don't consider this to be a bug, but a feature
request.
> 2] without any discussion for over 2.5 years;
I hope you are not blaming me for that.
> 3] with a reason given that demonstrates that the person who performed
> the action didn't give the action much of any thought;
Yet, I gave it more thought than anyone in 2.5 years!
> In this particular case, the person who closed the bug apparently looked
> at the sentence fragment 'does not work for positions within an info node (eg.
> line 85 of node x)', and confused the term `eg' with the term 'ie'.
How nice.
> At this point, emacs is uniquely inferior to all major 'word processors'
> in that it does not support the feature described in the bug, ie. the
> ability to link to a specific position within a document.
>
> Pretty basic, no?
Pretty inaccurate, actually. Org is able to link to a specific position
within an Org document, and to a specific line in any plain text
document.
Your feature request is to link to a specific position in a document
written in a foreign, processed format, namely Info. I cannot think of
any reliable way to do so (e.g., "going to the node, and searching for
a string" doesn't qualify as "reliable"). If you have an idea about it,
I suggest to first implement it as a custom link type, and open a proper
feature request, or report it on the Org mailing list.
Another option is to wait for 2.5 years again and despise the next
person to close this report.
Regards,
prev parent reply other threads:[~2017-12-03 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5500BF9E.7010608@gmx.com>
2015-03-12 19:50 ` bug#20090: 24.4: linking to a position within an info node Juri Linkov
2015-03-13 14:58 ` Boruch Baum
2017-12-03 17:27 ` Nicolas Goaziou
2017-12-03 17:27 ` Nicolas Goaziou
2017-12-03 19:09 ` bug#20090: improperly closed Boruch Baum
2017-12-03 21:21 ` Nicolas Goaziou [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d13va4oc.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=20090@debbugs.gnu.org \
--cc=boruch_baum@gmx.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/org-mode.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).