From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC][PATCH] Allow to export to ascii custom link types as notes
Date: Sun, 22 Oct 2023 09:13:36 +0000 [thread overview]
Message-ID: <874jijaukf.fsf@localhost> (raw)
In-Reply-To: <ugucve$12l4$1@ciao.gmane.io>
Max Nikulin <manikulin@gmail.com> writes:
> it was discussed that attempts to customize export to plain text of link
> types such as "elisp:" and "shell:" break formatting as notes at the end
> of the heading (`org-ascii-links-to-notes').
>
> The attached patches is a draft implementing this feature (new functions
> are not documented yet).
>
> For ascii backend :export function from `org-link-parameters' may return
> (PATH . DESCRIPTION) `cons' instead of string. Depending on chosen link
> style it will be exported as "[DESCRIPTION]" with the "[DESCRIPTION]
> PATH" note at the end of heading or as the inline reference "DESCRIPTION
> (PATH)".
This is non-standard. We should document it somewhere in the manual.
> I believe that parenthesis should be skipped in the case of angle
> brackets "(<URI>)", but I do not change this behavior. There is some
> inconsistency in respect to brackets for description of inline links,
> but it is preserved as well.
May you elaborate?
> I do not like that :export functions are called twice: for text and for
> note. In my opinion it is better to collect links in a property of INFO
> to later format notes at the end of the heading. I would consider more
> dense style of notes with list markers instead of empty line as separator.
Again, may you elaborate?
> + (if (string-match-p "\\`\u200b*\\[.*\\]\u200b*\\'" anchor)
> + anchor
> + (format "[%s]" anchor))
This is out of scope of the patch, isn't it?
I can see the motivation, but we should probably move this change to a
separate patch and discussion thread.
--
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-22 9:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 17:21 [RFC][PATCH] Allow to export to ascii custom link types as notes Max Nikulin
2023-10-22 9:13 ` Ihor Radchenko [this message]
2023-10-22 17:05 ` Max Nikulin
2023-10-23 9:17 ` Ihor Radchenko
2023-10-23 11:00 ` Max Nikulin
2023-10-23 12:09 ` Ihor Radchenko
2023-10-24 8:11 ` Max Nikulin
2023-10-24 10:40 ` Ihor Radchenko
2023-10-24 15:06 ` [PATCH] ox-ascii.el: Consistently add brackets around links (was: Re: [RFC][PATCH] Allow to export to ascii custom link types as notes) Max Nikulin
2023-10-25 10:34 ` Ihor Radchenko
2023-10-26 16:46 ` man pages references (Re: [PATCH] ox-ascii.el: Consistently add brackets around links) Max Nikulin
2023-11-05 12:08 ` Ihor Radchenko
2023-10-27 14:36 ` [RFC][PATCH] Allow to export to ascii custom link types as notes Max Nikulin
2023-10-25 15:16 ` [RFC][PATCH v2] " Max Nikulin
2023-11-07 9:30 ` Ihor Radchenko
2023-11-07 11:48 ` Max Nikulin
2023-11-07 11:58 ` Ihor Radchenko
2023-11-08 10:23 ` Max Nikulin
2023-11-08 10:45 ` Ihor Radchenko
2023-11-08 10:57 ` Max Nikulin
2023-11-08 11:16 ` Ihor Radchenko
2023-11-09 11:12 ` Max Nikulin
2023-11-11 11:17 ` Ihor Radchenko
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=874jijaukf.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 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).