emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Date: Sat, 22 Mar 2014 15:54:15 +0100	[thread overview]
Message-ID: <87r45uthbc.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87txaqmhzd.fsf@bzg.ath.cx

Hi all,

Bastien <bzg@gnu.org> writes:

[ ...]

>
> Also, there is no "backward-compatibility squad", only users who care
> about what they like.

I have been part in threads that discuss backward-compatibility.  As it
looks, there is the feeling that this ML is too(?) much concerned about
backward-compatibility -- even in favour over new features or cleaner
implementation (both of which the proposed emphasis change would be an
example of, IIUC).

In a way, I am happy that backward-compatibility is now a major
concern.  But on the other hand, it is not my intention to block
enhancements.

For the case at hand, I would happily type double letter emphasis, if
that helps to get a clean implementation.  If it even allows more
features, that would be a benefit.

My point of writing is this:  If a change like this was going to happen,
it would be very nice if a function was provided to change from the old
style to the new style.  This was (at least) once the case for a major
backward incompatible change in babel and even if it did not work
flawlessly it was a big help.
I guess it would be easy for the lisp-guru who removes the regexp to
turn it into such a function.  But it would take quite some time for me
to dig that regexp somewhen later and produce a working translation
function from it...

Anyway, as it looks this is probably hypothetical for this particular
change.

Regards,
Andreas

  reply	other threads:[~2014-03-22 14:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 13:11 [RFC] Creole-style / Support for **emphasis**__within__**a word** Jambunathan K
2014-03-04 14:55 ` Jambunathan K
2014-03-22 14:05 ` Nicolas Goaziou
2014-03-22 14:21   ` Bastien
2014-03-22 14:54     ` Andreas Leha [this message]
2014-03-22 15:22       ` Bastien
2014-03-22 15:30     ` Nicolas Goaziou
2014-03-22 15:37       ` Bastien
2014-03-23  0:53         ` Samuel Wales
2014-03-23  0:06       ` Marcin Borkowski
2014-03-23 11:32         ` Suvayu Ali
2014-03-23 11:39           ` Marcin Borkowski
2014-03-23  2:59   ` Jambunathan K
2022-01-24 10:50     ` [O] " Vincent Belaïche
2022-01-24 11:54       ` Nicolas Goaziou
2022-01-24 12:09       ` [O] " Juan Manuel Macías
2022-01-24 12:32         ` Vincent Belaïche
2022-01-25 10:55           ` Nicolas Goaziou
2022-01-25 17:18             ` Vincent Belaïche
2022-01-25 17:30               ` Juan Manuel Macías
2022-01-25 18:45                 ` Vincent Belaïche
2022-01-25 17:52               ` Nicolas Goaziou
2022-01-25 18:20               ` Vincent Belaïche
2022-01-25 16:27           ` Max Nikulin
  -- strict thread matches above, loose matches on Subject: below --
2014-03-04 13:00 Jambunathan K
2014-03-04 12:56 Jambunathan K

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=87r45uthbc.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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).