emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: emacs-orgmode@gnu.org
Subject: Re: Simple but repetitive http links
Date: Wed, 07 Sep 2022 15:49:26 +0200	[thread overview]
Message-ID: <87sfl3wazd.fsf@christianmoe.com> (raw)
In-Reply-To: <1DC735EE-27F6-4CDB-94E6-E6A41D10503C@easesoftware.com>


Hi,

Org scans the file for link definitions when you visit it, so when you
type in the link definition in the buffer, Org is not automatically
aware that it exists. To refresh setup without reloading the file, you
can `C-c C-c' with point on the line with the definition. That should do
it.

Also, if you don't particularly need or like the behavior of querying
for creating a new headline when none is found, you can turn it off by
customizing org-link-search-must-match-exact-headline to nil (the default is
'query-to-create).

Yours,
Christian

Perry Smith writes:

> I'm new to Org mode.  I found this page
> https://orgmode.org/manual/Link-Abbreviations.html about Link
> Abbreviations but I wanted to report my confusion.
>
> I added:
>
> #+LINK: rails  https://rubyonrails.org
>
> to my org file and then I wrote [[rails][Rails]] and when I clicked
> the text, it asked me if I wanted to create a section.  I had to kill
> the buffer and reload it to get it to work.  That's fine but I'm
> wondering if there is a way to make it active without killing the
> buffer.  And I also wanted to suggest adding something about that in
> the manual.
>
> Perhaps this is a common fact with many of Org modes features that I
> missed somewhere?
>
> Thank you for your time,
> Perry


  parent reply	other threads:[~2022-09-07 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 13:05 Simple but repetitive http links Perry Smith
2022-09-07 13:45 ` William Denton
2022-09-07 13:49 ` Christian Moe [this message]
2022-09-07 16:40   ` George Mauer

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=87sfl3wazd.fsf@christianmoe.com \
    --to=mail@christianmoe.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).