Re: a new user

Tuesday, 27 October 1998

        	In general, when you notice something strange, you should try to
reproduce it under `xemacs -vanilla' (no user file, no site file, no early
packages), then `xemacs -q' (no user file) to have an idea of where the
problem comes from.

Sam Steingold <sds(a)goems.com&gt; writes:

...
 2. When a key is undefined or bound to an undefined function,
nothing
    happens.  Emacs beeps, can I make XEmacs beep too? 
	Doesn't `xemacs -vanilla' beeps ? It beeps for me in all cases (X,
xterm, console ...).

...
 3. I have 

    (set-face-foreground 'bold "Red")
    (set-face-foreground 'bold-italic "Magenta")
    (set-face-foreground 'italic "Maroon")

    in my .emacs, and I have no desire whatsoever to mess with X
    resources.  Nevertheless, I am told:
    [ ... ]
    I can understand the implementational reasons for this (the frame is
    created before reading .emacs), but I would still consider this a
    bug, possibly a design one. 
	I don't understand what you are considering a bug.

...
 4. I get this:

 (1) (initialization/error) An error has occurred while loading ~/.emacs: 
	timezone belongs to the `xemacs-base' package. If you have installed
no packages, then you don't get it, and loading it from your .emacs generates
an error. 

...
 6. There seems to be 2 parallel help/apropos facilities:
    [ ... ]
    Incidentally, it creates a lot of buffers (it doesn't reuse buffers
    as it does in Emacs). 
	It's a feature. You can have several help buffers displayed at the
same time with different informations in them. This doesn't really create many 
buffers since in XEmacs typing `q' in a Help buffer kills it by default
instead of just burry it.

...
    Also, in Emacs 20.3 "*Help*" you can click on the name
of the file in
    which the function is defined and you are taken to the definition of
    that function.  Very neat. 
	Yup.

...
 7. I use special-display-* to display all help/apropos/info etc in
    their own frames.  "q" doesn't do anything useful in them now - for
    the simple reason that it doesn't expect that, say, "*Hyper Help*"
    lives in a dedicated frame.  Emacs had the same problem, and I wrote
    a special function, `quit-window' (distributed with Emacs 20.3, file
    window.el, this is the final version, heavily modified by RMS): 
	While using `special-display-popup-frame' directly sounds a bit
obscure to me, I think that your quit function could be very usefull in many
other cases.

...
 8. I am sorry about asking a trivial (apparently) question, but I
seem to
    be unable to get the packages working.  Soppose I want xemacs to work
    with dired, gnus etc.  I have the xemacs cvs tree under
    /usr/src/xemacs/* and gnus and dired in
    /usr/src/xemacs/lisp/xemacs-gnus/* etc (all by cvs).  what do I do? 
	Packages must be installed in ${prefix}/lib/xemacs-packages and
/mule-packages for mule-only ones.

-- 
    /     /   _   _       Didier Verna        http://www.inf.enst.fr/~verna/
 - / / - / / /_/ /      E.N.S.T. INF C201.1      mailto:verna＠inf.enst.fr
/_/ / /_/ / /__ /        46 rue Barrault        Tel.   (33) 01 45 81 73 46
                      75634 Paris  cedex 13     Fax.   (33) 01 45 81 31 19

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