emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Denton <wtd@pobox.com>
To: Perry Smith <pedz@easesoftware.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Simple but repetitive http links
Date: Wed, 7 Sep 2022 09:45:16 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2209070934320.71512@shell3.miskatonic.org> (raw)
In-Reply-To: <1DC735EE-27F6-4CDB-94E6-E6A41D10503C@easesoftware.com>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

On 7 September 2022, Perry Smith wrote:

> 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?

To tell Org about new keywords like that you need to hit C-c C-c on the keyword 
(or restart).  This is in "The Very Busy C-c C-c Key" in the manual,¹ and 
"Summary of In-Buffer Settings," but the manual is dense and it's easily 
overlooked.

However, as a general rule, if you ever want something to happen in Org, try 
hitting C-c C-c on the line and it probably will.

Welcome to Org!

Bill

¹ https://orgmode.org/org.html#The-Very-Busy-C_002dc-C_002dc-Key

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada

  reply	other threads:[~2022-09-07 13:46 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 [this message]
2022-09-07 13:49 ` Christian Moe
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=alpine.DEB.2.22.394.2209070934320.71512@shell3.miskatonic.org \
    --to=wtd@pobox.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pedz@easesoftware.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).