From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Gustav_Wikstr=F6m?= Subject: Re: unintended strike-through in table Date: Sat, 21 Apr 2012 11:04:23 +0200 Message-ID: References: <87ty0egfob.fsf@altern.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=14dae934048df5041104be2cb038 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41876) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLWF4-00010A-Au for emacs-orgmode@gnu.org; Sat, 21 Apr 2012 05:04:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SLWEz-0002CZ-PT for emacs-orgmode@gnu.org; Sat, 21 Apr 2012 05:04:29 -0400 Received: from mail-iy0-f169.google.com ([209.85.210.169]:32912) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLWEz-0002CP-HV for emacs-orgmode@gnu.org; Sat, 21 Apr 2012 05:04:25 -0400 Received: by iajr24 with SMTP id r24so17971052iaj.0 for ; Sat, 21 Apr 2012 02:04:23 -0700 (PDT) In-Reply-To: <87ty0egfob.fsf@altern.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Skip Collins , emacs-org list --14dae934048df5041104be2cb038 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Apr 21, 2012 at 1:13 AM, Bastien wrote: > Hi Skip, > > Skip Collins 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 --14dae934048df5041104be2cb038 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sat, Apr 21, 2012 = at 1:13 AM, Bastien <bzg@altern.org> wrote:
Hi Skip,

Skip Collins <skip.collins@gma= il.com> writes:

> I see little reason to continue to support +strike-through+ text.
> Perhaps the simplest solution would be to deprecate stricken text and<= br> > disable it by default, allowing for an option to turn it on for
> backward compatibility.

I agree. =A0If no one object, I will make this change soon.

Although I cannot r= ecall myself having used strike-through text I wonder what the reason is fo= r 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 uncertain= ty in usage). Would it not be better to fix the problem at hand? Maybe by c= hanging the symbol since + seems overloaded, would not - be a better choice= ?

On a=A0side= -note, what is the intended behavior of bold, italic, strike-through etc. r= egarding 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 Gus= tav
--14dae934048df5041104be2cb038--