emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Regression - problem with links
Date: Fri, 15 Mar 2019 16:18:15 -0400	[thread overview]
Message-ID: <87lg1fao3c.fsf@norang.ca> (raw)
In-Reply-To: <84mulw41vz.fsf@gmail.com> (Marco Wahl's message of "Fri, 15 Mar 2019 16:02:08 +0100")

Marco Wahl <marcowahlsoft@gmail.com> writes:

> Hi,
>
> [...]
>
>> My links are like this:
>>
>>
>> [[https://somewebsiteaddress.net/path/to/page.do][Timekeeper]]
>> [[id:eb1085ed-15fe-46a3-8b5e-3971587d1123][OTL 2019]]
>>
>> and I want to see
>>
>> [1] Timekeeper
>> [2] OTL 2019
>>
>> but instead I get the address like this which is much less useable
>>
>> [1] https://somewebsiteaddress.net/path/to/page.do
>> [2] id:eb1085ed-15fe-46a3-8b5e-3971587d1123
>
> This sounds like a bug fixed a few days ago.
>
>     https://code.orgmode.org/bzg/org-mode/commit/b1429cdfe043b199bb7be6dc5c97a299954b4e0d
>
> Can you check if the fix is in your copy of Org?

I have that commit in my current git version.

Last week I noticed agenda clock reports had file: text before this fix
and reverted back to normal looking clock reports after however the menu
from C-c C-o doesn't display link descriptions for me.

I'll try to isolate which commit breaks this.

Regards,
Bernt

  reply	other threads:[~2019-03-15 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 14:27 Regression - problem with links Bernt Hansen
2019-03-15 15:02 ` Marco Wahl
2019-03-15 20:18   ` Bernt Hansen [this message]
2019-03-15 20:34     ` Bernt Hansen
2019-03-15 21:56       ` Marco Wahl
2019-03-16 14:46         ` Bernt Hansen
2019-03-16 15:54           ` Bernt Hansen
2019-03-16 17:06             ` Nicolas Goaziou
2019-03-16 19:27               ` Bernt Hansen
2019-03-15 15:02 ` Eric S Fraga

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=87lg1fao3c.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=marcowahlsoft@gmail.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).