From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting elisp: and shell: links
Date: Thu, 12 Oct 2023 11:35:55 +0000 [thread overview]
Message-ID: <87il7ckr8k.fsf@localhost> (raw)
In-Reply-To: <ug39di$2vq$1@ciao.gmane.io>
Max Nikulin <manikulin@gmail.com> writes:
>> I like more how ox-ascii (without the
>> proposed diff) handles the situation via footnote-like link.
>
> That is why I believe that extracting fragments of code into helper
> functions is important. If ox-ascii.el had a function that adds an item
> to link list then ol.el would use it to add src_elisp elements to this list.
May you elaborate? I am not talking about implementation details, but
about the reasonable defaults for the export. Not necessary ASCII, but
other backends as well.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-12 11:34 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 15:25 [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)] Csepp
2023-09-01 2:44 ` Max Nikulin
2023-09-01 9:04 ` [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)]) Ihor Radchenko
2023-09-01 10:49 ` Dr. Arne Babenhauserheide
2023-09-01 11:01 ` Ihor Radchenko
2023-09-01 12:25 ` Dr. Arne Babenhauserheide
2023-09-02 7:26 ` Ihor Radchenko
2023-09-02 7:54 ` Dr. Arne Babenhauserheide
2023-09-04 14:58 ` Max Nikulin
2023-09-05 11:02 ` Ihor Radchenko
2023-09-06 14:27 ` Max Nikulin
2023-09-07 10:42 ` Ihor Radchenko
2023-09-07 11:07 ` Max Nikulin
2023-09-07 11:22 ` Ihor Radchenko
2023-09-01 12:15 ` [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? Jens Lechtenboerger
2023-09-02 7:29 ` Ihor Radchenko
2023-09-01 18:53 ` [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)]) Tom Gillespie
2023-09-02 7:45 ` Ihor Radchenko
2023-09-02 12:00 ` [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)] Max Nikulin
2023-09-03 7:53 ` Ihor Radchenko
2023-09-04 10:51 ` Max Nikulin
2023-09-05 9:42 ` Ihor Radchenko
2023-09-10 4:40 ` Max Nikulin
2023-09-17 22:08 ` Rudolf Adamkovič
2023-09-18 15:20 ` Exporting elisp: and shell: links Max Nikulin
2023-09-19 0:10 ` Rudolf Adamkovič
2023-09-19 15:19 ` Max Nikulin
2023-09-21 9:49 ` Ihor Radchenko
2023-09-22 23:43 ` Rudolf Adamkovič
2023-09-25 14:38 ` Max Nikulin
2023-09-26 10:42 ` Ihor Radchenko
2023-09-28 15:31 ` Rudolf Adamkovič
2023-10-08 9:48 ` Ihor Radchenko
2023-10-09 12:04 ` Max Nikulin
2023-10-09 12:12 ` Ihor Radchenko
2023-10-10 10:35 ` Max Nikulin
2023-10-12 11:35 ` Ihor Radchenko [this message]
2023-10-13 10:20 ` Max Nikulin
2023-10-14 8:13 ` Ihor Radchenko
2023-10-11 19:34 ` Rudolf Adamkovič
2024-02-05 15:41 ` [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)] Ihor Radchenko
2024-03-12 11:00 ` Ihor Radchenko
2023-09-04 15:08 ` [DISCUSSION] May we recognize everything like [[protocol:uri]] as a non-fuzzy link? (was: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)]) Max Nikulin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il7ckr8k.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.