October 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Barry A. Warsaw

Sorry, the useful function probably ought to be something like the following. I'm sure Hrvoje can sanitize this ;-) -Barry -------------------- snip snip -------------------- (defun imenu-popup-menu (event) "Wrapper for mouse button bindings for imenu." (interactive "e") (let* ((answer (imenu--mouse-menu (imenu--make-index-alist) event)) (name (car answer)) (position (cdr answer))) (if (< 0 position) (imenu-default-goto-function name position) (imenu--cleanup) (setq imenu--index-alist nil))))

1 participants
0 comments

One more imenu.el thing 25 years, 5 months

Barry A. Warsaw

This seems like a useful function: (defun imenu-popper (event) "Wrapper for mouse button bindings for imenu." (interactive "e") (imenu--mouse-menu (imenu--make-index-alist) event)) -Barry

1 participants
0 comments

Problem with imenu.el 25 years, 5 months

Barry A. Warsaw

I think there's a problem with Imenu when a buffer has no functions in it. I know Imenu is newly ported to XEmacs (thanks Hrvoje!) so there may be some rough edges. Mostly it works pretty well (I've been updating the python-mode.el support). Here's how to reproduce. Start up a vanilla XEmacs with the menubar on, and be sure the imenu library is loaded. Visit an empty Emacs-Lisp buffer, and run imenu-add-to-menubar (type "IM-Elisp" at prompt). You should now see a menu item that reads "IM-Elisp". Try to pull this menu down and you will get an error menu name (first element) must be a string: (nil) This is because the imenu-create-index-function returns nil, which triggers the second or-clause in imenu--make-index-alist, thus eventually setting imenu--index-alist to '(nil). In Emacs, this return value seems to tell the menu posting code (where ever *that* is ;-) not to post a menu item. In XEmacs, however this causes an error. I am unsure what the right thing is to return in XEmacs, so I can't supply a fix. Thanks, -Barry

1 participants
0 comments

Re: Problems building 21.2 "Aglaia" on Solaris 2.5.1 (missing -Rlibdir) 25 years, 5 months

Greg Klanderman

>>>>> "Kyle" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: Kyle> Kyle> Martin Buchholz writes: >> (Didn't someone submit a patch for this ages ago?? >> Why are patches getting lost??) Kyle> Kyle> They are probably not being submitted to the right place. Kyle> xemacs-beta is not the right place, if you want a patch to be Kyle> reviewed for inclusion in XEmacs. I've seen patches posted to Kyle> xemacs-beta recently and I don't know what happens to them. I'm pretty sure there are at least 2 patches that went to xemacs-patches and didn't get synched in 21.2 (yet), judging from this list. Are they supposed to be synched?

1 participants
0 comments

Re: a new user 25 years, 5 months

Greg Klanderman

>>>>> "Sam" == Sam Steingold <sds(a)goems.com> writes: Sam> ... Sam> As for the packages: Sam> Sam> - I got xemacs-base and efs and installed the rest via Sam> `pui-list-packages'. Sam> * I had to install vm and mh-e, which I will never use, but Sam> which are required by some other packaged I wanted - which ones?! I think EFS requires VM. (package-get-dependencies '(efs)) => (dired vm xemacs-base mail-lib) Unfortulately, at this time the requires are compile/build-time requires, not run-time. There has been discussion about fixing this. Note you don't *always* need to install the "required" packages. I'd bet you could get away without these two. That's why I've made adding the requires optional in pui-list-packages. Sam> - I am getting Sam> Sam> (4) (warning/warning) Autoload error in: /usr/src/xemacs/packs/lisp/text-modes/auto-autoloads: Sam> Symbol's value as variable is void: flyspell-mode-map This is a bug in the current text-modes package which should soon be fixed. You can manually edit the auto-autoloads file adding (defvar flyspell-mode nil) (make-variable-buffer-local 'flyspell-mode) (defvar flyspell-mode-map (make-sparse-keymap)) near the top and re-bytecompile. Sam> in `*Warnings-Show*', I think this was discussed here before. Sam> Sam> - I am getting Sam> Sam> Signaling: (void-variable last-buffer-undo-list) Dunno, may be due to the autoloads in text-modes being hosed. greg

1 participants
0 comments

Re: Changes to VC-CC 25 years, 5 months

SL Baur

[Cc'ed to xemacs-beta] I'm basically out of the loop other than putting in what appears to be reasonable changes and making minimal changes as the XEmacs package interface evolves. Please work with Rod on keeping the primary version of vc-cc in synch. Rod Whitby <rwhitby(a)asc.corp.mot.com> writes: > Guys, > I notice that you guys have been making changes to the vc-cc package > distributed with XEmacs. I notice that I (as the maintainer of that > package) and Chris Felaco <felaco(a)ziplink.net> have not been notified. > I know that I have not been the most active maintainer, and now want > to rectify that. > Did you know that the official distribution point for VC-CC is > /rwhitby.home.ml.org/vc-clearcase.html ? I want to merge your changes > with the official release, and stop the divergence of vc-cc. > Unfortunately, I'm behind a firewall, so can't access the CVS server > directly. How can we resolve this sitation ? If a volunteer with internet access steps forward he or she can integrate your changes. I would normally do this, but my patch latency is extremely high right now and it is quite possible that I will not be integrating any further patches before April 1999. I apologize for this.

5 participants
5 comments

[offtopic] Autoconf maintainer 25 years, 5 months

Hrvoje Niksic

I vaguely remember a guy mailing to this list asking us to report Autoconf bugs/patches to this list, him being the new Autoconf maintainer. Does anyone remember his name and address? I have some problems with Autoconf that I'd like to fix, but I don't know where to send the patches. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- You know it's going to be a bad day when your twin brother forgot your birthday.

2 participants
2 comments

Re: Problems building 21.2 "Aglaia" on Solaris 2.5.1 (missing -Rlibdir) 25 years, 5 months

Kyle Jones

Martin Buchholz writes: > (Didn't someone submit a patch for this ages ago?? > Why are patches getting lost??) They are probably not being submitted to the right place. xemacs-beta is not the right place, if you want a patch to be reviewed for inclusion in XEmacs. I've seen patches posted to xemacs-beta recently and I don't know what happens to them.

1 participants
0 comments

Re: a new user 25 years, 6 months

Sam Steingold

>>>> In message <kighfwpsoat.fsf(a)jagor.srce.hr> >>>> On the subject of "Re: a new user" >>>> Sent on 27 Oct 1998 22:11:22 +0100 >>>> Honorable Hrvoje Niksic <hniksic(a)srce.hr> writes: >> Sam Steingold <sds(a)goems.com> writes: >> >> > >>>> In message <m3emrvc58n.fsf_-_(a)eho.eaglets.com> >> > >>>> On the subject of "a new user" >> > >>>> Sent on 26 Oct 1998 17:45:12 -0500 >> > >>>> Honorable Sam Steingold <sds(a)goems.com> writes: >> > >> >> > >> 2. When a key is undefined or bound to an undefined function, nothing >> > >> happens. Emacs beeps, can I make XEmacs beep too? >> > >> > The reason for this misbehavior is that I set `debug-on-error' to T >> > in .emacs. Is there a way to have both backtrace on important >> > errors and ding on undefined keys? >> >> You mean, have `debug-ignored-errors' default to non-nil? I wanted I did not set `debug-ignored-errors', so it was nil. what I was observing: (with debug-ignored-errors = nil; debug-on-error = t): when I type <insert an undefined key sequence here> **nothing happens** - no ding, no backtrace, just plain *nothing*. >> that, but I was overruled. A sample setting for debug-ignored-errors what was the rationale? >> can be found at lisp/loaddefs.el (look at the commented-out code). What I see there is what I get for free in Emacs. I guess I'll just remove the comments and re-dump. That's what the GPL is for, right? :-) As for the packages: - I got xemacs-base and efs and installed the rest via `pui-list-packages'. * I had to install vm and mh-e, which I will never use, but which are required by some other packaged I wanted - which ones?! - I am getting (4) (warning/warning) Autoload error in: /usr/src/xemacs/packs/lisp/text-modes/auto-autoloads: Symbol's value as variable is void: flyspell-mode-map in `*Warnings-Show*', I think this was discussed here before. - I am getting Signaling: (void-variable last-buffer-undo-list) (eq last-buffer-undo-list nil) ) (or (eq buffer-undo-list t) (eq last-buffer-undo-list nil) (not (or ... ...)) (or (eq buffer-undo-list pending-undo-list) (eq ... pending-undo-list))) ) (not (or (eq buffer-undo-list t) (eq last-buffer-undo-list nil) (not ...) (or ... ...))) ) make-frame((user-size t user-position t reverse nil minibuffer nil cursor-type bar scroll-bar-width 12 mouse-color "magenta" foreground-color "DarkSlateBlue" background-color "lightgray" cursor-color "Blue" minibuffer nil cursor-type bar scroll-bar-width 12 mouse-color "magenta" foreground-color "DarkSlateBlue" background-color "lightgray" cursor-color "Blue" height 40 width 80 minibuffer t left 591 top 415 border-width 0 internal-border-width 4 border-color "#000000000000" ...)) frame-notice-user-settings() byte-code("..." [abbreviate-file-name default-directory expand-file-name format "%s%d-%s" auto-save-list-file-prefix emacs-pid system-name auto-save-list-file-name run-hooks emacs-startup-hook term-setup-hook nil frame-notice-user-settings window-setup-hook] 6) normal-top-level() on startup (I am not getting this with -q) and I am at a loss as to what would cause this. I did not observe this before, and `last-buffer-undo-list' is not present in my .emacs. -- Sam Steingold (http://www.goems.com/~sds) running RedHat5.1 GNU/Linux Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. I'm a Lisp variable -- bind me!

1 participants
0 comments

Re: a new user 25 years, 6 months

Jan Vroonhof

Sam Steingold <sds(a)goems.com> writes: > The reason for this misbehavior is that I set `debug-on-error' to T in > .emacs. Is there a way to have both backtrace on important errors and > ding on undefined keys? Presumably you also set debug-ignored-errors? However something is still wrong. I have debug-ignored-errors set to (beginning-of-buffer end-of-buffer undefined-keystroke-sequence) and debug-on-error set to t and I still get 'dings' on undefined keys. weird. Jan

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta October 1998