From: Eric S Fraga <esflists@gmail.com>
To: Win Treese <treese@acm.org>
Cc: Emacs-orgmode@gnu.org
Subject: Re: open link in source code block
Date: Sat, 05 Jan 2019 10:25:13 +0000 [thread overview]
Message-ID: <87y37zo0za.fsf@gmail.com> (raw)
In-Reply-To: <8585C713-3A24-4FE3-A187-A4587F3ADC97@acm.org> (Win Treese's message of "Fri, 4 Jan 2019 19:38:35 -0500")
On Friday, 4 Jan 2019 at 19:38, Win Treese wrote:
> Suppose I have the following Org file contents:
>
> * test
>
> #+BEGIN_SRC emacs-lisp
> (setq yyy 3)
> ;; See https://www.gnu.org
> #+END_SRC
>
> The URL for gnu.org is highlighted as a clickable link. But if I click
> it, the source block is evaluated. This seems rather unexpected,
> especially since my intention was to open the link.
Probably expected albeit maybe not your preferred behaviour; all about
precedence. In any case, I would suggest that the easy solution would
be to move such links out of the src block. I usually put these as org
comments, along the lines of
# See https://www.gnu.org
#+BEGIN_SRC emacs-lisp
(setq yyy 3)
#+END_SRC
My approach to literate programming is to have no (significant) comments
in the code segments themselves. Each code block is small and has all
commentary in the text, not the code.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442
next prev parent reply other threads:[~2019-01-05 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 0:38 open link in source code block Win Treese
2019-01-05 10:25 ` Eric S Fraga [this message]
2019-01-05 15:41 ` Win Treese
2019-01-12 0:12 ` Berry, Charles
2019-01-16 23:43 ` Win Treese
2019-01-17 18:38 ` Berry, Charles
2019-01-18 2:05 ` Win Treese
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=87y37zo0za.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=treese@acm.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).