From: Scott Randby <srandby@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Link Bug?
Date: Tue, 15 Jan 2019 20:58:00 -0500 [thread overview]
Message-ID: <7a5ea01d-23db-fabb-8a7e-f8cd169209f7@gmail.com> (raw)
In-Reply-To: <84h8e98wal.fsf@gmail.com>
On 1/15/19 4:07 PM, Marco Wahl wrote:
> Hi,
>
> Scott Randby <srandby@gmail.com> writes:
>
>> First, I'm using Emacs 26.1 and Org 9.2.
>>
>> If I have [[./page.html]] in an Org file and I click on the link,
>> page.html is opened in my browser, but if I have
>> [[./page.html#section]] in the Org file and I click on that link, a
>> text file named page.html#section is opened in a buffer instead of a
>> page in my browser that starts at the desired place. I'm not sure if
>> this is a bug or not, but it isn't the kind of behavior I want. Is
>> there any way of getting around this behavior?
>
> The core of your issue seems to be that one can interpret
> "./page.html#section" as filename and also as an anchor in html file
> "./page.html".
>
> Possibly there are clever ways to make the program smarter to detect
> links to anchors in html files.
>
> A way around is to be more explicit in the link. E.g. call a browser
> via elisp and use the "file:" protocol:
>
> [[elisp:(browse-url-firefox "file:///home/webstuff/page.html#section")]]
This sort of works, but it doesn't give me the correct link when I export to HTML. I was hoping to check links to anchors in HTML files before exporting to HTML, but maybe that was wishful thinking. Oh well, it is easy enough to check such links after exporting to HTML. I don't know enough elisp to be able to think about making Org smarter. Thanks for the help.
Scott
prev parent reply other threads:[~2019-01-16 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 19:21 Link Bug? Scott Randby
2019-01-15 21:07 ` Marco Wahl
2019-01-16 1:58 ` Scott Randby [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=7a5ea01d-23db-fabb-8a7e-f8cd169209f7@gmail.com \
--to=srandby@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).