From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problem exporting code
Date: Tue, 22 Jan 2013 18:37:03 +0100 [thread overview]
Message-ID: <87sj5tglvk.fsf@Rainer.invalid> (raw)
In-Reply-To: m1ip6p7lbt.fsf@tsdye.com
Thomas S. Dye writes:
> Interesting, this Emacs distribution removed Org a few days ago. I'm not
> certain why the distributor refers to this as "a rather drastic
> measure." From my perspective as a user, whose interests required using
> the git version of Org from the beginning, the Emacs distribution of Org
> has been nothing but trouble, leading to perplexing (for me) problems
> with mixed installs that I would rather have avoided.
That's not an entirely fair thing to say. Using an Emacs with a built-in
Org version just makes some problems more prominent that maybe you got
away with in the past.
> Installation of the git version is *easy* now, even for someone with my
> limited skills. I didn't have any luck with the ELPA version when it
> first came out, but the ELPA system works great and it seems like an
> ideal channel to distribute Org. So, even a user like me has very little
> difficulty using a non-Emacs version of Org.
Package manager, ELPA and the way it interacts with Emacs' built-in
packages certainly needs some more work. Right now things might be a
little more rough than everybody would like.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2013-01-22 17:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 23:44 Problem exporting code Ken Williams
2013-01-21 0:31 ` Ken Williams
2013-01-21 3:15 ` Eric S Fraga
2013-01-21 4:57 ` Ken Williams
2013-01-21 5:36 ` John Hendy
2013-01-21 5:38 ` John Hendy
2013-01-21 6:05 ` Ken Williams
2013-01-21 7:39 ` Eric S Fraga
2013-01-21 15:58 ` Ken Williams
2013-01-21 16:48 ` John Hendy
2013-01-21 17:45 ` Ken Williams
2013-01-21 22:16 ` John Hendy
2013-01-21 22:51 ` Ken Williams
2013-01-22 0:14 ` Thomas S. Dye
[not found] ` <CA+M2ft_nyHsjC3V0FPvL+NbYBTP1FGKLqF0=miX09uByhS_oKA@mail.gmail.com>
2013-01-22 2:48 ` Ken Williams
2013-01-22 7:01 ` Thomas S. Dye
2013-01-22 7:49 ` Bastien
2013-01-22 11:13 ` Thorsten Jolitz
2013-01-22 11:54 ` Bastien
2013-01-22 12:58 ` Thorsten Jolitz
2013-01-22 19:45 ` Thorsten Jolitz
2013-01-22 21:41 ` Bastien
2013-01-22 13:02 ` Ken Williams
2013-01-22 13:10 ` Bastien
2013-01-22 17:44 ` Achim Gratz
2013-01-22 21:41 ` Bastien
2013-01-22 17:37 ` Achim Gratz [this message]
2013-01-22 19:39 ` Thomas S. Dye
2013-01-23 7:27 ` Achim Gratz
2013-01-21 23:43 ` Eric S Fraga
2013-01-21 6:11 ` Ken Williams
2013-01-21 5:52 ` Ken Williams
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=87sj5tglvk.fsf@Rainer.invalid \
--to=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).