From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marco Wahl <marcowahlsoft@gmail.com>
Subject: Re: Link Bug?
Date: Tue, 15 Jan 2019 22:07:14 +0100
Message-ID: <84h8e98wal.fsf@gmail.com>
References: <ed544a08-d4fb-bba2-bc8e-bfe67b5ddc33@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:58394)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1gjVvo-0004He-EQ
	for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 16:07:33 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1gjVvn-0003xH-IH
	for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 16:07:32 -0500
Received: from [195.159.176.226] (port=52352 helo=blaine.gmane.org)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <geo-emacs-orgmode@m.gmane.org>)
	id 1gjVvl-0003kR-9W
	for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 16:07:31 -0500
Received: from list by blaine.gmane.org with local (Exim 4.84_2)
	(envelope-from <geo-emacs-orgmode@m.gmane.org>) id 1gjVtX-00085I-Nx
	for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 22:05:11 +0100
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: emacs-orgmode@gnu.org

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")]]


HTH
-- 
Marco