emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Juri Linkov <juri@linkov.net>
Cc: 20090@debbugs.gnu.org
Subject: bug#20090: 24.4: linking to a position within an info node
Date: Fri, 13 Mar 2015 10:58:58 -0400	[thread overview]
Message-ID: <5502FB32.9090006@gmx.com> (raw)
In-Reply-To: <87oanyc7vg.fsf@mail.linkov.net>

[-- Attachment #1: Type: text/plain, Size: 2978 bytes --]

On 03/12/2015 03:50 PM, Juri Linkov wrote:
>> When the org mode manual discusses creating links, it gives an example
>> of linking to an info node (the self-referencing example is
>> `info:org#External' links). The manual continues, at node
>> `info:org#Search options', to describe how specific positions within
>> file links can be directly specified. This does work for links to
>> regular files, but does not work for positions within an info node (eg.
>> line 85 of node x).
> 
> Is there an official format for the line numbers in Info cross-references?
I don't know - my assumption was that within emacs, it would be
basically just another type of emacs buffer, and be a legitimate subject
for all elisp commands.

Your question got me thinking, that emacs may have subtle rendering
quirks, so just now, I opened fresh instances of info buffers in both
very wide and very narrow windows, and they both `fill' to the same line
length, ie the wide window has a lot of right-side white-space, and the
narrow window has lines wrapped.

Since I submitted the bug report, I've continued trying to get the
feature working, and have been experimenting with the org-mode hooks
`org-create-file-search-functions' and
`org-execute-file-search-functions' to no success. The only, supposedly
working examples I've come across for these functions are [1] and [2].
If you know of other resources, that could be helpful.

One other possible related bug I've found is that when trying to use
org-store-link for a particular line number within an org-file, the link
is created to the most recent header. One can successfully, manually,
hack the created link, replacing the reference to the header with a line
number, in order to be able to navigate directly to the desired line
(all this, for a link target in an org mode file - this was done as a
test, once I came across the original bug) [3].

[1]
https://stackoverflow.com/questions/10681766/emacs-org-mode-textual-reference-to-a-fileline

[2] http://www.emacswiki.org/emacs/.emacs-DominiqueQuatravaux.el

[3] info:org#Search options

> 
> (info "(texinfo) Printing Indices & Menus") documents the format of
> line numbers only in the index, not in the cross-references:
> 
>    * In Info output, `@printindex' produces a special menu containing
>      the line number of the entry, relative to the start of the node.
>      Info readers can use this to go to the exact line of an entry, not
>      just the containing node.  (Older Info readers will just go to the
>      node.)  Here's an example:
> 
>           * First index entry:   Top.   (line  7)
> 
>      The actual number of spaces is variable, to right-justify the line
>      number; it's been reduced here to make the line fit in the printed
>      manual.
> 
> The Info reader already supports this format in the index.
> 


-- 
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-03-13 15:00 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 [this message]
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

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=5502FB32.9090006@gmx.com \
    --to=boruch_baum@gmx.com \
    --cc=20090@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).