From: Marcin Borkowski <mbork@mbork.pl>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Some projects
Date: Sun, 25 Oct 2015 17:18:48 +0100 [thread overview]
Message-ID: <87io5uzzv6.fsf@mbork.pl> (raw)
In-Reply-To: <87eggjar5u.fsf@ucl.ac.uk>
On 2015-10-25, at 16:45, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Sunday, 25 Oct 2015 at 14:08, Nicolas Goaziou wrote:
>> Hello,
>>
>> I'd like to see some features moving forward, and some important issues
>> fixed, hopefully, in the next months. I'm sharing them here so that
>> anyone interested can help.
>
> Nicolas,
>
> I look forward to all the advances you have proposed... except for this one:
>
>> ** Backslash escaping
>>
>> Allowing to escape some symbols in plain text (e.g., emphasis markers,
>> square brackets...) would remove a limitation in verbatim/code objects.
>> As a small benefit, it would also permit to implement mid-word markup:
>> b*o*ld.
>
> I'm concerned that it will make typing normal text more onerous. Right
> now, org is quite non-intrusive in most of my writing yet is quite rich
> in what it can encode. Having to backslash symbols that I use in text
> quite often (especially square brackets) would be annoying. Maybe I
> misunderstood; if so, I apologise for the noise!
Eric, it's good that you write (IMO at least) - this is how the ideas
can get refined.
Since your point is quite valid - and OTOH, I would like to put anything
(or almost anything) in =code= markup, for instance (my use case: Emacs
keybindings, try =C-x ,= - Org won't recognize it as code!). I could
mess up with org-emphasis-regexp-components in e.g. file local
variables, but this is far from clean.
Maybe a good solution would be to allow two syntaxes for markup:
"short", like *bold* or =code=, and "long", like \textbf{bold} and
\verb|code|. If it is decided that such LaTeX-like syntax is fine, we
could only introduce escaping of backslash and curly braces, which seems
a decent compromise.
We could even use LaTeX-like constructs like \textbf, but with
\verb-like delimitation by two identical characters not present in the
text itself. We might also use a convention that if the character right
after \textbf is an opening paren of some kind - the syntax table might
be reused for that - then we expect a closing one at the end, and if
not, we expect an identical one at the end. This way, we could say
\textbf{Boldface} and \verb{verbatim}
but also
\textbf|{boldface in curly braces}| and \verb|C-x {|
etc. This way only the backslash needs escaping.
There are a lot of possibilities, and plenty of time to settle on the
best one.
> Thanks,
> eric
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-10-25 16:19 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 13:08 Some projects Nicolas Goaziou
2015-10-25 14:43 ` Marcin Borkowski
2015-10-25 16:11 ` Nicolas Goaziou
2015-10-25 15:45 ` Eric S Fraga
2015-10-25 16:16 ` Nicolas Goaziou
2015-10-25 16:18 ` Marcin Borkowski [this message]
2015-10-25 16:37 ` Nicolas Goaziou
2015-10-25 18:13 ` Marcin Borkowski
2015-10-25 18:24 ` Nicolas Goaziou
2015-10-25 17:57 ` Thomas S. Dye
2015-10-25 18:00 ` Fabrice Popineau
2015-10-25 18:12 ` Nicolas Goaziou
2015-10-25 18:22 ` Eric S Fraga
2015-10-25 19:12 ` Marcin Borkowski
2015-10-25 19:11 ` Marcin Borkowski
2015-10-25 21:18 ` Anders Johansson
2015-10-25 21:29 ` Anders Johansson
2015-10-25 19:33 ` Thomas S. Dye
2015-10-25 20:00 ` Nicolas Goaziou
2015-10-25 20:17 ` Thomas S. Dye
2015-10-25 20:03 ` Nicolas Goaziou
2015-10-25 19:02 ` Rasmus
2015-10-25 19:20 ` Marcin Borkowski
2015-10-26 2:23 ` Matt Price
2015-10-25 20:24 ` Samuel Wales
2015-10-25 20:25 ` Samuel Wales
2015-10-25 23:03 ` Aaron Ecay
2015-10-26 8:13 ` Marcin Borkowski
2015-10-26 9:20 ` Rasmus
2015-10-26 16:39 ` Richard Lawrence
2015-10-26 18:17 ` Nicolas Goaziou
2015-10-26 22:23 ` Richard Lawrence
2015-10-27 0:03 ` Matt Price
2015-10-27 12:01 ` Aaron Ecay
2015-10-27 12:34 ` Rasmus
2015-10-27 13:03 ` Aaron Ecay
2015-10-27 13:51 ` Rasmus
2015-10-28 1:05 ` Matt Price
2015-10-28 3:28 ` Aldric Giacomoni
2015-10-28 3:31 ` Matt Lundin
2015-10-28 14:36 ` Matt Price
2015-10-28 15:31 ` Matt Price
2015-10-28 1:05 ` Matt Price
2015-10-27 13:19 ` Rainer M Krug
2015-10-27 13:42 ` Rasmus
2015-10-27 14:49 ` Ista Zahn
2015-10-27 15:09 ` Rasmus Pank Roulund
2015-10-27 15:25 ` Ista Zahn
2015-10-27 15:36 ` Rainer M Krug
2015-10-28 2:52 ` Matt Lundin
2015-10-27 13:22 ` Richard Lawrence
2015-10-28 1:57 ` Matt Lundin
2015-10-28 8:56 ` Rasmus
2015-10-28 9:07 ` Rasmus
2015-10-26 17:20 ` Eric Abrahamsen
2015-10-27 8:30 ` Nicolas Goaziou
2015-10-27 18:53 ` Eric Abrahamsen
2015-10-27 19:23 ` Rasmus
2015-10-27 20:28 ` Eric Abrahamsen
2015-10-27 20:01 ` Marcin Borkowski
2015-10-27 21:53 ` Nicolas Goaziou
2015-10-26 18:20 ` Kaushal Modi
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=87io5uzzv6.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=e.fraga@ucl.ac.uk \
--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).