From: "Ken Manheimer" <ken.manheimer@gmail.com>
Subject: Re: New allout revisions
Date: Mon, 13 Mar 2006 12:56:40 -0500 [thread overview]
Message-ID: <2cd46e7f0603130956t696ec113yf01585096cebb97e@mail.gmail.com> (raw)
In-Reply-To: <2cd46e7f0603130952v361cef17g6b77a9a0dcaa2add@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
dang - i sent the wrong copy of the ChangeLog in my last message -
attached is the current one - please use this instead...
On 3/13/06, Ken Manheimer <ken.manheimer@gmail.com> wrote:
> attached is a ChangeLog and patch for some refinements of allout.el.
> the most signficant changes are marking some commonly used allout file
> local variables as safe, according to the new system, and
> establishment of a custom variable for the default allout layout spec.
> see the ChangeLog for more details.
>
> (in crafting the allout-default-layout custom variable type i was
> blocked by what seems to be a limit in the customization type
> protocol. the layout spec allows for nested expressions that are
> themselves layout specs, and so the type form is self-recurrent. i
> see no way, however to declare self-recurrent or even
> indirectly-recurrent type definitions. is there a way, in the current
> custom types system?)
> --
> ken manheimer
> ken.manheimer@gmail.com
> http://myriadicity.net
>
>
>
--
ken manheimer
ken.manheimer@gmail.com
http://myriadicity.net
[-- Attachment #2: allout-ChangeLog.txt --]
[-- Type: text/plain, Size: 1053 bytes --]
2006-03-13 Ken Manheimer <ken.manheimer@gmail.com>
* allout.el: Increment version to 2.2.1 in file commentary.
(allout-version): Increment to 2.2.1.
(allout-default-layout): New customization variable, used when the
file lacks a specific allout-layout. Customization type is
substantive except when it comes to recursively nested layout
expressions, because i see no way to have self-recurrent, or even
indirectly recurrent customization types. I punt by using a
generic list.
(allout-mode): Incorporate allout-default-layout as fallback for
allout-layout.
(allout-layout): Mark as 'safe-local-variable', and refer mention
fallback to `allout-default-layout' in absence of a specified value.
(allout-passphrase-verifier-string)
(allout-passphrase-hint-string): Mark as 'safe-local-variable'.
(allout-file-passphrase-verifier-string): Obsolete variable, removed.
(allout-get-encryption-passphrase-verifier): Use correct name of
passphrase verifier in docstring.
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2006-03-13 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 17:52 New allout revisions Ken Manheimer
2006-03-13 17:56 ` Ken Manheimer [this message]
2006-03-13 18:04 ` Ken Manheimer
2006-03-13 18:11 ` Luc Teirlinck
2006-03-13 19:48 ` Ken Manheimer
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd46e7f0603130956t696ec113yf01585096cebb97e@mail.gmail.com \
--to=ken.manheimer@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.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).