From: Thorsten Jolitz <tjolitz@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Problem exporting code
Date: Tue, 22 Jan 2013 12:13:11 +0100 [thread overview]
Message-ID: <87wqv5wjw8.fsf@googlemail.com> (raw)
In-Reply-To: 87wqv5irnp.fsf@bzg.ath.cx
Bastien <bzg@altern.org> writes:
Hi Bastien,
your post touches two topics that I'm currently dealing with, so here
are two questions with regards to this topics:
(1)
>> 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.
>
> The distribution of Org as a built-in package in Emacs is *not* the
> problem.
>
> Installing Org through git or through .tar.gz/.zip on top of the Emacs
> distribution does not create problems if you follow the instructions
> in the manual -- I made a special effort to simplify them.
I recently experienced some casual trouble when updating Org-mode from
Git (I simply updated at a moment, when actual org.el wouldn't load due to a
bug that was to be fixed soon fixed soon. Here is the related thread on
the mailing list:
[[gnus:nntp%2Bnews.gmane.org:gmane.emacs.orgmode#87ehhmnqu6.fsf@googlemail.com][Email from Thorsten Jolitz: Re: {BUG} `org-load-noerror-m]]
In this thread, I was told that I'm causing 'a future train wreck' with
my habit to simply trash the org folder from the Emacs installation and
replace it with a symlink to the git version in my home dir (I had
enough trouble with mixed installs, and this seems to avoid them -
having only the git version, no Elpa and no Emacs version).
Now I was told there will be troubles with the autoloads, and I would
like to understand better what the possible implications are. I do 'make
autoloads' in the git version of org, so there is a loaddefs.el. There
is of course another loaddefs.el in the Emacs directory that is not
updated when I replace the Emacs org folder with a symlink to the
(slightly different) git version.
Is there really 'big trouble' possible due to this? Should I run 'make
autoloads' in the Emacs installation directory again?
(2)
> Also, I consider outline.el to be completely unusable, and Org is
> first an enhanced version of it, which Emacs strongly needs. I plan
> to push so that files in Emacs use org.el when they use outline.el.
When I started with Emacs, I had one .emacs init-file that became more
and more chaotic over time (and a real pain for navigation and
maintainment). Then I started to use a multi-file set-up, first Elisp
files, then using .org files via the starter-kit.
Now I know about M-x occur and recently discovered that
outline-minor-mode enables me to define my own outline-regexps in an .el
file, so I'm back to the start - using one big /.emacs.d/init.el, but
this time with all the outline functionality.
Here is a short excerpt from the init.el, showing that my
outline-headings just look like outcommented org-headings:
,----------------------------------------------------
| ;; * Recovery from Problems
|
| ;; ** Debugging
|
| (when section-debugging (message "99 Debugging...")
|
| ...
|
| (message "99 Debugging... Done"))
|
| ;; Local Variables:
| ;; coding: utf-8
| ;; mode: emacs-lisp
| ;; eval: (outline-minor-mode)
| ...
| ;; outline-regexp: ";; [*]+ "
| ;; End:
`----------------------------------------------------
Except for the extraordinary weird key-bindings of outline-minor-mode
(e.g. C-c @ C-n), that I still did not manage to override (with the
usual Org-mode bindings), I'm very satisfied with this set-up, it gives
me the best of both worlds (full outline functionality and the very
simple and direct approach of having just one init.el).
Why do you consider outline(-minor-mode) as completely unusable? And how
would you replace it in my use case with org(-struct?)? I'm asking just
out of curiosity, and to learn a bit more, there are no urgent problems
to be solved on my side here.
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-01-22 11:13 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 [this message]
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
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=87wqv5wjw8.fsf@googlemail.com \
--to=tjolitz@googlemail.com \
--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).