From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Date: Sun, 23 Mar 2014 12:39:23 +0100 [thread overview]
Message-ID: <20140323123923.5e11a746@aga-netbook> (raw)
In-Reply-To: <20140323113246.GC7474@chitra.dyndns-at-home.com>
Dnia 2014-03-23, o godz. 12:32:46
Suvayu Ali <fatkasuvayu+linux@gmail.com> napisał(a):
> On Sun, Mar 23, 2014 at 01:06:35AM +0100, Marcin Borkowski wrote:
> > Dnia 2014-03-22, o godz. 16:30:31
> > Nicolas Goaziou <n.goaziou@gmail.com> napisał(a):
> >
> > > > Also, there is no "backward-compatibility squad", only users who
> > > > care about what they like.
> > >
> > > That is what they want us to believe! :)
> >
> > Ninja'd!
> >
> > Re: topic: one idea that is maybe not very Org-ish, but seems
> > reasonable: Org already uses LaTeX syntax for sub/superscripts, and
> > accepts LaTeX snippets etc. Why not allow \textbf{something}
> > parallel to *something*? Would it break something? When using the
> > LaTeX exporter, currently it seems (from very few simple
> > experiments), that \textbf{whatever} copies "whatever" verbatim to
> > the file (I tried LaTeX and HTML exporters).
>
> Often LaTeX users tend to forget (including myself) one of Org's
> features is to be able to export to different backends without major
> modifications to the source file (.org file).
>
> Your proposal breaks that.
No, it doesn't. What I meant was to make Org *recognize* the
\textbf{...} etc. syntax and *convert* it to <strong> ... </strong> and
similar things (depending on the backend). Sorry if I wasn't clear
enough.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
next prev parent reply other threads:[~2014-03-23 11:39 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
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 [this message]
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=20140323123923.5e11a746@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--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).