From: Eric S Fraga <esflists@gmail.com>
To: "Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)" <nbercher@along-track.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [IT] Broken support for links to text files (both internal & external)
Date: Fri, 05 Jan 2018 06:42:02 +0000 [thread overview]
Message-ID: <87h8s0lscl.fsf@gmail.com> (raw)
In-Reply-To: <4abbb185-4323-8c62-c4f7-4a9a3b7a6b88@along-track.com> (Nicolas Bercher's message of "Thu, 4 Jan 2018 17:20:44 +0100")
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Thursday, 4 Jan 2018 at 17:20, Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ) wrote:
> Dear org-mode developers,
>
> Please find attached an org-mode file describing the issue.
Could you please post an org file that demonstrates the actual problem?
That is, one with headings you wish to link to?
> This is a sample org-mode log to report on what looks like a
> regression in between Debian Jessie's emacs24 (=24.4+1-5+deb8u1) and
> Debian Stretch's emacs24 (=24.5+1-11+deb9u1).
What are the versions of org in each of these? They may be quite old
and, more importantly, they could straddle a major version change of org
(from 7.x to 8.x or even 9.x).
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2018-01-05 6:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 16:20 [IT] Broken support for links to text files (both internal & external) Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)
2018-01-05 6:42 ` Eric S Fraga [this message]
2018-01-05 7:32 ` Nicolas Goaziou
2018-01-05 12:10 ` Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)
2018-01-05 12:27 ` Eric S Fraga
2018-01-05 16:15 ` Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)
2018-01-05 17:47 ` Eric S Fraga
2018-01-05 20:16 ` Tim Cross
2018-01-08 17:56 ` Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)
2018-01-09 19:36 ` Nicolas Goaziou
2018-01-10 3:44 ` Samuel Wales
2018-01-10 3:46 ` Samuel Wales
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=87h8s0lscl.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nbercher@along-track.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).