From: John Hendy <jw.hendy@gmail.com>
To: James Harkins <jamshark70@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [export] Easy way to make children of Beamer frames generate list items?
Date: Sat, 14 Sep 2013 21:49:18 -0500 [thread overview]
Message-ID: <CA+M2ft_gb0RW2hpBKVj6dxX0QPDoSA=g0U6qD4Y=CVev8uv_sQ@mail.gmail.com> (raw)
In-Reply-To: <loom.20130915T041533-719@post.gmane.org>
On Sat, Sep 14, 2013 at 9:16 PM, James Harkins <jamshark70@gmail.com> wrote:
> Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:
>
>> I think it is unwise to keep coming up with ways to support semantically
>> wrong behaviour just for the sake of backwards compatibility. This was
>> changed with good reason and after a lot of discussions. If you
>> continue on this path, you will have to keep maintaining this yourself
>> for all eternity (sorry about the hyperbole :-p). It's a lot of work
>> for a long time just to avoid some annoying work now.
>
I mostly agree, but as others are noting some of us had months and
months worth of presentations in the old format, so it's not always
trivial to update and old .org file and re-export. I don't think we
need to semantically (or syntactically?) support the old behavior (I
wouldn't say wrong), but it's worth coming up with solutions for those
who especially aren't using git or quasi-frequent snapshots.
Keep in mind that a majority of users may very well be using
distro-specific releases. I have no idea how, say, Ubuntu's releases
compare to Org's.
In any case, I'm mostly in agreement that Org's changed and thus the
file structure should change... but not all of us use the git and/or
snapshot Org version with regular frequency and thus I expect a fair
amount of trickling in of users surprised at the incompatibility.
John
> FWIW, I hit this issue about half a year ago, and argued pretty strenuously
> that breaking backward compatibility was a Terrible Terrible Thing. But,
> having adapted to the new markup spec, I find it's more logically consistent
> *and* easier to read while editing.
>
> I still have a semester's worth of class slides to convert from the old
> format, week by week, but it's worth it -- do it once per presentation, and
> that's the end of it.
>
> The new way really is better (I say this as someone who was horrified six
> months ago to find that my old presentations were broken).
>
> hjh
>
>
next prev parent reply other threads:[~2013-09-15 2:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 14:28 [export] Easy way to make children of Beamer frames generate list items? Christoph LANGE
2013-09-14 14:40 ` John Hendy
2013-09-14 15:15 ` Suvayu Ali
2013-09-15 2:16 ` James Harkins
2013-09-15 2:49 ` John Hendy [this message]
2013-09-15 10:57 ` Suvayu Ali
2013-09-15 11:07 ` Christoph LANGE
2013-09-15 11:41 ` Carsten Dominik
2013-09-15 12:42 ` Suvayu Ali
2013-09-17 19:59 ` Christoph LANGE
2013-09-15 14:48 ` John Hendy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+M2ft_gb0RW2hpBKVj6dxX0QPDoSA=g0U6qD4Y=CVev8uv_sQ@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.