emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rustom Mody <rustompmody@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Escaping again!
Date: Fri, 30 May 2014 20:14:29 +0530	[thread overview]
Message-ID: <CAJ+TeoeF4UanNZcYVcRdA6pANxdFNW1EHAbE8w6QwpMTFHAq8w@mail.gmail.com> (raw)
In-Reply-To: <87ha478iyd.fsf@bzg.ath.cx>

[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]

Hi Bastien

On Fri, May 30, 2014 at 7:30 PM, Bastien <bzg@gnu.org> wrote:

> Hi Rustom,
>
> Rustom Mody <rustompmody@gmail.com> writes:
>
> > - \(+\):: Int → Int → Int
> > - \(-\):: Int → Int →Int
> > - \(\leq\):: Int → Int → Bool
> > - \(=\):: Int → Int → Bool
>
> 1. \(+\) :: Int → Int → Int
> 2. \(-\) :: Int → Int →Int
> 3. \(\leq\) :: Int → Int → Bool
> 4. \(=\) :: Int → Int → Bool
>
> would do -- but this is not entirely satisfactory.
>
> For now description lists accept both "-" and "+".  I'm all for
> allowing only "-" so that we could use
>
> + \(+\) :: Int → Int → Int
> + \(-\) :: Int → Int →Int
> + \(\leq\) :: Int → Int → Bool
> + \(=\) :: Int → Int → Bool
>
> in your example.
>
> What do you and others think?
>
>
If you are asking me about a proposed change, I thank you for the
consideration :-)

Please dont take the following too seriously -- I am just spoilt by the
fact that I am an old programmer.

Here is a command I ran on the org sources and its output:

$ grep -r '\\\\\\\\\\\\\\\\\\\\' .
./contrib/lisp/ox-groff.el:          "\\(\\\\\\\\\\)?[ \t]*\n" ".br\n"
output)))


./lisp/ox-latex.el:            "\\(\\\\\\\\\\)?[ \t]*\n" " \\\\\\\\\n"
output)))
./lisp/ox-latex.el:              "\\(\\\\\\\\\\)?[ \t]*\n" " \\\\\\\\\n"
contents)))
./lisp/ox-odt.el:            "\\(\\\\\\\\\\)?[ \t]*\n" "<text:line-break/>"
output t)))
./lisp/ox-man.el:      (setq output (replace-regexp-in-string
"\\(\\\\\\\\\\)?[ \t]*\n" ".br\n"
./lisp/ox-html.el:         "\\(\\\\\\\\\\)?[ \t]*\n"
./lisp/ox-html.el:           "\\(\\\\\\\\\\)?[ \t]*\n"
./lisp/ox-texinfo.el:            "\\(\\\\\\\\\\)?[ \t]*\n" " @*\n" output)))
./lisp/ox-texinfo.el:             "\\(\\\\\\\\\\)?[ \t]*\n" " \\\\\\\\\n"
contents)))
./lisp/org.el:    (looking-at "\\\\\\\\\\($\\|[^\\\\]\\)")))

So sometimes we need that much ESCAPE-ing.

I realise that the general support for escaping in org is much harder than
in a programming language like lisp because there are so many different
contexts and different entities to escape.

However I would also like to humbly submit that if one doesn't have
systematic general escaping, there will always be legitimate uses that will
not be addressable.

Anyways… if you are doing this just for me (!) very kind of you!
For now I am getting along using '꞉' (Unicode 0xA789).

Regards,
Rusi

-- 
http://blog.languager.org

[-- Attachment #2: Type: text/html, Size: 3706 bytes --]

  reply	other threads:[~2014-05-30 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 13:33 Escaping again! Rustom Mody
2014-05-30 14:00 ` Bastien
2014-05-30 14:44   ` Rustom Mody [this message]
2014-05-30 15:15     ` Loyall, David
2014-05-30 15:23     ` Bastien
2014-05-30 16:37       ` Rustom Mody
2014-05-30 17:27         ` Nick Dokos
2014-05-30 22:19           ` Bastien
2014-06-01  8:44   ` Nicolas Goaziou
2014-07-28  8:58     ` Bastien
2014-06-01 12:57   ` Gregor Zattler
2014-06-01 13:47     ` Nicolas Goaziou

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=CAJ+TeoeF4UanNZcYVcRdA6pANxdFNW1EHAbE8w6QwpMTFHAq8w@mail.gmail.com \
    --to=rustompmody@gmail.com \
    --cc=bzg@gnu.org \
    --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).