X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=info%2Fxemacs-faq.info-2;h=62faa2bdf184943e1a26b7cca0d187fe7ccf59fb;hb=98769b42a33fd8236341ac4175165b2dab7ceae4;hp=e58bb3dd820289e790c08abbd1d50ae77e0ffa9b;hpb=81572e9b4653c5545c2eb43e87dec439f356c19c;p=chise%2Fxemacs-chise.git diff --git a/info/xemacs-faq.info-2 b/info/xemacs-faq.info-2 index e58bb3d..62faa2b 100644 --- a/info/xemacs-faq.info-2 +++ b/info/xemacs-faq.info-2 @@ -1,210 +1,12 @@ -This is Info file ../info/xemacs-faq.info, produced by Makeinfo version -1.68 from the input file xemacs-faq.texi. +This is ../info/xemacs-faq.info, produced by makeinfo version 4.0b from +xemacs-faq.texi. INFO-DIR-SECTION XEmacs Editor START-INFO-DIR-ENTRY -* FAQ: (xemacs-faq). XEmacs FAQ. +* FAQ: (xemacs-faq). XEmacs FAQ. END-INFO-DIR-ENTRY  -File: xemacs-faq.info, Node: Q2.0.2, Next: Q2.0.3, Prev: Q2.0.1, Up: Installation - -Q2.0.2: XEmacs is too big -------------------------- - - Although this entry has been written for XEmacs 19.13, most of it -still stands true. - - Steve Baur writes: - - The 45MB of space required by the installation directories can be - reduced dramatically if desired. Gzip all the .el files. Remove - all the packages you'll never want to use (or even ones you do - like the two obsolete mailcrypts and Gnus 4 in 19.13). Remove the - TexInfo manuals. Remove the Info (and use just hardcopy versions - of the manual). Remove most of the stuff in etc. Remove or gzip - all the source code. Gzip or remove the C source code. Configure - it so that copies are not made of the support lisp. I'm not - advocating any of these things, just pointing out ways to reduce - the disk requirements if desired. - - Now examine the space used by directory: - - 0 /usr/local/bin/xemacs - 2048 /usr/local/bin/xemacs-19.13 - - 1546 /usr/local/lib/xemacs-19.13/i486-miranova-sco3.2v4.2 - 1158 /usr/local/lib/xemacs-19.13/i486-unknown-linux1.2.13 - - You need to keep these. XEmacs isn't stripped by default in - installation, you should consider stripping. That will save you - about 5MB right there. - - 207 /usr/local/lib/xemacs-19.13/etc/w3 - 122 /usr/local/lib/xemacs-19.13/etc/sounds - 18 /usr/local/lib/xemacs-19.13/etc/sparcworks - 159 /usr/local/lib/xemacs-19.13/etc/vm - 6 /usr/local/lib/xemacs-19.13/etc/e - 21 /usr/local/lib/xemacs-19.13/etc/eos - 172 /usr/local/lib/xemacs-19.13/etc/toolbar - 61 /usr/local/lib/xemacs-19.13/etc/ns - 43 /usr/local/lib/xemacs-19.13/etc/gnus - - These are support directories for various packages. In general - they match a directory under - ./xemacs-19.13/lib/xemacs-19.13/lisp/. If you do not require the - package, you may delete or gzip the support too. - - 1959 /usr/local/lib/xemacs-19.13/etc - 175 /usr/local/lib/xemacs-19.13/lisp/bytecomp - 340 /usr/local/lib/xemacs-19.13/lisp/calendar - 342 /usr/local/lib/xemacs-19.13/lisp/comint - 517 /usr/local/lib/xemacs-19.13/lisp/dired - 42 /usr/local/lib/xemacs-19.13/lisp/electric - 212 /usr/local/lib/xemacs-19.13/lisp/emulators - 238 /usr/local/lib/xemacs-19.13/lisp/energize - 289 /usr/local/lib/xemacs-19.13/lisp/gnus - 457 /usr/local/lib/xemacs-19.13/lisp/ilisp - 1439 /usr/local/lib/xemacs-19.13/lisp/modes - 2276 /usr/local/lib/xemacs-19.13/lisp/packages - 1040 /usr/local/lib/xemacs-19.13/lisp/prim - 176 /usr/local/lib/xemacs-19.13/lisp/pcl-cvs - 154 /usr/local/lib/xemacs-19.13/lisp/rmail - 3 /usr/local/lib/xemacs-19.13/lisp/epoch - 45 /usr/local/lib/xemacs-19.13/lisp/term - 860 /usr/local/lib/xemacs-19.13/lisp/utils - 851 /usr/local/lib/xemacs-19.13/lisp/vm - 13 /usr/local/lib/xemacs-19.13/lisp/vms - 157 /usr/local/lib/xemacs-19.13/lisp/x11 - 19 /usr/local/lib/xemacs-19.13/lisp/tooltalk - 14 /usr/local/lib/xemacs-19.13/lisp/sunpro - 291 /usr/local/lib/xemacs-19.13/lisp/games - 198 /usr/local/lib/xemacs-19.13/lisp/edebug - 619 /usr/local/lib/xemacs-19.13/lisp/w3 - 229 /usr/local/lib/xemacs-19.13/lisp/eos - 55 /usr/local/lib/xemacs-19.13/lisp/iso - 59 /usr/local/lib/xemacs-19.13/lisp/mailcrypt - 187 /usr/local/lib/xemacs-19.13/lisp/eterm - 356 /usr/local/lib/xemacs-19.13/lisp/ediff - 408 /usr/local/lib/xemacs-19.13/lisp/hyperbole/kotl - 1262 /usr/local/lib/xemacs-19.13/lisp/hyperbole - 247 /usr/local/lib/xemacs-19.13/lisp/hm--html-menus - 161 /usr/local/lib/xemacs-19.13/lisp/mh-e - 299 /usr/local/lib/xemacs-19.13/lisp/viper - 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-x - 4 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/DocWindow.nib - 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/InfoPanel.nib - 3 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj/TreeView.nib - 11 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx/English.lproj - 53 /usr/local/lib/xemacs-19.13/lisp/oobr/tree-nx - 466 /usr/local/lib/xemacs-19.13/lisp/oobr - 14142 /usr/local/lib/xemacs-19.13/lisp - - These are all Emacs Lisp source code and bytecompiled object code. - You may safely gzip everything named *.el here. You may remove - any package you don't use. *Nothing bad will happen if you delete - a package that you do not use*. You must be sure you do not use - it though, so be conservative at first. - - Possible candidates for deletion include w3 (newer versions exist, - or you may just use Lynx or Netscape for web browsing), games, - hyperbole, mh-e, hm-html-menus (better packages exist), vm, viper, - oobr, gnus (new versions exist), etc. Ask yourself, *Do I ever - want to use this package?* If the answer is no, then it is a - candidate for removal. - - First, gzip all the .el files. Then go about package by package - and start gzipping the .elc files. Then run XEmacs and do - whatever it is you normally do. If nothing bad happens, then - delete the directory. Be conservative about deleting directories, - and it would be handy to have a backup tape around in case you get - too zealous. - - `prim', `modes', `packages', and `utils' are four directories you - definitely do *not* want to delete, although certain packages can - be removed from them if you do not use them. - - 1972 /usr/local/lib/xemacs-19.13/info - - These are online texinfo sources. You may either gzip them or - remove them. In either case, `C-h i' (info mode) will no longer - work. - - 20778 /usr/local/lib/xemacs-19.13 - - The 20MB achieved is less than half of what the full distribution - takes up, *and* can be achieved without deleting a single file. - - Giacomo Boffi provides this procedure: - - Substitute `/usr/local/lib/' with the path where the xemacs tree is - rooted, then use this script: - - #!/bin/sh - - r=/usr/local/lib/xemacs-19.13/lisp - - cd $r ; rm -f cmpr ; touch cmpr - - du -s . - - for d in * ; do - if test -d $d ; then - cd $d - for f in *.el ; do - # compress (remove) only (ONLY) the sources that have a - # corresponding compiled file --- do not (DO NOT) - # touch other sources - if test -f ${f}c ; then gzip -v9 $f >> $r/cmpr ; fi - done - cd .. - fi - done - - du -s . - - A step beyond would be substituting `rm -f' for `gzip -v9', but - you have to be desperate for removing the sources (remember that - emacs can access compressed files transparently). - - Also, a good megabyte could easily be trimmed from the $r/../etc - directory, e.g., the termcap files, some O+NEWS, others that I - don't remember as well. - - XEmacs 21.0 will unbundle the lisp hierarchy and allow the - installer to choose exactly how much support code gets installed. - - -File: xemacs-faq.info, Node: Q2.0.3, Next: Q2.0.4, Prev: Q2.0.2, Up: Installation - -Q2.0.3: Compiling XEmacs with Netaudio. ---------------------------------------- - - What is the best way to compile XEmacs with the netaudio system, -since I have got the netaudio system compiled but installed at a weird -place, I am not root. Also in the READMEs it does not say anything -about compiling with the audioserver? - - You should only need to add some stuff to the configure command line. -To tell it to compile in netaudio support: `--with-sound=both', or -`--with-sound=nas' if you don't want native sound support for some -reason.) To tell it where to find the netaudio includes and libraries: - - --site-libraries=WHATEVER - --site-includes=WHATEVER - - Then (fingers crossed) it should compile and it will use netaudio if -you have a server running corresponding to the X server. The netaudio -server has to be there when XEmacs starts. If the netaudio server goes -away and another is run, XEmacs should cope (fingers crossed, error -handling in netaudio isn't perfect). - - BTW, netaudio has been renamed as it has a name clash with something -else, so if you see references to NAS or Network Audio System, it's the -same thing. It also might be found at -`ftp://ftp.x.org/contrib/audio/nas/'. - - File: xemacs-faq.info, Node: Q2.0.4, Next: Q2.0.5, Prev: Q2.0.3, Up: Installation Q2.0.4: Problems with Linux and ncurses. @@ -229,8 +31,8 @@ Q2.0.5: Do I need X11 to run XEmacs? ------------------------------------ No. The name "XEmacs" is unfortunate in the sense that it is *not* -an X Window System-only version of Emacs. Starting with 19.14 XEmacs -has full color support on a color-capable character terminal. +an X Window System-only version of Emacs. XEmacs has full color +support on a color-capable character terminal.  File: xemacs-faq.info, Node: Q2.0.6, Next: Q2.0.7, Prev: Q2.0.5, Up: Installation @@ -270,7 +72,7 @@ ELF libraries are out of date. You have the following options: `_h_errno^@' with `h_errno^@^@'. Any version of Emacs will suffice. If you don't understand how to do this, don't do it. - 3. Rebuild XEmacs yourself - any working ELF version of libc should be + 3. Rebuild XEmacs yourself--any working ELF version of libc should be O.K. Hrvoje Niksic writes: @@ -280,7 +82,7 @@ ELF libraries are out of date. You have the following options: perl -pi -e 's/_h_errno\0/h_errno\0\0/g' \ /usr/local/bin/xemacs-19.14 - NB: You *must* patch `/usr/local/bin/xemacs-19.14', and not + NB: You _must_ patch `/usr/local/bin/xemacs-19.14', and not `xemacs' because `xemacs' is a link to `xemacs-19.14'; the Perl `-i' option will cause unwanted side-effects if applied to a symbolic link. @@ -331,8 +133,8 @@ PNG Compface `ftp://ftp.cs.indiana.edu/pub/faces/compface/'. This library has been frozen for about 6 years, and is distributed without version - numbers. *It should be compiled with the same options that X11 was - compiled with on your system*. The version of this library at + numbers. _It should be compiled with the same options that X11 was + compiled with on your system_. The version of this library at XEmacs.org includes the `xbm2xface.pl' script, written by , which may be useful when generating your own xface. @@ -385,7 +187,7 @@ that stock SunOS systems do not ship with DNS resolver code in libc. then proceed to link against the DNS resolver library code.  -File: xemacs-faq.info, Node: Q2.0.12, Next: Q2.1.1, Prev: Q2.0.11, Up: Installation +File: xemacs-faq.info, Node: Q2.0.12, Next: Q2.0.13, Prev: Q2.0.11, Up: Installation Q2.0.12: Why can't I strip XEmacs? ---------------------------------- @@ -428,7 +230,49 @@ Q2.0.12: Why can't I strip XEmacs? /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout  -File: xemacs-faq.info, Node: Q2.1.1, Next: Q2.1.2, Prev: Q2.0.12, Up: Installation +File: xemacs-faq.info, Node: Q2.0.13, Next: Q2.0.14, Prev: Q2.0.12, Up: Installation + +Q2.0.13: I don't need no steenkin' packages. Do I? (NEW) +--------------------------------------------------------- + + Strictly speaking, no. XEmacs will build and install just fine +without any packages installed. However, only the most basic editing +functions will be available with no packages installed, so installing +packages is an essential part of making your installed XEmacs _useful_. + + +File: xemacs-faq.info, Node: Q2.0.14, Next: Q2.1.1, Prev: Q2.0.13, Up: Installation + +Q2.0.12: How do I figure out which packages to install? (NEW) +------------------------------------------------------------- + + Many people really liked the old way that packages were bundled and +do not want to mess with packages at all. You can grab all the +packages at once like you used to with old XEmacs versions. Download +the file + + `xemacs-sumo.tar.gz' + + For an XEmacs compiled with Mule you also need + + `xemacs-mule-sumo.tar.gz' + + from the `packages' directory on your XEmacs mirror archive. N.B. +They are called 'Sumo Tarballs' for good reason. They are currently +about 15MB and 2.3MB (gzipped) respectively. + + Install them by + + `cd $prefix/lib/xemacs ; gunzip -c | tar xf -' + + See README.packages for more detailed installation instructions. + + As the Sumo tarballs are not regenerated as often as the individual +packages, it is recommended that you use the automatic package tools +afterwards to pick up any recent updates. + + +File: xemacs-faq.info, Node: Q2.1.1, Next: Q2.1.2, Prev: Q2.0.14, Up: Installation 2.1: Trouble Shooting ===================== @@ -633,10 +477,10 @@ Q2.1.8: got (wrong-type-argument color-instance-p nil) color backgrounds and foregrounds into your `.../app-defaults/Emacs' like: - *Foreground: Black ;everything will be of black on grey95, - *Background: Grey95 ;unless otherwise specified. - *cursorColor: Red3 ;red3 cursor with grey95 border. - *pointerColor: Red3 ;red3 pointer with grey95 border. + *Foreground: Black ;everything will be of black on grey95, + *Background: Grey95 ;unless otherwise specified. + *cursorColor: Red3 ;red3 cursor with grey95 border. + *pointerColor: Red3 ;red3 pointer with grey95 border. Natalie Kershaw adds: @@ -790,7 +634,7 @@ Q2.1.14: `C-g' doesn't work for me. Is it broken? Morten Welinder writes: - On some (but *not* all) machines a hung XEmacs can be revived by + On some (but _not_ all) machines a hung XEmacs can be revived by `kill -FPE '. This is a hack, of course, not a solution. This technique works on a Sun4 running 4.1.3_U1. To see if it works for you, start another XEmacs and test with that first. If @@ -955,6 +799,7 @@ debugger. Here are some hints: `src/gdbinit'. This had the disadvantage of not being sourced automatically by gdb, so you had to set that up yourself. +  File: xemacs-faq.info, Node: Q2.1.16, Next: Q2.1.17, Prev: Q2.1.15, Up: Installation @@ -1089,13 +934,11 @@ and 20.x. I am using Linux. #define MAIL_USE_FLOCK  -File: xemacs-faq.info, Node: Q2.1.24, Prev: Q2.1.23, Up: Installation +File: xemacs-faq.info, Node: Q2.1.24, Next: Q2.1.25, Prev: Q2.1.23, Up: Installation Q2.1.24: XEmacs won't start without network. (NEW) --------------------------------------------------- - Q2.1.23: Movemail on Linux does not work for XEmacs 19.15 and later. - If XEmacs starts when you're on the network, but fails when you're not on the network, you may be missing a "localhost" entry in your `/etc/hosts' file. The file should contain an entry like: @@ -1105,6 +948,19 @@ not on the network, you may be missing a "localhost" entry in your Add that line, and XEmacs will be happy.  +File: xemacs-faq.info, Node: Q2.1.25, Prev: Q2.1.24, Up: Installation + +Q2.1.25:: After upgrading, XEmacs won't do `foo' any more! (NEW) +----------------------------------------------------------------- + + You have been used to doing `foo', but now when you invoke it (or +click the toolbar button or select the menu item), nothing (or an error) +happens. The simplest explanation is that you are missing a package +that is essential to you. You can either track it down and install it +(there is a list of packages and brief descriptions of their contents in +`etc/PACKAGES'), or install the `Sumo Tarball' (see *note Q2.0.14::). + + File: xemacs-faq.info, Node: Customization, Next: Subsystems, Prev: Installation, Up: Top 3 Customization and Options @@ -1115,7 +971,7 @@ section is devoted to Customization and screen settings. * Menu: -Customization--Emacs Lisp and `.emacs': +Customization---Emacs Lisp and `.emacs': * Q3.0.1:: What version of Emacs am I running? * Q3.0.2:: How do I evaluate Elisp expressions? * Q3.0.3:: `(setq tab-width 6)' behaves oddly. @@ -1159,9 +1015,9 @@ The Modeline: * Q3.5.1:: How can I bind complex functions (or macros) to keys? * Q3.5.2:: How can I stop down-arrow from adding empty lines to the bottom of my buffers? * Q3.5.3:: How do I bind C-. and C-; to scroll one line up and down? -* Q3.5.4:: Globally binding `Delete'? +* Q3.5.4:: Globally binding Delete? * Q3.5.5:: Scrolling one line at a time. -* Q3.5.6:: How to map `Help' key alone on Sun type4 keyboard? +* Q3.5.6:: How to map Help key alone on Sun type4 keyboard? * Q3.5.7:: How can you type in special characters in XEmacs? * Q3.5.8:: Why does `(global-set-key [delete-forward] 'delete-char)' complain? * Q3.5.9:: How do I make the Delete key delete forward? @@ -1181,7 +1037,7 @@ The Mouse and Highlighting: * Q3.7.5:: Why does cut-and-paste not work between XEmacs and a cmdtool? * Q3.7.6:: How I can set XEmacs up so that it pastes where the text cursor is? * Q3.7.7:: How do I select a rectangular region? -* Q3.7.8:: Why does `M-w' take so long? +* Q3.7.8:: Why does M-w take so long? The Menubar and Toolbar: * Q3.8.1:: How do I get rid of the menu (or menubar)? @@ -1200,7 +1056,7 @@ Text Selections: * Q3.10.1:: How can I turn off or change highlighted selections? * Q3.10.2:: How do I get that typing on an active region removes it? * Q3.10.3:: Can I turn off the highlight during isearch? -* Q3.10.4:: How do I turn off highlighting after `C-x C-p' (mark-page)? +* Q3.10.4:: How do I turn off highlighting after C-x C-p (mark-page)? * Q3.10.5:: The region disappears when I hit the end of buffer while scrolling.  @@ -1274,3 +1130,188 @@ front of the load-path, the other at the end: (push (expand-file-name "~keithh/.emacsdir") load-path) + +File: xemacs-faq.info, Node: Q3.0.5, Next: Q3.0.6, Prev: Q3.0.4, Up: Customization + +Q3.0.5: How to check if a lisp function is defined? +--------------------------------------------------- + + Use the following elisp: + + (fboundp 'foo) + + It's almost always a mistake to test `emacs-version' or any similar +variables. + + Instead, use feature-tests, such as `featurep', `boundp', `fboundp', +or even simple behavioral tests, eg.: + + (defvar foo-old-losing-code-p + (condition-case nil (progn (losing-code t) nil) + (wrong-number-of-arguments t))) + + There is an incredible amount of broken code out there which could +work much better more often in more places if it did the above instead +of trying to divine its environment from the value of one variable. + + +File: xemacs-faq.info, Node: Q3.0.6, Next: Q3.0.7, Prev: Q3.0.5, Up: Customization + +Q3.0.6: Can I force the output of `(face-list)' to a buffer? +------------------------------------------------------------ + + It would be good having it in a buffer, as the output of +`(face-list)' is too wide to fit to a minibuffer. + + Evaluate the expression in the `*scratch*' buffer with point after +the rightmost paren and typing `C-j'. + + If the minibuffer smallness is the only problem you encounter, you +can simply press `C-h l' to get the former minibuffer contents in a +buffer. + + +File: xemacs-faq.info, Node: Q3.0.7, Next: Q3.0.8, Prev: Q3.0.6, Up: Customization + +Q3.0.7: Font selections in don't get saved after `Save Options'. +---------------------------------------------------------------- + + For XEmacs 19.14 and previous: + + John Mann writes: + + You have to go to Options->Frame Appearance and unselect + `Frame-Local Font Menu'. If this option is selected, font changes + are only applied to the _current_ frame and do _not_ get saved + when you save options. + + For XEmacs 19.15 and later: + + Implement the above as well as set the following in your `.emacs' + + (setq options-save-faces t) + + +File: xemacs-faq.info, Node: Q3.0.8, Next: Q3.0.9, Prev: Q3.0.7, Up: Customization + +Q3.0.8: How do I get a single minibuffer frame? +----------------------------------------------- + + Vin Shelton writes: + + (setq initial-frame-plist '(minibuffer nil)) + (setq default-frame-plist '(minibuffer nil)) + (setq default-minibuffer-frame + (make-frame + '(minibuffer only + width 86 + height 1 + menubar-visible-p nil + default-toolbar-visible-p nil + name "minibuffer" + top -2 + left -2 + has-modeline-p nil))) + (frame-notice-user-settings) + + *Please note:* The single minibuffer frame may not be to everyone's +taste, and there any number of other XEmacs options settings that may +make it difficult or inconvenient to use. + + +File: xemacs-faq.info, Node: Q3.0.9, Next: Q3.1.1, Prev: Q3.0.8, Up: Customization + +Q3.0.9: What is `Customize'? +---------------------------- + + Starting with XEmacs 20.2 there is new system 'Customize' for +customizing XEmacs options. + + You can access `Customize' from the `Options' menu or invoking one +of customize commands by typing eg. `M-x customize', `M-x +customize-face', `M-x customize-variable' or `M-x customize-apropos'. + + Starting with XEmacs 20.3 there is also new `browser' mode for +Customize. Try it out with `M-x customize-browse' + + +File: xemacs-faq.info, Node: Q3.1.1, Next: Q3.1.2, Prev: Q3.0.9, Up: Customization + +3.1: X Window System & Resources +================================ + +Q3.1.1: Where is a list of X resources? +--------------------------------------- + + Search through the `NEWS' file for `X Resources'. A fairly +comprehensive list is given after it. + + In addition, an `app-defaults' file is supplied, `etc/Emacs.ad' +listing the defaults. The file `etc/sample.Xdefaults' gives a set of +defaults that you might consider. It is essentially the same as +`etc/Emacs.ad' but some entries are slightly altered. Be careful about +installing the contents of this file into your `.Xdefaults' or +`.Xresources' file if you use GNU Emacs under X11 as well. + + +File: xemacs-faq.info, Node: Q3.1.2, Next: Q3.1.3, Prev: Q3.1.1, Up: Customization + +Q3.1.2: How can I detect a color display? +----------------------------------------- + + You can test the return value of the function `(device-class)', as +in: + + (when (eq (device-class) 'color) + (set-face-foreground 'font-lock-comment-face "Grey") + (set-face-foreground 'font-lock-string-face "Red") + .... + ) + + +File: xemacs-faq.info, Node: Q3.1.3, Next: Q3.1.4, Prev: Q3.1.2, Up: Customization + +Q3.1.3: [This question intentionally left blank] +------------------------------------------------ + + +File: xemacs-faq.info, Node: Q3.1.4, Next: Q3.1.5, Prev: Q3.1.3, Up: Customization + +Q3.1.4: [This question intentionally left blank] +------------------------------------------------ + + +File: xemacs-faq.info, Node: Q3.1.5, Next: Q3.1.6, Prev: Q3.1.4, Up: Customization + +Q3.1.5: How can I get the icon to just say `XEmacs'? +---------------------------------------------------- + + I'd like the icon to just say `XEmacs', and not include the name of +the current file in it. + + Add the following line to your `.emacs': + + (setq frame-icon-title-format "XEmacs") + + +File: xemacs-faq.info, Node: Q3.1.6, Next: Q3.1.7, Prev: Q3.1.5, Up: Customization + +Q3.1.6: How can I have the window title area display the full path? +------------------------------------------------------------------- + + I'd like to have the window title area display the full +directory/name of the current buffer file and not just the name. + + Add the following line to your `.emacs': + + (setq frame-title-format "%S: %f") + + A more sophisticated title might be: + + (setq frame-title-format + '("%S: " (buffer-file-name "%f" + (dired-directory dired-directory "%b")))) + + That is, use the file name, or the dired-directory, or the buffer +name. +