On 10/2/05, Steve Youngs <steve(a)sxemacs.org> wrote:
* Ken Manheimer <ken.manheimer(a)gmail.com> writes:
> i'd be happy to be the maintainer, with direct commit
privileges. (do
> you use cvs over ssh? if so, i'll need an account on some system...)
Norbert Koch <viteno(a)xemacs.org> is the man to speak to about setting
it all up. I'm sure he'll be in touch.
haven't heard from him, but i'll post my revisions to xemacs patches
sometime next week, and reopen the issue of applying the changes
directly.
> i'm continuing to discover niggles ("wait, this is
the last one...":-)
I have a "niggle" :-) ...
(defun my-mark-marker (&optional force buffer)
"Accommodate the different signature for `mark-marker' across Emacsen.
XEmacs takes two optional args, while mainline GNU Emacs does not,
so pass them along when appropriate."
(if (string-match " XEmacs " emacs-version)
(mark-marker force buffer)
(mark-marker)))
I'd like to see that written as...
(defun allout-mark-marker (&optional force buffer)
"Accommodate the different signature for `mark-marker' across Emacsen.
XEmacs takes two optional args, while mainline GNU Emacs does not,
so pass them along when appropriate."
(if running-xemacs
(mark-marker force buffer)
(mark-marker)))
,----[ C-h v running-xemacs RET ]
| `running-xemacs' is a variable declared in Lisp.
|
| Value: t
|
| Documentation:
| Non-nil when the current emacs is XEmacs or SXEmacs.
`----
The value of the variable `emacs-version' might change one day,
whereas `running-xemacs' will _always_ be `t'. :-)
but it's not defined at all in gnu emacs, which makes for a very
limited compatibility provision...-)
i see recommendations for: (featurep 'xemacs)
i'll switch to that.
thanks for the hints!
ken
ken.manheimer(a)gmail.com