August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Need help with `imenu-generic-expression' wrt menu splitting 26 years

Adrian Aichner

Hello users of Imenu. I am using imenu to keep modules I write portable between XEmacs and GNU Emacs although I am not using GNU Emacs. Someone may still benefit from it. The problem: Using `imenu-generic-expression' to generate the menu (make-local-variable 'imenu-generic-expression) (setq imenu-generic-expression (list (list nil vb-function-definition-regexp 4) (list "goto LABEL" vb-label-goto-regexp 2) (list "LABEL:" vb-label-definition-regexp 1) (list "Constants" vb-constant-regexp 3) (list "Functions" vb-function-definition-regexp 4) (list "Properties" vb-property-definition-regexp 3) (list "Variables" vb-variable-regexp 3))) (imenu-add-to-menubar "Symbols")) I found menu splitting only to work on the top-level. While I would like to use a sub-menu for functions: (list "Functions" vb-function-definition-regexp 4) this menu does not split and I can only access those functions from the menu that fit on the screen. The top-level entry (list nil vb-function-definition-regexp 4) which I put in for testing purposes splits nicely according to imenu-max-items (25 by default), producing menu entries like: From: a> From: f> From: m> From: w> goto LABEL:> LABEL:> Constants> Functions> Properties> Variables> Can anyone tell me how to get entries under Functions> to split out as From: a> From: f> From: m> From: w> according to imenu-max-items? Thanks for any suggestions! Regards, Adrian

1 participants
0 comments

Re: some comments on the gutter 26 years

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > At 11:20 AM 8/13/99 +0900, SL Baur wrote: >> Andy, buttons appear and disappear with no apparent underlying reason. >> I am competely confused and disoriented. > These sound like bugs. I am doing no customization and the default ought to be fairly sane. > The current logic is: > for the currently selected buffer, put in the tabs: > - all buffers with the same major-mode > - all buffers with the same mode-name > - all buffers that have the same major-mode name prefix up to '-' > i.e. vm-mode and vm-summary-mode are considered as being in the same > group. > If gnus buffers match these criteria then you are seeing bugs. I don't know, maybe so, maybe not. Whatever is happening now is sub-optimal.

1 participants
0 comments

Re: some comments on the gutter 26 years

SL Baur

Didier Verna <verna(a)inf.enst.fr> writes in xemacs-beta(a)xemacs.org: > Jan Vroonhof <vroonhof(a)math.ethz.ch> wrote: >> What happened to the scrollable mode-line anyway? Maybe it is a good >> time to bring it back and try again. > I just don't have time to hack it again but it's still in my > pocket. Please try. It was a good hack (IMO). We really, really need it.

1 participants
0 comments

Re: cannot kill last buffer if it is named '*scratch*' 26 years

SL Baur

Karl Kleinpaste <karl(a)justresearch.com> writes in xemacs-beta(a)xemacs.org: > SL Baur wrote: >>> I have no idea where this code is from. > Andy Piper <andy(a)xemacs.org> writes: >> Not me. I dislike profanity in source code. I used too also, until censorship legislation in various governments started popping up. The next two version names of XEmacs 21.2 are aimed at censors[1] and bigots of various sorts. > mly (Richard Mlynarik) did that in early Emacs v18, circa late '86 or > early '87. He'd been tasked with terminal.el Karl, the above citation of me is a misquote. I know that the stack backtrace William posted did not come from terminal.el. Thank you for the explanation about terminal.el though. Footnotes: [1] I will do it obliquely so that it will pass censorship, but we will still know what it really means. Fuck censorship.

1 participants
0 comments

Re: [Success] XEmacs 21.1.4 "Arches", i386-pc-win32 26 years

Vin Shelton

Adrian, thanks for the reply. > Vin, I think it would be better to identify patches by their URL as > found in http://www.xemacs.org/list-archives/xemacs-patches/ Well, I have these patches in a mail folder, and using gnus it's very easy to extract the message-id. The message-id uniquely identifies the message, and we should be able to search the archive based on that string. I don't really want to have to go to the website every time I want to refer to a patch which I already have saved and ticked. Another option is for the mailinglist to add the archive URL to the message header. - vin

1 participants
0 comments

Re: Simple Q: 26 years

SL Baur

mike fabian <mike.fabian(a)mail.rhein-ruhr.de> writes in xemacs-beta(a)xemacs.org: > Jake Callery writes: >> why does xemacs leave files like "filename~" laying around? > These are backup files of the files you edited. >> and is there any way to stop that from happening? > put > (setq make-backup-files nil) > in your .emacs. This is potentially very dangerous. Backup files are turned on by default for a reason -- they provide a bit of extra safety if something goes wrong. You can turn off backup files, but be aware that the possibility of losing data is higher without them. I would suggest taking a look at backup-dir.el. It allows you put the backup files into an arbitrary directory somewhere out of the way. My question: In sample.emacs we have code that describes how to enable auto-save.el. Are enough people using backup-dir to merit putting code to enable it in sample.emacs? I use auto-save.el though I don't particularly like it. Backup files I use a great deal more often.

2 participants
1 comments

Re: [Success] XEmacs 21.1.4 "Arches", i386-pc-win32 26 years

Jan Vroonhof

Vin Shelton <acs(a)xemacs.org> writes: > Adrian, I would like to resolve this for 21.1.5, which I would like to > release this weekend. Wow that is soon! I would love to see this patch: Index: package-get.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/lisp/package-get.el,v retrieving revision 1.27 diff -u -u -r1.27 package-get.el --- package-get.el 1999/03/10 11:34:11 1.27 +++ package-get.el 1999/08/14 14:00:29 ＠＠ -245,7 +245,7 ＠＠ :type 'boolean :group 'package-get) -(defcustom package-get-require-signed-base-updates t +(defcustom package-get-require-signed-base-updates nil "*If set to a non-nil value, require explicit user confirmation for updates to the package-get database which cannot have their signature verified via PGP. When nil, updates which are not PGP signed are allowed without confirmation." > Jan, do you want me to take all of frob-face-property from 21.2 or > all of faces.el from 21.2? I'd be most comfortable with a patch, > but if you give me explicit instructions on what to steal from 21.2, > I can follow them. Given what Adrian says, I would say leave it the way it is. Jan

1 participants
0 comments

Re: xemacs size 26 years

Jan Vroonhof

Gleb Arshinov <gleb(a)broadbase.com> writes: > How would you go about doing that, giving the memory weirdness that > dumping introduces? The is a purify target in the Makefile. That makes it run temacs directly. Last time I tried I got loads of bogus malloc() warnings. I think you also have use "--with-system-malloc". Jan

1 participants
0 comments

Re: [Success] XEmacs 21.1.4 "Arches", i386-pc-win32 26 years

Adrian Aichner

>>>>> "Vin" == Vin Shelton <acs(a)xemacs.org> writes: Vin> Adrian, I would like to resolve this for 21.1.5, which I Vin> would like to release this weekend. Hello Vin, hello Jan, sorry for not getting back earlier. I have been experimenting. The original bug where loading sample.emacs did break (custom-set-faces '(font-lock-comment-face ((t (:foreground "forest green" :bold t)))) '(font-lock-doc-string-face ((t (:foreground "brown" :bold nil))))) is gone in both versions. I suggest the patch should NOT be applied to 21.1.4. Neither in 21.1.4 -vanilla nor in 21.2-b19 -vanilla can I change the `default' face to bold via M-x customize-face RET default RET without first setting Font Family. After setting Font Family: Courier New this works fine in both XEmacsen. Adrian >>>>> On 12 Aug 1999, Jan Vroonhof <vroonhof(a)math.ethz.ch> said: Jan> If it is what I think it (the frob-face-property patch) then at the Jan> very least it must be combined with the fix for it that I just applied Jan> for cvs. Vin, I think it would be better to identify patches by their URL as found in http://www.xemacs.org/list-archives/xemacs-patches/ Vin> Yes, that was the patch in question. Jan> Adrian: Jan> 1. Were you implying that with the new frob-face-property Jan> 21.1.x works better. If so 2. Does the NT version of the I don't think so any longer. Jan> -vanilla default face contain specifier specs that are device Jan> specific and/or have tags? (emacs-version) "XEmacs 21.1 (patch 4) \"Arches\" [Lucid] (i386-pc-win32) of Fri Aug 13 1999 on ZJ75T" (face-font 'default) #<font-specifier global=<unspecified> fallback=(((mswindows) . "Courier New:Regular:10::Western") ((mswindows) . "Courier:Regular:10::Western") ((mswindows) . "Fixedsys:Regular:9::Western")) 0x193> (emacs-version) "XEmacs 21.2 (beta19) \"Shinjuku\" [Lucid] (i586-pc-win32) of Fri Aug 13 1999 on ZJ75T" (face-font 'default) #<font-specifier global=<unspecified> fallback=(((mswindows) . "Courier New:Regular:10::Western") ((mswindows) . "Courier:Regular:10::Western") ((mswindows) . "Fixedsys:Regular:9::Western")) 0x1c0> Vin> -vin

1 participants
0 comments

Re: [Success] XEmacs 21.1.4 "Arches", i386-pc-win32 26 years

Vin Shelton

Adrian, I would like to resolve this for 21.1.5, which I would like to release this weekend. Jan, do you want me to take all of frob-face-property from 21.2 or all of faces.el from 21.2? I'd be most comfortable with a patch, but if you give me explicit instructions on what to steal from 21.2, I can follow them. >>>>> On 12 Aug 1999, Jan Vroonhof <vroonhof(a)math.ethz.ch> said: Jan> Vin Shelton <acs(a)xemacs.org> writes: >> Adrian and Jan, >> Just to be clear: are you recommending that I apply this patch >> Message-ID: <byaexc6i8w.fsf_-_(a)bolzano.math.ethz.ch> >> to 21.1? Jan> What patch is that. Is their an easy way to lookup patches in the Jan> archive by message ID? I don't know of any way to do this. First I tried searching on the entire string: "byaexc6i8w.fsf_-_(a)bolzano.math.ethz.ch". Not only was this very slow, it didn't work. So next I tried a partial match on "byaexc6i8w" this also failed to turn up any matches. Jan> If it is what I think it (the frob-face-property patch) then at the Jan> very least it must be combined with the fix for it that I just applied Jan> for cvs. Yes, that was the patch in question. Jan> In itself it would be no problem to upgrade frob-face-property to its Jan> 21.2.x version because it supposed to be compatible a better version. Jan> Adrian: Jan> 1. Were you implying that with the new frob-face-property 21.1.x works Jan> better. If so Jan> 2. Does the NT version of the -vanilla default face contain specifier Jan> specs that are device specific and/or have tags? Jan> In 21.1.x the default face is only face that could have something to Jan> "frob" so it is not surprising that if there are any problems, it is Jan> there. Jan> If Adrian says it works for him, upgrade to the 21.2 version. The Jan> complete one of course. -vin

1 participants
0 comments

2025

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 August 1999