emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: orgtbl-mode and markdown
Date: Thu, 20 Dec 2012 09:01:53 +0100	[thread overview]
Message-ID: <417EF3F0-EB5E-4EE2-B800-FA2C9C7B6E43@gmail.com> (raw)
In-Reply-To: <87a9tbi6r0.fsf@Rainer.invalid>


On 18.12.2012, at 18:56, Achim Gratz <Stromeko@nexgo.de> wrote:

> Carsten Dominik writes:
>> Well this is very safe - but if you have to assume that every elisp
>> command does change match data behind your back, you would have to
>> create a lot of extra code.
> 
> Stefan Monnier advises the opposite (quote from
> http://article.gmane.org/gmane.emacs.bugs/68688 ):
> 
> --8<---------------cut here---------------start------------->8---
>> Okay.  On second though: it wouldn't be very useful to use the match
>> data set by these functions.  Why not save the match-data here once so
>> that no caller has to ever worry about it?  Is there a general policy
>> that this kinda thing shouldn't be done?
> 
> Yes, the general policy is: all functions should be presumed to trash
> the match-data, except for a very few exceptions.
> --8<---------------cut here---------------end--------------->8---

I am sure that Stefan would consider backward-delete-charater
such an exception, if you ask him directly.

- Carsten

> 
> 
> Regards,
> Achim.
> -- 
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
> 
> SD adaptation for Waldorf rackAttack V1.04R1:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
> 
> 

  reply	other threads:[~2012-12-20  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18  8:33 orgtbl-mode and markdown Vegard Vesterheim
2012-12-18 13:07 ` Carsten Dominik
2012-12-18 13:39   ` Vegard Vesterheim
2012-12-18 14:50     ` Carsten Dominik
2012-12-18 17:56       ` Achim Gratz
2012-12-20  8:01         ` Carsten Dominik [this message]
2012-12-21 10:53           ` Carsten Dominik
2012-12-23 16:33             ` Bastien

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=417EF3F0-EB5E-4EE2-B800-FA2C9C7B6E43@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=Stromeko@nexgo.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).