January 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [PATCH] xemacs-base/add-log.el customise glitch 24 years, 10 months

Hrvoje Niksic

Valdis.Kletnieks(a)vt.edu writes: > On Thu, 13 Jan 2000 09:01:32 +0100, Andreas Jaeger said: > > Btw. there's no need to CC xemacs-beta. > > Some of us (like me) subscribe to xemacs-beta, but not -patches. It's OK to post patches to xemacs-beta, if you want the beta community to review them. If the developer doesn't consider the patch controversial or interesting, he can just mail it to xemacs-patches, where it should get the reviewers' attention and a stamp of approval or veto. > As an alternative, may I suggest this: The Enlightenment crew has a > daily/weekly 'cvs commits' mailing list, that automagically mails > all interested subscribers a summary of recent activity. But so do we! Subscribe to xemacs-cvs(a)xemacs.org if you're interested.

2 participants
1 comments

Re: [PATCH] xemacs-base/add-log.el customise glitch 24 years, 10 months

Andreas Jaeger

>>>>> Kirill 'Big K' Katsnelson writes: kkm> xemacs-base/add-log.el incorrectly typed the add-log-current-defun-function kkm> defcustom as 'boolean. kkm> Big K kkm> 2000-01-12 Kirill 'Big K' Katsnelson <kkm(a)dtmx.com> kkm> * add-log.el (add-log-current-defun-function): Changed :type of kkm> this defcustom to the correct one, 'function. Thanks, I've commited this to our CVS archive now. Btw. there's no need to CC xemacs-beta. Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

2 participants
1 comments

Re: Long absence/near inactivity 24 years, 10 months

Jan Vroonhof

Paul Bibilo <peb(a)delcam.com> writes: > This was the key to it. I'm back in business again with a working > XEmacs. > > Thanks to Jan and Colin, and Max Matveev who actually wrote the fix the original problem. Jan

1 participants
0 comments

Re: Long absence/near inactivity 24 years, 10 months

Paul Bibilo

Jan Vroonhof writes: > Colin Rafferty <colin.rafferty(a)msdw.com> writes: > > > I noticed that one of the patches is to `configure.in', which will > > mean that if you just apply the patch, you will not get the change > > that you need, which is to `configure'. Make sure that you are > > linking in unexelfsgi.o, and not unexelf.o. > > i.e. don't forget to run autoconf after applying the patch. > This was the key to it. I'm back in business again with a working XEmacs. Thanks to Jan and Colin, -- Paul

1 participants
0 comments

Re: Better history and completion support for Info 24 years, 10 months

Didier Verna

Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> wrote: > FSF Emacs has better completion support when you type `g'. > Also, use DEFAULT argument when typing `g', `f' and `m' to > record default in history. > > 1999-12-20 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> > > * info.el (Info-read-node-completion-table): New variable. > (Info-read-node-name-1): New function. > (Info-read-node-name): Use it. > (Info-follow-reference): Use DEFAULT argument of completing-read. > (Info-menu): Ditto. Hayashi-San, it seems that these changes have completely broken the completion mecanism for me. The symptom is: BEFORE: I didn't have any completion in the minibuffer when typing `g', but giving a full node name would do it. AFTER: I don't have any completion either, but now even the full node name barfs at me. This is probably because of a new require-match argument to completing-read or something. Looking at hte variable Info-current-file-completions, I see that only the Top node is present. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

Where should I add document about bookmark.el? 24 years, 10 months

Yoshiki Hayashi

XEmacs manual doesn't document bookmark.el. I'd like to add some document based on FSF Emacs' manual. bookmark.el is in edit-utils package. So the question is, where should I document it? Perhaps I should create edit-utils.texi and add ＠xref from xemacs.texi but I'm not sure. -- Yoshiki Hayashi

1 participants
0 comments

Re: [PATCH] startup.el "Load .emacs" menu item fix 24 years, 10 months

Didier Verna

> "Kirill 'Big K' Katsnelson" <kkm(a)dtmx.com> Now, look who's here! We thought you were dead or something :-) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

Re: [PATCH] startup.el "Load .emacs" menu item fix 24 years, 10 months

Jan Vroonhof

"Kirill 'Big K' Katsnelson" <kkm(a)dtmx.com> writes: He's back! > xemacs -q => "Load .emacs" => signal wrong number of arguments. > > What a pleasure hacking xemacs after a 1.55 year break!!! :) Welcome back! Can you disclose where you have been? Just busy with work and real life? Jan P.S. There were some attempts to contact you in the past. Most of the stuff still lists your .ru address. Would you mind submitting a patch to about.el to update your info?

1 participants
0 comments

Re: check process state before accessing coding_stream (fix PR#1061) 24 years, 10 months

Gunnar Evermann

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > > > * process.c (Fprocess_input_coding_system): check whether process > > is still alive > > Approved. Recommened for 21.1. I think we should still apply the above patch to 21.1. > > process = get_process (process); > > + if (!PROCESS_LIVE_P (process)) > > + error ("Process %s is not active", > > + XSTRING_DATA (XPROCESS (process)->name)); > > + > > return decoding_stream_coding_system (XLSTREAM (XPROCESS (process)->coding_instream) ); > > You might want to turn this into a CHECK_PROCESS_LIVE(process) > macro[1], to be consistent with other such checks. yes, good point. I had actually looked for. I have now defined CHECK_LIVE_PROCESS and, to make all this consistent, a Lisp Function process-live-p (why wasn´t that defined before? Surely it is useful and nicer to use than process-status?). I also made the existing PROCESS_LIVE_P consistent with the other _LIVE_P macros and used it where possible (OK, so I got a bit carried away hacking process.c :-). There is one use of PROCESS_LIVE_P left (in process_send_signal) that could be replaced by CHECK_LIVE_PROCESS. I haven´t done that yet because the resulting error would be different (i.e. we wouldn´t print the process name anymore). any opinions on that? I´ll submit the crash test case for the test-suite separately. I would appreciate comments from people more familiar with process.c (Ben?). 1999-12-18 Gunnar Evermann <ge204(a)eng.cam.ac.uk> * process.h (PROCESS_LIVE_P): Modify to take a Lisp_Process instead of a Lisp_Object as argument to make it consistent with the other LIVE_P macros. (CHECK_LIVE_PROCESS): New macro. * process.c: Declare Qprocess_live_p. (Fprocess_live_p): New function. (create_process): Use PROCESS_LIVE_P. (read_process_output): Ditto. (set_process_filter): Ditto. (Fdelete_process): Ditto. (kill_buffer_processes): Ditto (Fprocess_input_coding_system): Check whether process is still alive (fix PR#1061). (Fprocess_output_coding_system): Ditto. (Fprocess_coding_system): Ditto. (Fset_process_input_coding_system): Ditto. (Fset_process_output_coding_system): Ditto. --- src/process.h.orig Sat Dec 18 16:39:02 1999 +++ src/process.h Sat Dec 18 16:39:11 1999 ＠＠ -45,7 +45,13 ＠＠ #define XSETPROCESS(x, p) XSETRECORD (x, p, process) #define PROCESSP(x) RECORDP (x, process) #define CHECK_PROCESS(x) CHECK_RECORD (x, process) -#define PROCESS_LIVE_P(x) (!NILP (XPROCESS(x)->pipe_instream)) +#define PROCESS_LIVE_P(x) (!NILP ((x)->pipe_instream)) + +#define CHECK_LIVE_PROCESS(x) do { \ + CHECK_PROCESS (x); \ + if (! PROCESS_LIVE_P (XPROCESS (x))) \ + dead_wrong_type_argument (Qprocess_live_p, (x)); \ +} while (0) #ifdef emacs --- src/process.c.orig Sat Dec 18 16:43:27 1999 +++ src/process.c Sat Dec 18 17:32:40 1999 ＠＠ -58,7 +58,7 ＠＠ #include "systty.h" #include "syswait.h" -Lisp_Object Qprocessp; +Lisp_Object Qprocessp, Qprocess_live_p; /* Process methods */ struct process_methods the_process_methods; ＠＠ -257,6 +257,14 ＠＠ return PROCESSP (obj) ? Qt : Qnil; } +DEFUN ("process-live-p", Fprocess_live_p, 1, 1, 0, /* +Return t if OBJECT is a process that is alive. +*/ + (obj)) +{ + return PROCESSP (obj) && PROCESS_LIVE_P (XPROCESS (obj)) ? Qt : Qnil; +} + DEFUN ("process-list", Fprocess_list, 0, 0, 0, /* Return a list of all processes. */ ＠＠ -510,7 +518,7 ＠＠ pid = PROCMETH (create_process, (p, argv, nargv, program, cur_dir)); p->pid = make_int (pid); - if (!NILP(p->pipe_instream)) + if (PROCESS_LIVE_P (p)) event_stream_select_process (p); } ＠＠ -823,7 +831,7 ＠＠ Really, the loop in execute_internal_event() should check itself for a process-filter change, like in status_notify(); but the struct Lisp_Process is not exported outside of this file. */ - if (NILP(p->pipe_instream)) + if (!PROCESS_LIVE_P (p)) return -1; /* already closed */ if (!NILP (p->filter) && (p->filter_does_read)) ＠＠ -1032,7 +1040,7 ＠＠ set_process_filter (Lisp_Object proc, Lisp_Object filter, int filter_does_read) { CHECK_PROCESS (proc); - if (PROCESS_LIVE_P (proc)) { + if (PROCESS_LIVE_P (XPROCESS (proc))) { if (EQ (filter, Qt)) event_stream_unselect_process (XPROCESS (proc)); else ＠＠ -1121,6 +1129,7 ＠＠ (process)) { process = get_process (process); + CHECK_LIVE_PROCESS (process); return decoding_stream_coding_system (XLSTREAM (XPROCESS (process)->coding_instream) ); } ＠＠ -1130,6 +1139,7 ＠＠ (process)) { process = get_process (process); + CHECK_LIVE_PROCESS (process); return encoding_stream_coding_system (XLSTREAM (XPROCESS (process)->coding_outstream)); } ＠＠ -1139,6 +1149,7 ＠＠ (process)) { process = get_process (process); + CHECK_LIVE_PROCESS (process); return Fcons (decoding_stream_coding_system (XLSTREAM (XPROCESS (process)->coding_instream)), encoding_stream_coding_system ＠＠ -1153,6 +1164,8 ＠＠ { codesys = Fget_coding_system (codesys); process = get_process (process); + CHECK_LIVE_PROCESS (process); + set_decoding_stream_coding_system (XLSTREAM (XPROCESS (process)->coding_instream), codesys); return Qnil; ＠＠ -1166,6 +1179,8 ＠＠ { codesys = Fget_coding_system (codesys); process = get_process (process); + CHECK_LIVE_PROCESS (process); + set_encoding_stream_coding_system (XLSTREAM (XPROCESS (process)->coding_outstream), codesys); return Qnil; ＠＠ -1527,7 +1542,7 ＠＠ if (network_connection_p (proc)) error ("Network connection %s is not a subprocess", XSTRING_DATA (XPROCESS(proc)->name)); - if (!PROCESS_LIVE_P (proc)) + if (!PROCESS_LIVE_P (XPROCESS (proc))) error ("Process %s is not active", XSTRING_DATA (XPROCESS(proc)->name)); ＠＠ -1883,7 +1898,7 ＠＠ p->tick++; process_tick++; } - else if (!NILP(p->pipe_instream)) + else if (PROCESS_LIVE_P (p)) { Fkill_process (proc, Qnil); /* Do this now, since remove_process will make sigchld_handler do nothing. */ ＠＠ -1915,7 +1930,7 ＠＠ { if (network_connection_p (proc)) Fdelete_process (proc); - else if (!NILP (XPROCESS (proc)->pipe_instream)) + else if (PROCESS_LIVE_P (XPROCESS (proc))) process_send_signal (proc, SIGHUP, 0, 1); } } ＠＠ -1978,6 +1993,7 ＠＠ syms_of_process (void) { defsymbol (&Qprocessp, "processp"); + defsymbol (&Qprocess_live_p, "process-live-p"); defsymbol (&Qrun, "run"); defsymbol (&Qstop, "stop"); defsymbol (&Qopen, "open"); ＠＠ -1991,6 +2007,7 ＠＠ #endif DEFSUBR (Fprocessp); + DEFSUBR (Fprocess_live_p); DEFSUBR (Fget_process); DEFSUBR (Fget_buffer_process); DEFSUBR (Fdelete_process);

5 participants
11 comments

Re: Tabs, the gutter, `window-height', scrolling. (Was: Re: OK I give up) 24 years, 10 months

Jan Vroonhof

Andy Piper <andy(a)xemacs.org> writes: > > I looked at `window-height', and see that it accounts for the > > modeline and possible scrollbar, but it does not (yet) account for > > the tab gutter, and needs to. I am not capable at this time of > > making that patch, or I would. I just plain don't understand things > > well enough yet to monkey with it. > > If page down is using window-height then that is the bug - it should use > window-displayed-height instead. window-height should yield consistent > geometries, not accurate numbers of lines. Aha... So this is what is breaking things like ispell's computation for its window. I really think you want to change window height to take the gutter into account. window-height is really meant to do as good an approximation of window-displayed-height without doing a redisplay. The main purpose is to make code from the pre-varying-height-font era (i.e. FSF code) work correctly. Jan

3 participants
2 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 January 2000