August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: some comments on the gutter 26 years

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > > Speaking of the mode-line, why do we need the `XEmacs:' string in it? So you can see what editor you started on a TTY? I would say: Ditch it. Jan

1 participants
0 comments

Re: some comments on the gutter 26 years

SL Baur

Darryl Okahata <darrylo(a)sr.hp.com> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)xemacs.org> wrote: >> Yes. Put the usually invisible major and minor modes as buttons in >> the gutter. That idea I like. I *really* want to see the Major and >> Minor modes in effect and it is irritating not to be able to scroll >> the mode-line to make them visible there. > I like the idea, but what about leaving the mode information > (everything between the parentheses) in the mode line, but move, into > the gutter, all of the cruft that pushes the mode information off the > screen? I suppose that's worth a try too. > It is called the "mode line", and moving the mode info out of > the mode line is a bit confusing. Possible candidates for gutter info > include: > * Function names, etc. displayed by the func-menu.el. > * Line/column numbers. > * VC info (RCS version, symbolic name, etc.). > * Time/date/load average. You left out: * Buffer name * Coding System in effect * Input Method State area Maybe not the Input Method State as that is as modal as the major/minor modes. It's the super-extra-extra-extra-long-buffer-names in Gnus that push all the other useful information off the mode-line. Speaking of the mode-line, why do we need the `XEmacs:' string in it?

2 participants
1 comments

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

SL Baur

This has nothing to do with the buffer name. The beep is coming from the new gutter code. The particular place you bombed doesn't do any bounds checking so it should do the same thing with any last buffer regardless of the name. Didier Verna <verna(a)inf.enst.fr> writes in xemacs-beta(a)xemacs.org: > wmperry(a)aventail.com (William M. Perry) wrote: >> Bleeeeep! >> [...] (setq fuckme buffers) [...] I have no idea where this code is from. > Waddya expect anyway ?! :-)

2 participants
1 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: > Andy Piper <andy(a)xemacs.org> wrote: >> You can put *anything* in the gutter area. It would be nice for people to >> come up with a few ideas of what would be useful. Restricting them to be buffers is pretty much useless in Gnus. I don't know which rules you currently use to select which buffers get buttons, but they are almost always the wrong ones. > Maybe I'll make people scream but anyway: I'd like to have the echo > area in the gutter. At least, I'd like to have separate places for the echo > area and the minibuffer. That's an interesting thought. I don't think I would like to run that way normally, but it would be interesting to try it out.

3 participants
3 comments

Re: some comments on the gutter 26 years

SL Baur

Paul Krause <krause(a)ibelong.net> writes in xemacs-beta(a)xemacs.org: ... > What about putting the mode-line in the gutter? Or to be more > specific, breaking the mode-line into a window-oriented mode-line > and a frame-oriented status-bar? Yes. Put the usually invisible major and minor modes as buttons in the gutter. That idea I like. I *really* want to see the Major and Minor modes in effect and it is irritating not to be able to scroll the mode-line to make them visible there.

3 participants
2 comments

Re: GCPRUG in run_hooks [was Re: Another 21.2.19 crash] 26 years

Jan Vroonhof

Raymond Toy <toy(a)rtp.ericsson.se> writes: > I'll try out your patch. This is the first time this crash has > happened since b19 came out, so it's not a frequent bug, for the > things that I do. I presume Andy's gutter update stuff runs of those hooks. That would explain why it is triggered now. Jan

2 participants
1 comments

Re: XEmacs in the gutter (Re: gutter fixes) 26 years

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: >> Another possibility might be to only show tabs for buffers that don't >> have windows. In both of the examples I posted earlier, the tabs represented buffers not mapped to any window. In this buffer I'm now writing in, there are two tabs `*sent mail to xemacs-review(a)xemacs.org*' and `*send mail*<3>' both of which are buffers that have been buried and will never see the light of a window again until I start housecleaning and deleting old unused buffers via the C-x C-b buffer menu. > This breaks the metphor badly as the top tab would always be empty. If what I've been experiencing in the past week or so is required by the metaphor, then it is completely and totally broken and we probably should remove this feature now. I don't like metaphors that don't make any sense in the context they are used in. http://www.iarchitect.com/mshame.htm

2 participants
1 comments

Re: some comments on the gutter 26 years

Didier Verna

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. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: some comments on the gutter 26 years

Jan Vroonhof

Darryl Okahata <darrylo(a)sr.hp.com> writes: > * Function names, etc. displayed by the func-menu.el. > > * Line/column numbers. > > * VC info (RCS version, symbolic name, etc.). These are window specific, so I am not sure they are that well suited for a frame-wide gutter. (As I am editing this the modeline reads ESC/Quote--**--XEmacs: *wide reply to Darryl Okahata on xemacs-beta(a)xemacs.org * F | No mode in the mode line at all ! What happened to the scrollable mode-line anyway? Maybe it is a good time to bring it back and try again. Jan

1 participants
0 comments

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

Didier Verna

Steve Baur wrote: > [Unless sanity has prevailed while I wasn't looking, this thread is > illegal in Australia. Why ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

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