From: "Eric Schulte" <schulte.eric@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Chris Maier <christopher.maier@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>,
Dan Davison <dandavison7@gmail.com>
Subject: Re: Re: [BABEL] Editing dot blocks with org-exp-blocks
Date: Thu, 10 Feb 2011 10:02:10 -0700 [thread overview]
Message-ID: <87lj1nn7ql.fsf@gmail.com> (raw)
In-Reply-To: <87tygci4rx.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 10 Feb 2011 10:05:06 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> "Eric Schulte" <schulte.eric@gmail.com> writes:
>
> [...]
>
>>
>> I also vote for removing the dot and ditaa block types from
>> org-exp-blocks, left over from before the existence of begin_src blocks.
>> As the original developer of org-exp-blocks, I no longer maintain it in
>> favor of focusing on begin_src blocks.
>>
>> The only downside to removing these block types is breaking existing
>> Org-mode files... Perhaps we could add a deprecation warning which will
>> appear as a message every time a begin_dot or begin_ditaa blocks is
>> evaluate, then after a month or so of warning we can remove those blocks
>> entirely.
>>
>> Thoughts? -- Eric
>
> Completely in favour ...
>
> ... so long as the message either provides a clear description of how to
> change from =begin_X= to =begin-src X= or gives a link to this clear
> description in the manual, say. I haven't changed the various begin_X
> blocks yet because of the uncertainty in the mapping from one to the
> other... and because I've been lazy, I guess ;-)
Alright, I've just pushed up such deprecation warnings. They instruct
the user to switch e.g., begin_dot to begin_src dot. Hopefully this is
sufficient. I suppose the responsible thing to do now is to wait
through an entire release cycle, and then two releases from now the
functions can be removed.
Cheers -- Eric
next prev parent reply other threads:[~2011-02-10 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 3:50 [BABEL] Editing dot blocks with org-exp-blocks Chris Maier
2011-02-09 8:56 ` Eric S Fraga
2011-02-09 13:31 ` Chris Maier
2011-02-09 14:10 ` Eric S Fraga
2011-02-09 15:14 ` Dan Davison
2011-02-09 15:39 ` Chris Maier
2011-02-09 16:14 ` Dan Davison
2011-02-10 2:05 ` Chris Maier
2011-02-10 1:05 ` Eric Schulte
2011-02-10 10:05 ` Eric S Fraga
2011-02-10 17:02 ` Eric Schulte [this message]
2011-02-09 8:58 ` Sébastien Vauban
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=87lj1nn7ql.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=christopher.maier@gmail.com \
--cc=dandavison7@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).