May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [FEATURE] Random trajectory of dropped files 25 years, 11 months

Hrvoje Niksic

Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: > to behave as Kirill describes. This was lost in the tidying up of the > dnd code. The new generic code does: > > (pop-to-buffer (find-file-noselect file)) pop-to-buffer looks wrong here. From the docstring of pop-to-buffer: Select buffer BUFNAME in some window, preferably a different one. This is not what we want here. Oliver, could you please change it? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The Lord protects children and fools... But don't push it.

1 participants
0 comments

Re: Crash in event code 25 years, 11 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Place the mouse pointer over the scrollbar, evaluate the following > code and drag the scrollbar: > > (event-over-modeline-p (next-event)) > > For me, it crashes: Same here. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: [FEATURE] Random trajectory of dropped files 25 years, 11 months

Jonathan Harris

Kirill M. Katsnelson wrote: > > When I drop a file onto XEmacs frame, I would expect that it will be > open in a window under mouse cursor. This is not the case, it seems > to appear in (other-window). The mswindows-specific drop code in mouse-mswindows-drop used to do something like: (let (window (event-window event)) ... (cond (window (select-window (window))) (switch-to-buffer (find-file-noselect file)) ... to behave as Kirill describes. This was lost in the tidying up of the dnd code. The new generic code does: (pop-to-buffer (find-file-noselect file)) Oliver, is there any reason why doing the former would be a bad thing in the new generic code? Jonathan. -- Jonathan Harris | jhar(a)tardis.ed.ac.uk London, England | Jonathan-Harris(a)psion.com

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > > The anology doesn't work as the loadpaths are computed before > > > .emacs/init.el is loaded. > > > > The analogy definitely works. `.cshrc' is a special file, and can't > > be placed just anywhere. It's not just a random executable. The same > > goes for .emacs & friends. > > No it doesn't... The reason .cshrc is a special file in a special > location is because there is no user dependent path setup in csh at > the time it gets loaded. No, that's not the reason, as I see it. The reason is that .cshrc is not *supposed* to be loaded from a random PATH location, ever. Obviously, we see things differently so my analogy doesn't work for you. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The Lord protects children and fools... But don't push it.

1 participants
0 comments

Re: custom-file 25 years, 11 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > These days I don't lie and say "You can't" since one guy tried it > anyway (with a different program) and it worked, then proceeded to > break when the interface got publically released in a different > form. You needn't lie. Say the truth: that it is undocumented because the interface might change. Say that the user should stick to `.emacs' util 21.1 when things will be bright and joyous once more. > We obviously have a different evaluation of the relative likelihoods > and importance of the different forms of breakage. I concede; you > probably know more about both. Actually, I don't. I only haven't seen a compelling reason *not* to keep the undocumented .xemacs/ code around, since it means so much for the xemacs-beta members. (except for custom-file, which unfortunately had to be reverted.) -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- What is mind? No matter. What is matter? Never mind.

1 participants
0 comments

Re: [PATCH] vc.el cleanup, THE RIGHT ONE 25 years, 11 months

Jan Vroonhof

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > vc.el did not work on Windows in some cases, because it used /bin/sh > to redirect stdout to a file. I changed it to use (with-temp-file) > for the same kludgery. Also... Please mark all you changes with a ";; XEmacs change" or something like that. It symplifies the syncs a lot. Jan

1 participants
0 comments

Re: [PATCH] vc.el cleanup, THE RIGHT ONE 25 years, 11 months

Jan Vroonhof

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > * vc.el (vc-do-command): Discard stderr of a vc process. The FSF version catches these in a seperate stream. I left that out because I wanted to have my sync ready before the freeze, but maybe it is good to do anyway. Jan

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > The anology doesn't work as the loadpaths are computed before > > .emacs/init.el is loaded. > > The analogy definitely works. `.cshrc' is a special file, and can't > be placed just anywhere. It's not just a random executable. The same > goes for .emacs & friends. No it doesn't... The reason .cshrc is a special file in a special location is because there is no user dependent path setup in csh at the time it gets loaded. There is in XEmacs (now). Jan (Of cource csh has no path mechanism at all for "source"ing files but it could have)

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Michael Sperber

>>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: Didier> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: >> >>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: >> Didier> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: >> >> >> [Chuckle ...] Actually, the official location for the late packages >> >> is .../lib/xemacs/xemacs-packages. (You don't know that because the >> >> documentation hasn't been written yet.) >> Didier> Guhh! Disgusting! Since we're under an `xemacs' Didier> directory, what sort of packages could we have appart from Didier> *xemacs* packages ?! >> >> mule-packages >> site-packages >> infodock-packages Didier> packages/[mule,site,infodock]/ Nice try, but you left one out. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Didier Verna

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > >>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: > > Didier> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > > >> [Chuckle ...] Actually, the official location for the late packages > >> is .../lib/xemacs/xemacs-packages. (You don't know that because the > >> documentation hasn't been written yet.) > > Didier> Guhh! Disgusting! Since we're under an `xemacs' > Didier> directory, what sort of packages could we have appart from > Didier> *xemacs* packages ?! > > mule-packages > site-packages > infodock-packages packages/[mule,site,infodock]/

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 May 1998