From: "Gustav Wikström" <gustav.erik@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Skip Collins <skip.collins@gmail.com>,
emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: unintended strike-through in table
Date: Sat, 21 Apr 2012 11:04:23 +0200 [thread overview]
Message-ID: <CA+SyOP88fEGrbvwKkwV8O7_zSqD3ri5XLAWcP3-UMmwGWFJCGw@mail.gmail.com> (raw)
In-Reply-To: <87ty0egfob.fsf@altern.org>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
On Sat, Apr 21, 2012 at 1:13 AM, Bastien <bzg@altern.org> wrote:
> Hi Skip,
>
> Skip Collins <skip.collins@gmail.com> writes:
>
> > I see little reason to continue to support +strike-through+ text.
> > Perhaps the simplest solution would be to deprecate stricken text and
> > disable it by default, allowing for an option to turn it on for
> > backward compatibility.
>
> I agree. If no one object, I will make this change soon.
>
> Although I cannot recall myself having used strike-through text I wonder
what the reason is for removing the functionality? Is it just this, that it
(probably) isn't used much? Not a good argument in my book (especially due
to the uncertainty in usage). Would it not be better to fix the problem at
hand? Maybe by changing the symbol since + seems overloaded, would not - be
a better choice?
On a side-note, what is the intended behavior of bold, italic,
strike-through etc. regarding line-breaks? Since a single long line has the
same meaning in org as multiple consecutive short lines I think the
markup-elements above also should support multiple lines of text (but not
be valid between paragraphs)
Regards Gustav
[-- Attachment #2: Type: text/html, Size: 1701 bytes --]
next prev parent reply other threads:[~2012-04-21 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 18:27 unintended strike-through in table Skip Collins
2012-04-20 23:13 ` Bastien
2012-04-21 9:04 ` Gustav Wikström [this message]
2012-04-21 14:35 ` Rasmus
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=CA+SyOP88fEGrbvwKkwV8O7_zSqD3ri5XLAWcP3-UMmwGWFJCGw@mail.gmail.com \
--to=gustav.erik@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=skip.collins@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).