emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Samuel Wales <samologist@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Survey: changing a few default settings for Org 9.4
Date: Wed, 19 Feb 2020 21:15:53 +0100	[thread overview]
Message-ID: <87v9o2s58m.fsf@mbork.pl> (raw)
In-Reply-To: <CAJcAo8uVVOi5OmUYmKZADdSHpgT33EKOnuOBbdZ1uCqL8Pz=kA@mail.gmail.com>


On 2020-02-19, at 21:02, Samuel Wales <samologist@gmail.com> wrote:

> just an idea but changing the subscript and superscript export feature
> to ‘{}’ would reduce accidental invocation.  i have seen solecistic
> subscripts on websites created with org (probably by experts who
> babelize their .emacs!), and on this ml :).
>
> i have seen it used accidentally more than i have seen it used for its
> intended purpose.  {} seems more unambiguous.
>
> that would, of course, be an issue for those who already have a lot of
> the short form in their technical and scientific papers.
>
> so there would have to be a nice regexp fixer.  or a warning.

+1!!!

There is already an option for that (~org-use-sub-superscripts~).
Changing the default to `{} seems a great idea.

Best,

-- 
Marcin Borkowski
http://mbork.pl

  reply	other threads:[~2020-02-19 20:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19  7:39 Survey: changing a few default settings for Org 9.4 Bastien
2020-02-19  8:57 ` Samuel Wales
2020-02-19  9:01   ` Bastien
2020-02-19 20:02   ` Samuel Wales
2020-02-19 20:15     ` Marcin Borkowski [this message]
2020-02-19 21:35       ` Bastien
2020-02-19 22:06         ` Samuel Wales
2020-02-19 11:03 ` Marco Wahl
2020-02-19 11:41   ` Bastien
2020-02-19 13:21     ` Marco Wahl
2020-02-19 13:39       ` Bastien
2020-02-19 17:57         ` Marco Wahl
2020-02-19 20:44           ` Bastien
2020-02-20  4:11       ` Adam Porter
2020-02-19 11:30 ` Nicolas Goaziou
2020-02-19 11:57   ` Bastien
2020-02-19 14:07     ` Nicolas Goaziou
2020-02-19 17:24       ` Bastien
2020-02-19 23:23         ` Vladimir Lomov
2020-02-19 23:53           ` Bastien
2020-02-20  0:20             ` Samuel Wales
2020-02-19 12:58   ` Tim Cross
2020-02-19 13:22     ` Bastien
2020-02-19 15:06       ` Tim Cross
2020-02-19 13:03   ` AW
2020-02-19 15:41 ` Matthew Lundin
2020-02-19 16:16   ` Joost Kremers
2020-02-19 17:13     ` Bastien
2020-02-19 16:50   ` Detlef Steuer
2020-02-19 17:14     ` Bastien
2020-02-20  4:07 ` Adam Porter
2020-02-20  7:10   ` Bastien
2020-02-20 14:10     ` Kaushal Modi
2020-02-21 15:49 ` Bastien
2020-02-21 19:36   ` Diego Zamboni
2020-02-21 21:28     ` Archenoth
2020-02-22  9:38       ` Bastien
2020-02-22 12:45         ` Nicolas Goaziou
2020-02-22 13:31           ` Bastien
2020-02-22 18:57           ` Archenoth
2020-03-18  2:20 ` Mark E. Shoulson
2020-03-18  8:58   ` Norman Tovey-Walsh
2020-03-18 20:47     ` Hiding emphasis markers Mark E. Shoulson
2020-05-22 16:47       ` Bastien

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=87v9o2s58m.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@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).