From: ST <smntov@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Emacs-orgmode@gnu.org
Subject: Re: Feature proposal: Triple square brackets to create a link to a file AND include the file
Date: Thu, 27 Sep 2018 17:08:41 +0300 [thread overview]
Message-ID: <1538057321.1873.35.camel@gmail.com> (raw)
In-Reply-To: <87k1n7jeuk.fsf@nicolasgoaziou.fr>
> > What do you mean by "inlined"?
>
> Roughly, I mean "located within a paragraph".
>
> > During an export such a link
> > [[[dir/file]]] should be replaced with the content of the "file", and
> > the link itself disappear. But in the source .org file it is just
> > shorter/cleaner way to write
> >
> > #+INCLUDE: "dir/file"
>
> This is different. It is easier to insert text at column 0 than at
> a random position in a line. You cannot do the latter in Org.
Aaa... I see. Actually I don't need it to be in the middle, only at
column 0.
> > and be able to click the link to open the file in a separate buffer.
>
> This is already possible.
Starting with which version of Org? I have 8.2.10 and it doesn't seem to
work there...
>
> > Why shouldn't it be possible to achieve just the same by ALSO clicking
> > on the URI? If you use .org files as a wiki - this feature is quite
> > useful.
>
> Why do you need something else if there is already a way to do what you
> want? I'm not a big fan of extending syntax gratuitously.
Well, triple square brackets is shorter and cleaner for wiki purposes...
I don't mind it to be able to include files only at column 0, it's
totally OK.
Regards.
next prev parent reply other threads:[~2018-09-27 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 11:35 Feature proposal: Triple square brackets to create a link to a file AND include the file ST
2018-09-27 11:58 ` Nicolas Goaziou
2018-09-27 12:18 ` ST
[not found] ` <87k1n7jeuk.fsf@nicolasgoaziou.fr>
2018-09-27 14:08 ` ST [this message]
2018-09-27 15:02 ` Nicolas Goaziou
2018-09-27 15:11 ` Kaushal Modi
2018-09-27 14:54 ` Nicolas Goaziou
2018-09-27 16:55 ` John Kitchin
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=1538057321.1873.35.camel@gmail.com \
--to=smntov@gmail.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).