From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: export form feed as page break
Date: Mon, 23 Oct 2023 17:37:07 +0700 [thread overview]
Message-ID: <uh5icl$959$1@ciao.gmane.io> (raw)
In-Reply-To: <877cnfav5s.fsf@localhost>
On 22/10/2023 16:00, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> P.S. I am against using non-printable characters for markup. It might be
>> an \... entity for page break inside a paragraph, "#+...:" keyword
>> between block-level elements, etc.
>
> What about all the above? We may provide entity, keyword, and also ^L.
I have not changed my opinion. Control characters should not be used for
plain text markup.
^L might be inconvenient for users of browser-based tools (organice,
etc.). Firefox displays it as a square with 0c code inside <textarea>
and as some space in regular tags. In Chromium it is invisible similar
to zero-width space. Fortunately browsers allows to copy a paste it, it
is exemption from control characters that are stripped on copy to
protect users from unexpected effects of paste.
However e.g. konsole (terminal application) shows a warning popup on
attempt to paste text containing ^L.
My vote is for portability, so usage of ^L should be discouraged.
next prev parent reply other threads:[~2023-10-23 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 7:42 Feature request: export form feed as page break Marvin Gülker
2023-10-21 9:19 ` Ihor Radchenko
2023-10-21 14:43 ` Max Nikulin
2023-10-22 8:54 ` Ihor Radchenko
2023-10-21 16:33 ` Marvin Gülker
2023-10-22 8:58 ` Ihor Radchenko
2023-10-21 14:26 ` Max Nikulin
2023-10-21 16:27 ` Marvin Gülker
2023-10-22 9:00 ` Ihor Radchenko
2023-10-23 10:37 ` Max Nikulin [this message]
2023-10-22 6:00 ` Jambunathan K
2023-10-22 12:55 ` Uwe Brauer
2023-10-24 6:08 ` Marvin Gülker
2024-01-07 7:23 ` Timothy
2024-01-07 12:57 ` 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='uh5icl$959$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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).