changed:
-
This page has updates for an Emacs package i develop and use, the Allout outline editing mode.
Emacs is a free, extremely capable text editor, `used principally by
programmers`_ (and revered by some of them, including me). One outstanding
strength is its broad extensibility - many people contribute, extending and
polishing the functionality. I've developed an extension of my own, Allout mode, for editing and navigating outlines. I use it extensively, and Allout has been adopted as an alternative outliner in both emacs variants - the mainline GNU `Emacs <http://directory.fsf.org/emacs.html>`_ and the prominent fork, `!XEmacs <http://xemacs.org/>`_.
See the AlloutNEWS file for the differences between this version and the
one released with Emacs 21. (The new version is being included with Emacs
22.)
I'm also working in earnest on a cooperative extension for Allout,
`allout-widgets.tgz`_, which presents the structure with easier-to-track
graphics. The real reason for it is as a platform for some exploration i'd
like to do of "spherical" outlining, where items can exist in multiple
places and their structure is qualified according to their containment
context. I'll say more about this as it develops.
The table below indicates the components you'll need, with '+' plus signs
for the emacs versions where you'll need to add them. With all the
necessary ingredients, i see everything including encryption work in all of
the indicated versions. When the dust settles, the shaken-out allout
version will be included in the Emacs 22 and !XEmacs distributions.
Migration of the newer pgg code to XEmacs is in the works, as well.
There is an `Emacs Wiki page on allout`_, including some background info,
links to this page, contributed guidance, and so forth.
Look below the table for some questions and comments concerning recent
changes.
+----------------+----------------------------+---------------------------------+
| Version | Artifacts | Notes |
+----+----+------+ | |
|Ema\|Ema\|!XEma\| | |
|cs |cs |cs | | |
|22 |21 |21 | | |
| | | | | |
+====+====+======+============================+=================================+
|\+ |\+ | \+ | - `allout.el`__ |The allout lisp code, version |
| | | | - AlloutChangeLog |2.2.1 (rev 1.277 Feb 2008), |
| | | | - AlloutNEWS |plus change history documents. |
| | | | | |
| | | | |The 'allout-mode' function's |
| | | | |docstring is your guide, |
| | | | |including an introduction, |
| | | | |keybindings and pointers for eg, |
| | | | |using the encryption feature. |
+----+----+------+----------------------------+---------------------------------+
| |\+ | \+ | - `pgg.el.gz`__ |Required only for topic |
| | | | - `pgg-gpg.el.gz`__ |encryption/decryption - the rest |
| | | | - `pgg-def.el.gz`__ |of allout will work fine without |
| | | | - `pgg-parse.el.gz`__ |this. |
| | | | | |
| | | | |Newer versions of Emacs pgp/gpg |
| | | | |encryption interface. Available |
| | | | |from the CVS head for Emacs 22, |
| | | | |you need these versions for the |
| | | | |topic encryption functionality in|
| | | | |the other emacs. |
+----+----+------+----------------------------+---------------------------------+
|\+ |\+ | \+ |GNU GPG installed, and emacs|Necessary only if you want to do |
| | | |pgg configured to use it |topic encryption/decryption. |
| | | | | |
+----+----+------+----------------------------+---------------------------------+
| | | \+ |Compilation with Mule |Necessary only if you want to |
| | | |extensions |use topic encryption/decryption. |
| | | | | |
| | | | |The encryption functions require |
| | | | |coding region sensitivity |
| | | | |provided by Mule. |
+----+----+------+----------------------------+---------------------------------+
| |\+ | \+ |For your emacs init/emacsrc:|v21 emacs variants get mildly |
| | | | |confused traversing invisible |
| | | |- (substitute-key-definition|text with the |
| | | | 'beginning-of-line |{beginning,end}-of-line |
| | | | 'move-beginning-of-line |functions. This code, intended |
| | | | global-map) |for your emacsrc, substitutes |
| | | |- (substitute-key-definition|routines from Emacs 22 (which |
| | | | 'end-of-line |Allout defines if not already |
| | | | 'move-end-of-line |present) which handle that |
| | | | global-map) |correctly. |
| | | | | |
| | | | | |
+----+----+------+----------------------------+---------------------------------+
|\+ |\+ | \+ | - `allout-widgets.tgz`_ |A cooperative allout extension |
| | | | |which adds graphical structural |
| | | | |cues and, eventually, more |
| | | | |intricate outline structuring. |
| | | | | |
| | | | |It's currently quite preliminary,|
| | | | |but offers some value. Situate |
| | | | |the code and icon directories on |
| | | | |your load-path, load, and eval |
| | | | |(allout-mode-widgets-init), then |
| | | | |visit an allout outline. |
+----+----+------+----------------------------+---------------------------------+
A remark from one enthusiastic allout user:
Using allout is like putting on glasses - I've been able to improve and
clarify code in every file in which I've used it. Sure, any outline mode
could help with that, but they all have arcane or busy navigation &
show/hide commands. The genius of allout's hot-spot navigation makes it
all as easy as putting on a pair of glasses. Hmm... that sounds like
promotional copy - feel free to use it if it answers a need :-) Bill W.
__ allout.el
__ pgg.el.gz
__ pgg-gpg.el.gz
__ pgg-def.el.gz
__ pgg-parse.el.gz
~
.. _`Emacs Wiki page on allout`: http://www.emacswiki.org/cgi-bin/wiki/AllOut
.. _`used principally by programmers`: http://xkcd.com/378/
.. _`allout-widgets.tgz`: allout-widgets.tgz
.. _`allout.el`: allout.el
.. figure:: elm_large_oblong.png
:align: center
From Stefan Sun Jun 18 16:10:37 -0400 2006
From: Stefan
Date: Sun, 18 Jun 2006 16:10:37 -0400
Subject: automatic loading of auto-fill mode
Message-ID: <20060618161037-0400@www.myriadicity.org>
I am trying out the latest/greates (!) allout-mode version that I have downloaded from this site. I try to adapt it to my needs. When I work with text files I prefer explicit filling of paragraphs and therefore do not use the auto-fill-mode. When I load allout-mode auto-fill-mode gets loaded automatically. Is auto-fill mode essential for allout-mode to work. If not is it possible to make the automatic loading of auto-fill mode configurable - or are there any other reasons why this would not be a good idea. Thanks for you answer and many thanks for allout-mode - Stefan
From klm Sun Jun 18 18:12:15 -0400 2006
From: klm
Date: Sun, 18 Jun 2006 18:12:15 -0400
Subject: automatic loading of auto-fill mode
Message-ID: <20060618181215-0400@myriadicity.net>
In-Reply-To: <20060618161037-0400@www.myriadicity.org>
i've uploaded a new allout version which includes, among other things, a new custom configuration variable, `allout-inhibit-auto-fill'. setting this will turn off auto-fill in the buffer where you set it (if you use 'Esc-x set-variable' or 'Esc-: (setq ...'), or in all allout buffers if you customize the setting (eg, 'customize-variable').
This new version is also has a bunch of other fixes - see the link to the code, above, and AlloutNEWS and AlloutChangeLog for details about the changes.
(organization of auto-fill functionality in allout was complicated by the hanging-indent requirements. there may be a cleaner way to do it, particularly since many things in emacs in general have gotten cleaner. if this new config var is enough to address the problem you noticed, though, i doubt i'll pay much more attention to that. i'm working on other allout stuff - soon there should be automatic escaping to enable including item-prefix looking text inside of item bodies without breaking the bodies, and i'm working on a whole nother layer, including nice graphics but more importantly, substantial cross references and settings, for the longer term.)
i have no way to reply to you, since i don't have your full name or email address - if you visit again and find this response, please let me know whether or not the change does what you need. enjoy!
From klm Fri Jul 07 16:41:47 -0400 2006
From: klm
Date: Fri, 07 Jul 2006 16:41:47 -0400
Subject: auto-fill, mode-deactivation cleanup, more improved
Message-ID: <20060707164147-0400@myriadicity.net>
i've finally reworked the cleanup provisions on allout-mode deactivation, so that variables, hook functions, and so forth are nicely reverted, which they weren't being before. (the new version of the mechanism is also much more programmer friendly, preventing overlooking some resumptions among other things.)
one specific thing that's done more nicely with the new mechanism is auto-fill provisions, so that auto-fill-mode is not activated if it wasn't already active. turning on auto-fill along the way, however, continues to provide auto-indentation that respects topic headlines, if allout customization settings are configured for that.
there are also now some unit tests, specifically for the modal-settings resumptions code. developers can select having the unit tests run automatically on module load by customizing `allout-run-unit-tests-after-load'.
i've uploaded the new version of the code, along with a new NEWS and ChangeLog files.
From tom Sat Nov 11 17:46:11 -0500 2006
From: tom
Date: Sat, 11 Nov 2006 17:46:11 -0500
Subject: C-mode fixes submitted
Message-ID: <20061111174611-0500@myriadicity.net>
I can't see a proper place to submit this, so I'm just submitting it here. Frustrated with allout's difficulty with C-style comments, I fixed the problem as I see it, and am submitting diffs which I hope will be included in the next version of allout.el
Specifically: It now understands about "*" in comment-start, and it now writes comment-end after a line.
| [Begin diff]
| 696,697c696,697
| < (setq outline-regexp (concat "\\("
| < (regexp-quote outline-header-prefix)
| ---
| > (setq outline-regexp (concat "\\(\\"
| > outline-header-prefix
| 2851,2852c2851
| < " "
| < comment-end))
| ---
| > " "))
| [End diff]
From tom Sat Nov 11 17:47:41 -0500 2006
From: tom
Date: Sat, 11 Nov 2006 17:47:41 -0500
Subject: and that diff got horribly munged
Message-ID: <20061111174741-0500@myriadicity.net>
Sorry about that, couldn't be helped.
From: klm
Date: Wed, 15 Nov 2006 20:02:06 -0500
Subject: C-mode fixes submitted
Message-ID: <20061115200206-0500@myriadicity.net>
In-Reply-To: <20061111174611-0500@myriadicity.net>
thanks for the patch, tom. (the formatting was preserved in the page source, it's just mangled in rendering.) it turns out that the problem was repaired in a more recent allout version - your patch is against a version that's at least a year old. download the newest version from the link, above, and give it a try...
From jesse Fri Jan 19 14:45:34 -0500 2007
From: jesse
Date: Fri, 19 Jan 2007 14:45:34 -0500
Subject: relation to linkd?
Message-ID: <20070119144534-0500@myriadicity.net>
Hi Ken,
There's a new emacs package in town: linkd, see http://dto.freeshell.org/notebook/Linkd.html . What's the relationship between these two packages? Can one use both of them simultaneously?
Jesse
From klm Tue Feb 20 15:14:04 -0500 2007
From: klm
Date: Tue, 20 Feb 2007 15:14:04 -0500
Subject: relation to linkd?
Message-ID: <20070220151404-0500@myriadicity.net>
In-Reply-To: <20070119144534-0500@myriadicity.net>
just took a look at linkd, and it seems like the linking stuff should work
with allout, but use of the linkd block features may be problematic in
allout, because there's no structural coordination between the two modes.
that is, linkd blocks are created without regard to allout topic boundaries
or containment structure. i don't think linkd was created specifically
with allout in mind, and i didn't know about linkd until your mention of
it.
From tassilo Tue Jul 10 17:08:15 -0400 2007
From: tassilo
Date: Tue, 10 Jul 2007 17:08:15 -0400
Subject: Toggling the hidden state of the current entry
Message-ID: <20070710170815-0400@myriadicity.net>
Hi Ken,
I really enjoy allout mode, but one thing I always missed was toggling the hidden state of the current entry. I came up with this function which does exactly this::
(defun th-allout-toggle-children ()
"Show or hide the current subtree depending on its current
state."
(interactive)
(save-excursion
(allout-back-to-heading)
(if (allout-hidden-p (point-at-eol))
(progn
(allout-show-children)
(allout-show-entry))
(allout-hide-current-subtree))))
Currently I'm waiting for assignment papers for GNU Emacs, so if you want I can provide a patch soon.
From tassilo Tue Jul 10 17:24:28 -0400 2007
From: tassilo
Date: Tue, 10 Jul 2007 17:24:28 -0400
Subject: Toggling the hidden state of the current entry
Message-ID: <20070710172428-0400@myriadicity.net>
In-Reply-To: <20070710170815-0400@myriadicity.net>
Ups, that didn't work. Here's a paste: http://paste.lisp.org/display/44307
From: anonymous
Date: Thu, 06 Sep 2007 23:24:00 -0400
Subject: Add real keymap for hotspots?
Message-ID: <20070906232400-0400@myriadicity.net>
Is there any chance of replacing the hotspot key mapping logic with a real keymap? I would have liked to be able to define other hotspot keys - specifically, I wanted to add "@" to work as "\C-c @". But without a keymap to define a key into, there was no reasonable way to do it.
If I submitted a patch replacing that logic with a keymap, would there be any interest in it?
From klm Fri Sep 07 02:01:23 -0400 2007
From: klm
Date: Fri, 07 Sep 2007 02:01:23 -0400
Subject: Add real keymap for hotspots?
Message-ID: <20070907020123-0400@myriadicity.net>
In-Reply-To: <20070906232400-0400@myriadicity.net>
instead of retrofitting these things to allout, i'm working on a fairly thorough widget-ish allout addon, `allout-widgets.tgz`_. it's described briefly in the main body of this page. the addon includes, among other things, using keymaps for the various active areas. i've made some progress since the version was last uploaded here, but it'll be a few days before i can upload the latest version - the guts are currently on the table. (i was actually editing it, working out a bug, when this comment came in.)
the addon's enhancements include graphical rendering of the outline structure, use of keymaps for the various outine parts with (as yet, mostly unused) mouse bindings, and undo that applies to structure exposure changes as well as edits. (the latter is necessary so that edit changes are visible as they're undone - settling a problem with regular allout.) there may be other features i'm forgetting, and in not too long i hope to get to dealing with multiply located outline items, to deal with things like layered topic versioning, alternately organized views of collections of hierarchies, and other database-y uses of outlines.
though there's still a ways to go to get it where i want, it's a pretty striking improvement on allout as it currently stands, if only for the graphical outline structure. though it doesn't yet surface some existing allout features - notably, distinctive bullets are currently hidden - i've been using it for almost all of my outlining for many months now, and wouldn't do without it.
From klm Fri Sep 07 10:24:39 -0400 2007
From: klm
Date: Fri, 07 Sep 2007 10:24:39 -0400
Subject: Toggling the hidden state of the current entry
Message-ID: <20070907102439-0400@myriadicity.net>
In-Reply-To: <20070710170815-0400@myriadicity.net>
sorry about the delay replying - i will incorporate your toggle-visibility function. (i notice that the progn becomes unnecessary when you switched to using `allout-show-current-subtree' in the version you pasted to paste.lisp.org.)
.. allout-xref-question:
From tehom Fri Sep 07 23:14:44 -0400 2007
From: tehom
Date: Fri, 07 Sep 2007 23:14:44 -0400
Subject: allout-widgets
Message-ID: <20070907231444-0400@myriadicity.net>
allout-widget sounds fascinating. Tantalizing might be a better word,
actually.
I was about to start coding smarter links as an add-on to allout, a
"smarter \C-c @", so to speak. The docs of allout-widget say
"provides for situating and otherwise cross referencing items within
and across outlines". But I don't see code for that yet.
Now I'm wondering whether I should go ahead and write it, or wait, or
try to co-ordinate with you.
Have you considered what should happen if target files are renamed?
Tom Breton (Tehom)
From klm Sat Sep 08 16:07:12 -0400 2007
From: klm
Date: Sat, 08 Sep 2007 16:07:12 -0400
Subject: allout-widgets
Message-ID: <20070908160712-0400@myriadicity.net>
In-Reply-To: <20070907231444-0400@myriadicity.net>
| > allout-widget sounds fascinating. Tantalizing might be a better word,
| > actually.
|
tantalyzing for me, too. i'm only very slowing getting to the meat of what really interests me here.
| > I was about to start coding smarter links as an add-on to allout, a
| > "smarter C-c @", so to speak. The docs of allout-widget say
| > "provides for situating and otherwise cross referencing items within
| > and across outlines". But I don't see code for that yet.
| >
| > Now I'm wondering whether I should go ahead and write it, or wait, or
| > try to co-ordinate with you.
| >
| > Have you considered what should happen if target files are renamed?
|
i'm not sure how to answer your question, though i do think that results from my efforts in this regard are going to be slow to arrive. that said, it may be helpful to know what i'm ultimately thinking about, to inform whether and what you do. i'm putting that in AlloutStableReferences, but be warned, it's very rough-draft and speculative (in american idiom, "pie in the sky"). that you're tantalyzed by the hints i've mentioned thus far suggests that you might find more details interesting, in any event. i also have a somewhat simplistic description of my ultimate interests, in TurningAnswersIntoStories
i'm glad to hear of your interest!
ken
[P.S. incidentally, tom, i just learned about regress.el, on the emacs
wiki, through it's association with your name. one of the last things i
need to do for allout-widgets before i work on settings (and after i post
an updated version for others to play with) is better infrastructure for
regression testing. i hate being without test coverage where it's really
needed, and have some rudimentary provisions in both allout.el and
allout-widgets.el - look for -run-unit-tests-on-load. regress.el may be
just what i need...]
From klm Thu Sep 13 17:40:12 -0400 2007
From: klm
Date: Thu, 13 Sep 2007 17:40:12 -0400
Subject: new version of allout-widgets uploaded
Message-ID: <20070913174012-0400@myriadicity.net>
i've uploaded a new version of `allout-widgets.tgz`_ which may be
interesting to some allout users out there. there's still some missing
allout features, notably, distinctive bullets are hidden - not removed from
the text, just not yet surfaced to view. some fixes depend on a new
version of `allout.el`_ i've also uploaded. give it a whirl, if you're
interested, let me know if you encounter problems - i may have some time to
polish things.
From klm Thu Sep 20 14:31:41 -0400 2007
From: klm
Date: Thu, 20 Sep 2007 14:31:41 -0400
Subject: new version of allout-widgets uploaded
Message-ID: <20070920143141-0400@myriadicity.net>
In-Reply-To: <20070913174012-0400@myriadicity.net>
for any of you interested in allout widgets, i botched the version of `allout-widgets.tgz`_ that i uploaded previously. i just uploaded a new version that rectifies the mistake. unpack it in a directory on your emacs load-path, byte-compile (optional, but useful for large outlines) and load allout-widgets in your init somewhere.
(note that the allout-widgets.el file, as well as allout.el, have settings in their emacs file variable section to inhibit allout widget mode in the files, themselves. you can disable that inhibition by removing or relocating the line that assigns the ``allout-widgets-mode-inhibit`` variable.)
From tehom Thu Sep 20 21:16:55 -0400 2007
From: tehom
Date: Thu, 20 Sep 2007 21:16:55 -0400
Subject: Re: new version of allout-widgets uploaded
Message-ID: <20070920211655-0400@myriadicity.net>
Thanks for the upload.
Some comments:
I like the item settings. I'm more excited about them than I am about
widgets.
I had written a little code towards a similar idea. I had put the
values in an s-exp immediately following the bullet. But I like your
design better. It's more consonant with the text nature of these sort
of files.
As the code stands, I can't really experiment because
allout-get-item-widget just returns nil and the other interesting
functions all want a widget as an argument. The problem may lie in
how I invoked it, but I tried both allout-widgets-mode and allout-mode
and then allout-widgetize-buffer.
I see there is code to read them in allout-assimilate-body-settings,
but it assumes that widgets are set up and working. That makes it
difficult for me to use it right now.
So if you don't mind, I'd like to send you changes I've written. It
splits the non-widget code out of allout-assimilate-body-settings. I
created some test example files and some tests - seems like continued
lines and null settings are not working yet, so that might be handy.
One thing I've found helpful in writing tests for allout is to use
outline-flatten-exposed-to-buffer to test that exposure is done right.
I use this in conjunction with my mockbuf.el and a test-helper
function I can send you.
When i want to test folding I make two example files, "EXAMPLE" and
"EXAMPLE-folded". "EXAMPLE" is text in the configuration of interest,
with "interesting" points marked by arbitrary unique strings.
"EXAMPLE-folded" is the same thing minus any text that should be
invisible. ::
(with-current-buffer
(find-file-goto-text "example-file" "that-unique-string" ade:th-test-subdir)
(outline-show-all) ;;Undo any previous hiding
;;BODY: Do whatever is being tested, confident that it's
;;executed in "example-file" with point where the string
;;"that-unique-string" is
(ade:th-compare-exposed-to-file "example-file-folded"))
(As I write this, I realize I could fruitfully encap that logic so
that it only needs BODY and some parameters)
PS: Glad you like regress.el I have an updated version of it available called rtest.
From klm Fri Sep 21 00:13:13 -0400 2007
From: klm
Date: Fri, 21 Sep 2007 00:13:13 -0400
Subject: Re: new version of allout-widgets uploaded
Message-ID: <20070921001313-0400@myriadicity.net>
In-Reply-To: <20070920211655-0400@myriadicity.net>
| > I like the item settings. I'm more excited about them than I am about widgets.
|
interesting.
| > As the code stands, I can't really experiment because allout-get-item-widget
| > just returns nil and the other interesting functions all want a widget as an
| > argument. The problem may lie in how I invoked it, but I tried both
| > allout-widgets-mode and allout-mode and then allout-widgetize-buffer.
|
i'm not surprised that you're having some difficulty getting it going - you're probably the first person besides me to try it. in fact, there's a priming measure that i forgot to mention, in the docs and on this site. you need to do ``(allout-mode-widgets-init)`` after the allout-widgets code is loaded. i need to include a note about this step prominently in the file commentary, and in some main entry function.
also, allout-get-item-widget's behavior is a little odd. it only succeeds when point is located in the structure area of the item (before the body text - it's explained in the function's docstring). this can be beguiling.
one thing i want to do for testing is to have various outline static conditions, like text-property locations, recorded in emacs local file variables for comparison during tests. a regression testing harness should help make that fairly easy to automate.
From tehom Fri Sep 21 16:13:08 -0400 2007
From: tehom
Date: Fri, 21 Sep 2007 16:13:08 -0400
Subject: Re: new version of allout-widgets uploaded
Message-ID: <20070921161308-0400@myriadicity.net>
Thanks for the directions on starting widgets. I'll definitely give
it another whirl. Yes, when I did that, it worked, and graphics
appeared in response to the outline.
<blockquote> allout-get-item-widget's behavior ... only succeeds when
point is located in the structure area of the item </blockquote>
Maybe save-excursion, move point and get the widget? This seems to
work as a stopgap measure:
(save-excursion
(allout-beginning-of-current-entry)
(allout-get-item-widget))
<blockquote>
i think the way i want to do regressions is to make some routines that
record various conditions of an outline - where the text properties
are, for instance - in file-local-variables using the routines, and
have the tests
</blockquote>
...test that the result is the same as before? That's one way to
test, and it's tempting if the code already works. For testing output
that has the property that if it looks right it's right, that sort of
testing is perfect. But tests can do more for you than that. I find
that test-driven design does wonders for me, but one needs to design
and write the testability functionality first.
Tom Breton (Tehom)
From klm Sat Sep 22 16:07:27 -0400 2007
From: klm
Date: Sat, 22 Sep 2007 16:07:27 -0400
Subject: Re: new version of allout-widgets uploaded
Message-ID: <20070922160727-0400@myriadicity.net>
In-Reply-To: <20070921161308-0400@myriadicity.net>
| > ...test that the result is the same as before? That's one way
| > to test, and it's tempting if the code already works. For testing
| > output that has the property that if it looks right it's right, that
| > sort of testing is perfect. But tests can do more for you than that.
| > I find that test-driven design does wonders for me, but one needs to
| > design and write the testability functionality first.
|
you're entirely right, and i have enjoyed programming that way - particularly when developing substantially layered applications. i've found it hard to do, though, when graphical UI interactions were an essential part of the functionality being tested. in fact, that concern partly explains the focus of my comment - i realized that i could capture many of the sensitive aspects of the allout widgets UI by recording and comparing the character (text and overlay) properties positions, detecting discrepancies that way. it so happens that i'm finding the way i'm using properties brittle, so i'm a bit obsessed with that. (i think i've figured out a way around that, and intend to make a substantial change in the way that item body regions are identified, avoiding using character properties for that.)
none of that addresses a major concern, for which i had already started to create a little bit of testing infrastructure - settings. i'm thrilled that you're interested in that, to the point of sending some tests that look like they'll be quite useful, and maybe help get me kick started - yay!
and, i've uploaded another version of the allout-widgets with some more mistakes polished off - plus, some of those setup notes that were missing.
From tehom Sat Oct 06 17:54:34 -0400 2007
From: tom breton
Date: Sat, 06 Oct 2007 17:54:34 -0400
Subject: Let's move item settings to before item body?
Message-ID: <20071006175434-0400@myriadicity.net>
Ken: I've been working with allout-item-settings a fair bit recently.
I have some code that reads and writes them - not to and from widgets,
though. I sent you an early version of it.
I've encountered what I think is a serious problem: When an item's
body is split into subtopics, the settings end up in the last child,
not in the node itself (as new parent). This happens because the
settings follow the body.
I think the best solution is to move the settings to above items'
bodies instead of below. I'd like to implement this.
Tom Breton (Tehom)
From klmplus Tue Feb 26 16:24:59 -0500 2008
From: klmplus
Date: Tue, 26 Feb 2008 16:24:59 -0500
Subject: allout.el xemacs compatibility
Message-ID: <20080226162459-0500@myriadicity.net>
on prompting from someone who needed it, i've finally spent a bit of time getting the recent allout.el working in the recent version of xemacs. there are still some small glitches, but it seems quite usable. (allout-widgets.el is another story. i'll have to address differences in graphics/images instantiation, and probably won't do that immediately.)
yet another logo