emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ)" <nbercher@along-track.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, emacs-orgmode@gnu.org
Subject: Re: [IT] Broken support for links to text files (both internal & external)
Date: Mon, 8 Jan 2018 18:56:47 +0100	[thread overview]
Message-ID: <1cad6675-4cd6-d8fd-6b1c-0c94a9aa2890@along-track.com> (raw)
In-Reply-To: <1fa8ac46-6dd4-483c-6646-7a4635aa31b6@along-track.com>

This patch to my ~/.emacs PARTIALLY, but permanently, solved my issue:

diff --git a/conf/home/.emacs b/conf/home/.emacs
index 6bc96469e..cef1c08a7 100755
--- a/conf/home/.emacs
+++ b/conf/home/.emacs
@@ -27,6 +27,7 @@
   ;; If you edit it by hand, you could mess it up, so be careful.
   ;; Your init file should contain only one such instance.
   ;; If there is more than one, they won't work right.
+ '(org-link-search-must-match-exact-headline nil)
   '(inhibit-startup-screen t)
   '(safe-local-variable-values

Now, I can use again my internal links to inline random text in my
files

HOWEVER, in the case of links pointing to headlines, the matching to has
to be EXACT (but it was not necessary in earlier version since 2011 at
least) otherwise I get the message below:

   "No match for fuzzy expression: <random text>"

Do you know if I can revert some option to make the sample below to work
again?

-----8<-----
[[*random text][link to the past]]

* TODO random text in a headline title
-----8<-----

As of today, only this link with EXACT matching would work:

[[*random text in a headline title][link to the past]]

Thanks a lot,
Nicolas

On 05/01/2018 17:15, Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ) wrote:
> On 05/01/2018 13:27, Eric S Fraga wrote:
>> On Friday,  5 Jan 2018 at 13:10, Nicolas Bercher (Aʟᴏɴɢ-Tʀᴀᴄᴋ) wrote:
>>
>> [...]
>>
>>> Is it possible that this setting is set by Debian packagers?
>>> I ask this because I reproduced this bug with and without my
>>>   ~/.emacs[.d/] files.
>>
>> It's the default for org (at least now, as far as I can tell).
>>
>>> But I ashamedly don't know how to set it permanently in my  ~/.emacs!
>>> Would you please help me on this?
>>
>> Easy: describe the variable
>>
>>    C-h v org-link-search-must-match-exact-headline RET
>>
>> and then click on the "customize" link near the end of the
>> description.  Make sure to "Apply and set" the change you make.
>>
> 
> I've done this but only changed the indentation of the
> custom-set-variables block and added nothing new.
> 
> And if I start from an empty ~/.emacs I got this ew block, but again, it
> does not mention org-link-search-must-match-exact-headline variable:
> 
> (custom-set-variables
>   ;; custom-set-variables was added by Custom.
>   ;; If you edit it by hand, you could mess it up, so be careful.
>   ;; Your init file should contain only one such instance.
>   ;; If there is more than one, they won't work right.
>   )
> (custom-set-faces
>   ;; custom-set-faces was added by Custom.
>   ;; If you edit it by hand, you could mess it up, so be careful.
>   ;; Your init file should contain only one such instance.
>   ;; If there is more than one, they won't work right.
>   )
> 
> What should I add *by hand* in ~/.emacs?
> I'm sorry, it is just a matter of very basic elisp syntax (but I never
> took the time to dig into elisp yet!).
> 
> Thank you,
> Nicolas


-- 
Nicolas Bercher
Aʟᴏɴɢ-Tʀᴀᴄᴋ
Mob: +33 651 792 011
Tel: +33 952 550 210
Fax: +33 957 550 210
http://www.along-track.com/

  parent reply	other threads:[~2018-01-08 17:57 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
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ʀᴀᴄᴋ) [this message]
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=1cad6675-4cd6-d8fd-6b1c-0c94a9aa2890@along-track.com \
    --to=nbercher@along-track.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).