emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [export] Easy way to make children of Beamer frames generate list items?
Date: Sun, 15 Sep 2013 09:48:54 -0500	[thread overview]
Message-ID: <CA+M2ft9H2Ff7zPUee5W4eQ_2Ntfnc=U+CcEWwm1FjRqf_5AqtA@mail.gmail.com> (raw)
In-Reply-To: <20130915105749.GN28088@kuru.dyndns-at-home.com>

On Sun, Sep 15, 2013 at 5:57 AM, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> On Sat, Sep 14, 2013 at 09:49:18PM -0500, John Hendy wrote:
>>
>> 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.
>
> As I outlined towards the end of my earlier message, it is not possible
> (at least easily with some config magic) to get back the old behaviour
> with the new exporter.  Maybe then we should have an FAQ stating so and
> outlining how one could make the format switch (again, a possible path
> provided in my previous message).
>

My response was geared toward "Is there a handy workaround in the mean
time so that Christoph can get quicker access to his materials" than
"Can we program Org-mode to handle all legacy forms of input to the
exporter." Sorry if it seemed that I was requesting an "official" fix.
It was more of a prompt for someone clever with LaTeX and/or the new
exporter guts to possibly give him some magic to convert lower
headlines to list while he changes over vs. simply saying, "No. You
can't do that."

Now I understand it really just isn't possible at all, and that's a
good answer to have as well :)

> Do you think that would be a good idea?  If so, I'll add a short FAQ
> with a pointer to this thread for now.  We can clean it up later.

I'm not sure on this. I was thinking about your answer some more, and
perhaps I'm trying to be empathetic with those who aren't subscribed
to the mailing list and thus weren't submerged in constant discussions
about the new exporter, opportunities to try it on an experimental
branch, tons of warnings that "it's coming," and so on. Then again, I
countered myself with realizing that it's not like extreme computer
novices are installing this on a daily basis -- each of us probably
had to stumble on it when looking for outlining program alternatives,
either already knew or endured Emacs to use Org (like me), and are
aware of things like mailing lists and StackOverflow.

So... maybe my concern is unfounded. Org users are most likely more
familiar than many with reading manuals/help files, seeking help, etc.
I think there's a decent amount out there about the new exporter, but
it can seem a bit scattered between the manual and Worg. When I wanted
to constantly refer back to the upgrade instructions page that
Bastien/Nicolas created, I was constantly googling "upgrade Org 8.0."
At the time, I don't think it worked with just "upgrade" and no
version. So things like that make me wonder how easy it is to find
these things without sort of knowing where they are.

Alright -- enough wind out of me. All that said, yes, more info and
references/links can't hurt. That's probably the most helpful thing
for newcomers/non-mailing-list people -- something smack-dab on the
Org-mode webpage about FAQs or troubleshooting.


Thanks for the explanations and dialog!
John

>
> Cheers,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>

      parent reply	other threads:[~2013-09-15 14: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
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 [this message]

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='CA+M2ft9H2Ff7zPUee5W4eQ_2Ntfnc=U+CcEWwm1FjRqf_5AqtA@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@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 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).