Mercurial > hg > xemacs-beta
annotate man/xemacs-faq.texi @ 4505:a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
2008-08-31 Aidan Kehoe <kehoea@parhasard.net>
* xemacs-faq.texi (Q5.0.7): Add a section on how one can use
antialiased fonts under X11; thank you Giacomo Boffi.
(Q1.0.3): Clarify pronunciation using a serious phonetic
alphabet.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Sun, 31 Aug 2008 13:53:36 +0200 |
| parents | ee41a739fba3 |
| children | dd12adb12b8f |
| rev | line source |
|---|---|
| 442 | 1 \input texinfo.tex @c -*- mode: texinfo; coding: iso-2022-8 -*- |
| 428 | 2 @c %**start of header |
| 3 @setfilename ../info/xemacs-faq.info | |
| 4 @settitle Frequently asked questions about XEmacs | |
| 5 @setchapternewpage off | |
| 6 @c %**end of header | |
| 7 @finalout | |
| 8 @titlepage | |
| 9 @title XEmacs FAQ | |
| 3404 | 10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2006/05/16 15:36:16 $ |
| 428 | 11 @sp 1 |
| 2417 | 12 @author Ben Wing <ben@@xemacs.org> |
| 1869 | 13 @author Tony Rossini <rossini@@u.washington.edu> |
| 428 | 14 @author Chuck Thompson <cthomp@@xemacs.org> |
| 15 @author Steve Baur <steve@@xemacs.org> | |
| 16 @author Andreas Kaempf <andreas@@sccon.com> | |
| 17 @author Christian Nyb@o{} <chr@@mediascience.no> | |
| 434 | 18 @author Sandra Wambold <wambold@@xemacs.org> |
| 428 | 19 @page |
| 20 @end titlepage | |
| 21 | |
| 22 @ifinfo | |
| 23 @dircategory XEmacs Editor | |
| 24 @direntry | |
| 440 | 25 * FAQ: (xemacs-faq). XEmacs FAQ. |
| 428 | 26 @end direntry |
| 27 @end ifinfo | |
| 28 | |
| 2417 | 29 @ignore |
| 30 ***************************************** | |
| 31 ***** To update the menus and nodes ***** | |
| 32 ***************************************** | |
| 33 | |
| 34 First, the first argument to @node (the name itself) needs to be correct. | |
| 35 Use a macro if necessary to update the @node names from the | |
| 36 @unnumberedsubsec commands. Also note that the command we're about to | |
| 37 run will not correctly fix up the part of the menu to the right of a ::. | |
| 38 It will leave existing text in place but not change anything. If you | |
| 39 make a lot of changes and want to update this semi-automatically, use | |
| 40 M-x occur to pick out all @unnumberedsubsec lines then do some editing | |
| 41 magic to coerce them into the right format and cut and paste as necessary: | |
| 42 | |
| 43 1. M-x occur @unnumberedsubsec | |
| 44 2. <select a rectangle including all text before the Q#.#.#> | |
| 45 3. C-x r t *<space> | |
| 46 4. go to the top and use the following macro to get the indentation right. | |
| 47 | |
| 48 (setq last-kbd-macro (read-kbd-macro | |
| 49 "C-s : RET : <right> M-x indent- to- column RET 14 RET <home> <down>")) | |
| 50 | |
| 51 5. Cut and paste the menus into the detailmenu at the top and | |
| 52 individual menus at the top of the appropriate chapters. (#### I | |
| 53 wonder, does texinfo-master-menu generate the detailmenu from the | |
| 54 individual menus or vice-versa or neither?) | |
| 55 | |
| 56 Then, | |
| 57 | |
| 2559 | 58 6. C-u C-c C-u m (C-u M-x texinfo-master-menu) will update the menus |
| 2417 | 59 and nodes. However, it appears that even though it tries to |
| 60 preserve the existing menu structure as much as possible, it | |
| 61 doesn't do a perfect job. It messes up in at least two ways: The | |
| 62 indentation in the part of the main menu above the detailmenu will | |
| 63 be screwed up, and the #.0 titles will be removed from both the | |
| 64 detailmenu and the individual chapter menus. In addition, | |
| 65 sometimes random things get screwed up in individual parts of the | |
| 66 menus. Therefore: | |
| 67 | |
| 2559 | 68 1. Use the Lisp line below to get the spacing correct for the Q#.#.# |
| 69 menu entries. | |
| 70 | |
| 71 (set (make-local-variable 'texinfo-column-for-description) 14) | |
| 72 | |
| 73 2. Copy the whole detailmenu beforehand. | |
| 74 3. Run C-u C-c C-u m to fix up the nodes. | |
| 75 4. Run `fix-main-menu' and `fix-omitted-menu-lines'. | |
| 76 5. Check the new detailmenu carefully to see if anything is screwed up | |
| 2417 | 77 compared to the old detailmenu you copied. |
| 2559 | 78 6. If so, paste back the appropriate sections and fix up the corresponding |
| 2417 | 79 part of the chapter-specific menu. |
| 80 | |
| 81 (defun fix-main-menu () | |
| 82 (interactive) | |
| 83 (save-restriction | |
| 84 (let (p q) | |
| 2559 | 85 (goto-char (point-min)) |
| 86 (re-search-forward "^@menu") | |
| 2417 | 87 (setq p (match-beginning 0)) |
| 88 (re-search-forward "^$") | |
| 89 (setq q (match-end 0)) | |
| 90 (narrow-to-region p q) | |
| 91 (goto-char p) | |
| 92 (while (search-forward ":: " nil t) | |
| 93 (indent-to-column 26))))) | |
| 94 | |
| 95 (defun fix-omitted-menu-lines () | |
| 96 (interactive) | |
| 97 (save-excursion | |
| 2559 | 98 (loop for x from 1 to 10 do |
| 2417 | 99 (goto-char (point-min)) |
| 100 (re-search-forward (format "@unnumberedsec \\(%d.0: .*\\)" x)) | |
| 101 (let ((line (match-string 1))) | |
| 2559 | 102 (re-search-backward "^@menu") |
| 2417 | 103 (forward-line 1) |
| 2559 | 104 (unless (looking-at "[0-9]+.0:") |
| 2417 | 105 (insert line) |
| 106 (insert "\n")) | |
| 107 (goto-char (point-min)) | |
| 2559 | 108 (re-search-forward "^@menu") |
| 2417 | 109 (search-forward (format "Q%d.0.1:" x)) |
| 110 (forward-line -1) | |
| 2559 | 111 (unless (looking-at "[0-9]+.0:") |
| 112 (insert "\n") | |
| 113 (insert line)))))) | |
| 2417 | 114 |
| 115 ***************************************** | |
| 116 ***** Other work ***** | |
| 117 ***************************************** | |
| 118 | |
| 119 When you've rearranged and renumbered a bunch of nodes, you can get | |
| 120 the numbers agreeing again. The macro below assumes that the | |
| 121 unnumberedsubsec number is correct, and fixes up the node to agree. | |
| 122 Only the first part of the node is fixed and the other parts may still | |
| 123 be wrong; but they will be fixed as part of | |
| 124 @code{texinfo-master-menu}. | |
| 125 | |
| 126 (setq last-kbd-macro (read-kbd-macro | |
| 127 "<f1> unnumberedsubsec SPC RET C-s : RET <left> C-x C-x <f3> <home> <up> <C-right> <right> C-s , RET <left> C-x C-x <f4> <home> 2*<down>")) | |
| 128 @end ignore | |
| 129 | |
| 130 | |
| 428 | 131 @node Top, Introduction, (dir), (dir) |
| 132 @top XEmacs FAQ | |
| 133 | |
| 134 This is the guide to the XEmacs Frequently Asked Questions list---a | |
| 135 compendium of questions and answers pertaining to one of the finest | |
| 442 | 136 programs ever written. XEmacs is much more than just a Text Editor. |
| 137 | |
| 138 This FAQ is freely redistributable. This FAQ is distributed in the hope | |
| 139 that it will be useful, but WITHOUT ANY WARRANTY; without even the | |
| 140 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. | |
| 428 | 141 |
| 142 If you have a Web browser, the official hypertext version is at | |
| 143 @iftex | |
| 144 @* | |
| 145 @end iftex | |
| 1143 | 146 @uref{http://www.xemacs.org/FAQ/xemacs-faq.html} |
| 428 | 147 |
| 148 @ifset CANONICAL | |
| 149 @html | |
| 150 This document is available in several different formats: | |
| 151 @itemize @bullet | |
| 152 @item | |
| 153 @uref{xemacs-faq.txt, As a single ASCII file}, produced by | |
| 154 @code{makeinfo --no-headers} | |
| 155 @item | |
| 156 @uref{xemacs-faq.dvi, As a .dvi file}, as used with | |
| 157 @uref{http://www.tug.org, TeX.} | |
| 158 @item | |
| 159 As a PostScript file @uref{xemacs-faq-a4.ps, in A4 format}, | |
| 160 as well as in @uref{xemacs-faq-letter.ps, letter format} | |
| 161 @item | |
| 162 In html format, @uref{xemacs-faq_1.html, split by chapter}, or in | |
| 163 @uref{xemacs-faq.html, one monolithic} document. | |
| 164 @item | |
| 165 The canonical version of the FAQ is the texinfo document | |
| 166 @uref{xemacs-faq.texi, man/xemacs-faq.texi}. | |
| 167 @item | |
| 168 If you do not have makeinfo installed, you may @uref{xemacs-faq.info, | |
| 169 download the faq} in info format, and install it in @file{<XEmacs | |
| 170 library directory>/info/}. For example in | |
| 462 | 171 @file{/usr/local/lib/xemacs-21.4/info/}. |
| 428 | 172 |
| 173 @end itemize | |
| 174 | |
| 175 @end html | |
| 176 | |
| 177 @end ifset | |
| 178 | |
| 179 @c end ifset points to CANONICAL | |
| 180 | |
| 181 @menu | |
| 2417 | 182 * Introduction:: Introduction, Policy, Credits. |
| 183 * Installation:: Installation and Troubleshooting. | |
| 2459 | 184 * Editing:: Editing Functions. |
| 185 * Display:: Display Functions. | |
| 2417 | 186 * External Subsystems:: Interfacing with the OS and External Devices. |
| 187 * Internet:: Connecting to the Internet. | |
| 188 * Advanced:: Advanced Customization Using XEmacs Lisp. | |
| 2459 | 189 * Other Packages:: Other External Packages. |
| 2417 | 190 * Current Events:: What the Future Holds. |
| 191 * Legacy Versions:: New information about old XEmacsen. | |
| 428 | 192 |
| 193 @detailmenu | |
| 194 --- The Detailed Node Listing --- | |
| 195 | |
| 2417 | 196 1 Introduction, Policy, Credits |
| 197 | |
| 2537 | 198 1.0: What is XEmacs? |
| 2417 | 199 * Q1.0.1:: What is XEmacs? |
| 200 * Q1.0.2:: What is the current version of XEmacs? | |
| 2537 | 201 * Q1.0.3:: How do you pronounce XEmacs? |
| 202 * Q1.0.4:: What does XEmacs look like? | |
| 203 * Q1.0.5:: Who wrote XEmacs? | |
| 204 * Q1.0.6:: Who wrote the FAQ? | |
| 205 | |
| 206 1.1: Getting XEmacs | |
| 207 * Q1.1.1:: Where can I find XEmacs? | |
| 208 * Q1.1.2:: Are binaries available? | |
| 209 * Q1.1.3:: How do I get the bleeding-edge sources? | |
| 210 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 211 | |
| 212 1.2: Versions for Different Operating Systems | |
| 213 * Q1.2.1:: Do I need X11 to run XEmacs? | |
| 214 * Q1.2.2:: What versions of Unix does XEmacs run on? | |
| 215 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows? | |
| 216 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 217 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 218 * Q1.2.6:: What are the differences between the various MS Windows emacsen? | |
| 219 * Q1.2.7:: How does the port cope with differences in the Windows user interface? | |
| 220 * Q1.2.8:: Is there a port of XEmacs to the Macintosh? | |
| 221 * Q1.2.9:: Is there a port of XEmacs to MS-DOS? | |
| 222 * Q1.2.10:: Is there a port of XEmacs to OS/2? | |
| 223 * Q1.2.11:: Is there a port of XEmacs to NextStep? | |
| 224 * Q1.2.12:: Is there a port of XEmacs to VMS? | |
| 225 | |
| 226 1.3: Getting Started | |
| 227 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? | |
| 228 * Q1.3.2:: Where do I put my @file{init.el} file? | |
| 229 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs? | |
| 230 * Q1.3.4:: Any good XEmacs tutorials around? | |
| 231 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function? | |
| 232 * Q1.3.6:: And how do I bind it to a key? | |
| 233 * Q1.3.7:: What's the difference between a macro and a function? | |
| 234 * Q1.3.8:: What is @code{Custom}? | |
| 235 | |
| 236 1.4: Getting Help | |
| 237 * Q1.4.1:: Where can I get help? | |
| 238 * Q1.4.2:: Which mailing lists are there? | |
| 2559 | 239 * Q1.4.3:: Where are the mailing lists archived? |
| 240 * Q1.4.4:: How can I get two instances of info? | |
| 241 * Q1.4.5:: How do I add new Info directories? | |
| 2537 | 242 |
| 243 1.5: Contributing to XEmacs | |
| 244 * Q1.5.1:: How do I submit changes to the FAQ? | |
| 245 * Q1.5.2:: How do I become a beta tester? | |
| 246 * Q1.5.3:: How do I contribute to XEmacs itself? | |
| 2559 | 247 * Q1.5.4:: How do I get started developing XEmacs? |
| 248 * Q1.5.5:: What's the basic layout of the code? | |
| 2537 | 249 |
| 250 1.6: Politics (XEmacs vs. GNU Emacs) | |
| 251 * Q1.6.1:: What is GNU Emacs? | |
| 252 * Q1.6.2:: How does XEmacs differ from GNU Emacs? | |
| 253 * Q1.6.3:: How much does XEmacs differ? | |
| 254 * Q1.6.4:: Is XEmacs "GNU"? | |
| 255 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 256 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged? | |
| 257 | |
| 258 1.7: External Packages | |
| 2559 | 259 * Q1.7.1:: What is the package system? |
| 260 * Q1.7.2:: Which external packages are there? | |
| 261 * Q1.7.3:: Do I need to have the packages to run XEmacs? | |
| 262 * Q1.7.4:: Is there a way to find which package has particular functionality? | |
| 2537 | 263 |
| 264 1.8: Internationalization | |
| 265 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)? | |
| 266 * Q1.8.2:: How can I help with internationalization? | |
| 267 * Q1.8.3:: How do I type non-ASCII characters? | |
| 268 * Q1.8.4:: Can XEmacs messages come out in a different language? | |
| 269 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs | |
| 270 * Q1.8.6:: How do I portably code for MULE/XEmacs? | |
| 271 * Q1.8.7:: How about Cyrillic modes? | |
| 272 * Q1.8.8:: Does XEmacs support Unicode? | |
| 273 * Q1.8.9:: How does XEmacs display Unicode? | |
| 2417 | 274 |
| 275 2 Installation and Troubleshooting | |
| 276 | |
| 2559 | 277 2.0: Installation (General) |
| 278 * Q2.0.1:: How do I build and install XEmacs? | |
| 279 * Q2.0.2:: Where do I find external libraries? | |
| 280 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files? | |
| 281 * Q2.0.4:: Running XEmacs without installing | |
| 282 * Q2.0.5:: XEmacs is too big | |
| 283 | |
| 284 2.1: Package Installation | |
| 285 * Q2.1.1:: How do I install the packages? | |
| 286 * Q2.1.2:: Can I install the packages individually? | |
| 287 * Q2.1.3:: Can I install the packages automatically? | |
| 288 * Q2.1.4:: Can I upgrade or remove packages? | |
| 289 * Q2.1.5:: Which packages to install? | |
| 290 * Q2.1.6:: Can you describe the package location process in more detail? | |
| 291 * Q2.1.7:: EFS fails with "500 AUTH not understood" | |
| 292 | |
| 293 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) | |
| 294 * Q2.2.1:: Libraries in non-standard locations | |
| 295 * Q2.2.2:: Why can't I strip XEmacs? | |
| 3404 | 296 * Q2.2.3:: X11/bitmaps/gray (or other X11-related file) not found. |
| 2559 | 297 |
| 298 2.3: Windows Installation (Windows, Cygwin, MinGW) | |
| 299 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows? | |
| 300 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs? | |
| 301 * Q2.3.3:: How do I compile the native port? | |
| 302 * Q2.3.4:: What do I need for Cygwin? | |
| 303 * Q2.3.5:: How do I compile under Cygwin? | |
| 304 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 305 * Q2.3.7:: How do I compile with X support? | |
| 306 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 307 | |
| 308 2.4: General Troubleshooting | |
| 309 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running? | |
| 310 * Q2.4.2:: Help! XEmacs just crashed on me! | |
| 311 * Q2.4.3:: XEmacs crashes and I compiled it myself. | |
| 312 * Q2.4.4:: How to debug an XEmacs problem with a debugger | |
| 313 * Q2.4.5:: I get a cryptic error message when trying to do something. | |
| 314 * Q2.4.6:: XEmacs hangs when I try to do something. | |
| 315 * Q2.4.7:: I get an error message when XEmacs is running in batch mode. | |
| 316 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 317 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken? | |
| 318 * Q2.4.10:: How do I debug process-related problems? | |
| 319 * Q2.4.11:: XEmacs is outputting lots of X errors. | |
| 320 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more! | |
| 321 | |
| 322 2.5: Startup-Related Problems | |
| 323 * Q2.5.1:: XEmacs cannot connect to my X Terminal! | |
| 324 * Q2.5.2:: Startup problems related to paths or package locations. | |
| 325 * Q2.5.3:: XEmacs won't start without network. | |
| 326 * Q2.5.4:: Startup warnings about deducing proper fonts? | |
| 327 * Q2.5.5:: Warnings from incorrect key modifiers. | |
| 328 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? | |
| 2417 | 329 |
| 2459 | 330 3 Editing Functions |
| 2417 | 331 |
| 332 3.0: The Keyboard | |
| 2459 | 333 * Q3.0.1:: How can I customize the keyboard? |
| 334 * Q3.0.2:: How can I bind complex functions (or macros) to keys? | |
| 335 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down? | |
| 336 * Q3.0.4:: Globally binding @kbd{Delete}? | |
| 337 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 338 * Q3.0.6:: How can you type in special characters in XEmacs? | |
| 339 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys? | |
| 340 * Q3.0.8:: How do I map the arrow keys? | |
| 341 * Q3.0.9:: HP Alt key as Meta. | |
| 342 * Q3.0.10:: Why does edt emulation not work? | |
| 343 * Q3.0.11:: How can I emulate VI and use it as my default mode? | |
| 2417 | 344 |
| 345 3.1: The Mouse | |
| 346 * Q3.1.1:: How can I turn off Mouse pasting? | |
| 347 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons? | |
| 348 * Q3.1.3:: Clicking the left button does not do anything in buffer list. | |
| 349 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3? | |
| 2459 | 350 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is? |
| 351 | |
| 352 3.2: Buffers, Text Editing | |
| 353 * Q3.2.1:: Can I have the end of the buffer delimited in some way? | |
| 354 * Q3.2.2:: How do I insert today's date into a buffer? | |
| 355 * Q3.2.3:: How do I get a single minibuffer frame? | |
| 356 * Q3.2.4:: How can I enable auto-indent and/or Filladapt? | |
| 357 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 358 | |
| 359 3.3: Text Selections | |
| 360 * Q3.3.1:: How do I select a rectangular region? | |
| 361 * Q3.3.2:: How can I turn off or change highlighted selections? | |
| 362 * Q3.3.3:: How do I cause typing on an active region to remove it? | |
| 363 * Q3.3.4:: Can I turn off the highlight during isearch? | |
| 364 * Q3.3.5:: Why is killing so slow? | |
| 365 * Q3.3.6:: Why does @kbd{M-w} take so long? | |
| 366 | |
| 367 3.4: Editing Source Code | |
| 368 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode? | |
| 369 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly? | |
| 370 | |
| 371 4 Display Functions | |
| 372 | |
| 373 4.0: Textual Fonts and Colors | |
| 374 * Q4.0.1:: How do I specify a font? | |
| 375 * Q4.0.2:: How do I set the text, menu and modeline fonts? | |
| 376 * Q4.0.3:: How can I set color options from @file{init.el}? | |
| 377 * Q4.0.4:: How can I set the colors when highlighting a region? | |
| 378 * Q4.0.5:: How can I limit color map usage? | |
| 379 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them. | |
| 380 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs? | |
| 381 * Q4.0.8:: How do I display non-ASCII characters? | |
| 382 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}. | |
| 383 | |
| 384 4.1: Syntax Highlighting (Font Lock) | |
| 385 * Q4.1.1:: How can I do source code highlighting using font-lock? | |
| 386 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default? | |
| 387 | |
| 388 4.2: The Modeline | |
| 389 * Q4.2.1:: How can I make the modeline go away? | |
| 390 * Q4.2.2:: How do you have XEmacs display the line number in the modeline? | |
| 391 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline? | |
| 392 * Q4.2.4:: How can I change the modeline color based on the mode used? | |
| 393 | |
| 394 4.3: The Cursor | |
| 395 * Q4.3.1:: Is there a way to make the bar cursor thicker? | |
| 396 * Q4.3.2:: Is there a way to get back the block cursor? | |
| 397 * Q4.3.3:: Can I make the cursor blink? | |
| 398 | |
| 399 4.4: The Menubar | |
| 400 * Q4.4.1:: How do I get rid of the menubar? | |
| 401 * Q4.4.2:: How can I customize the menubar? | |
| 402 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 403 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 404 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working? | |
| 405 | |
| 406 4.5: The Toolbar | |
| 407 * Q4.5.1:: How do I get rid of the toolbar? | |
| 408 * Q4.5.2:: How can I customize the toolbar? | |
| 409 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar? | |
| 410 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar | |
| 411 | |
| 412 4.6: Scrollbars and Scrolling | |
| 413 * Q4.6.1:: How can I disable the scrollbar? | |
| 414 * Q4.6.2:: How can I change the scrollbar width? | |
| 415 * Q4.6.3:: How can I use resources to change scrollbar colors? | |
| 416 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this? | |
| 417 * Q4.6.5:: Scrolling one line at a time. | |
| 418 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes? | |
| 419 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off? | |
| 420 | |
| 421 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 422 * Q4.7.1:: How can I disable the gutter tabs? | |
| 423 * Q4.7.2:: How can I disable the progress bar? | |
| 424 * Q4.7.3:: There are bugs in the gutter or widgets. | |
| 425 * Q4.7.4:: How can I customize the gutter or gutter tabs? | |
| 426 | |
| 427 5 Interfacing with the Operating System and External Devices | |
| 428 | |
| 429 5.0: X Window System and Resources | |
| 430 * Q5.0.1:: Where is a list of X resources? | |
| 431 * Q5.0.2:: How can I detect a color display? | |
| 432 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}? | |
| 433 * Q5.0.4:: How can I have the window title area display the full path? | |
| 434 * Q5.0.5:: @samp{xemacs -name junk} doesn't work? | |
| 435 * Q5.0.6:: @samp{-iconic} doesn't work. | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
436 * Q5.0.7:: How can I use antialiased fonts under X11? |
| 2459 | 437 |
| 438 5.1: Microsoft Windows | |
| 439 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? | |
| 440 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 441 | |
| 442 5.2: Printing | |
| 443 * Q5.2.1:: What do I need to change to make printing work? | |
| 444 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer? | |
| 445 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 446 * Q5.2.4:: Can you print under MS Windows? | |
| 447 | |
| 448 5.3: Sound | |
| 449 * Q5.3.1:: How do I turn off the sound? | |
| 450 * Q5.3.2:: How do I get funky sounds instead of a boring beep? | |
| 451 * Q5.3.3:: What are NAS and ESD (EsounD)? | |
| 452 * Q5.3.4:: Sunsite sounds don't play. | |
| 453 | |
| 454 5.4: Running an Interior Shell, Invoking Subprocesses | |
| 455 * Q5.4.1:: What is an interior shell? | |
| 456 * Q5.4.2:: How do I start up a second shell buffer? | |
| 457 * Q5.4.3:: Telnet from shell filters too much | |
| 458 * Q5.4.4:: Strange things are happening in Shell Mode. | |
| 459 * Q5.4.5:: XEmacs complains "No such file or directory, diff" | |
| 2995 | 460 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed" |
| 2459 | 461 |
| 462 5.5: Multiple Device Support | |
| 463 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display? | |
| 464 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 465 * Q5.5.3:: How do I disable gnuserv from opening a new frame? | |
| 466 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 467 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 468 | |
| 469 6 Connecting to the Internet | |
| 470 | |
| 471 6.0: General Mail and News | |
| 472 * Q6.0.1:: What are the various packages for reading mail? | |
| 473 * Q6.0.2:: How can I send mail? | |
| 474 * Q6.0.3:: How do I get my outgoing mail archived? | |
| 475 * Q6.0.4:: How can I read and/or compose MIME messages? | |
| 476 * Q6.0.5:: How do I customize the From line? | |
| 477 * Q6.0.6:: How do I get my MUA to filter mail for me? | |
| 478 * Q6.0.7:: Remote mail reading with an MUA. | |
| 479 * Q6.0.8:: An MUA gets an error incorporating new mail. | |
| 480 * Q6.0.9:: Why isn't @file{movemail} working? | |
| 481 * Q6.0.10:: How do I make my MUA display graphical smilies? | |
| 482 * Q6.0.11:: How can I get those oh-so-neat X-Face lines? | |
| 483 | |
| 484 6.1: Reading Mail with VM | |
| 485 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP? | |
| 486 * Q6.1.2:: How can I get VM to automatically check for new mail? | |
| 487 * Q6.1.3:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"? | |
| 488 * Q6.1.4:: Is there a mailing list or FAQ for VM? | |
| 489 * Q6.1.5:: How do I make VM stay in a single frame? | |
| 490 * Q6.1.6:: Customization of VM not covered in the manual, or here. | |
| 491 | |
| 492 6.2: Reading Netnews and Mail with Gnus | |
| 493 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 494 * Q6.2.2:: How do I make Gnus stay within a single frame? | |
| 495 | |
| 496 6.3: FTP Access | |
| 497 * Q6.3.1:: Can I edit files on other hosts? | |
| 498 * Q6.3.2:: What is EFS? | |
| 499 | |
| 500 6.4: Web Browsing with W3 | |
| 501 * Q6.4.1:: What is W3? | |
| 502 * Q6.4.2:: How do I run W3 from behind a firewall? | |
| 503 * Q6.4.3:: Is it true that W3 supports style sheets and tables? | |
| 504 | |
| 505 7 Advanced Customization Using XEmacs Lisp | |
| 506 | |
| 2537 | 507 7.0: Emacs Lisp and @file{init.el} |
| 508 * Q7.0.1:: What version of Emacs am I running? | |
| 509 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions? | |
| 510 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. | |
| 511 * Q7.0.4:: How can I add directories to the @code{load-path}? | |
| 512 * Q7.0.5:: How to check if a lisp function is defined? | |
| 513 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? | |
| 514 | |
| 515 7.1: Emacs Lisp Programming Techniques | |
| 516 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 517 * Q7.1.2:: Can I generate "fake" keyboard events? | |
| 518 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? | |
| 519 * Q7.1.4:: What is the performance hit of @code{let}? | |
| 520 * Q7.1.5:: What is the recommended use of @code{setq}? | |
| 521 * Q7.1.6:: What is the typical misuse of @code{setq}? | |
| 522 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down? | |
| 523 * Q7.1.8:: I like recursion, does it slow things down? | |
| 524 * Q7.1.9:: How do I put a glyph as annotation in a buffer? | |
| 525 * Q7.1.10:: @code{map-extents} won't traverse all of my extents! | |
| 526 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 527 | |
| 528 7.2: Mathematics | |
| 2559 | 529 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp? |
| 530 * Q7.2.2:: XEmacs segfaults when I use very big numbers! | |
| 531 * Q7.2.3:: Bignums are really slow! | |
| 532 * Q7.2.4:: Equal bignums don't compare as equal! What gives? | |
| 2459 | 533 |
| 534 8 Other External Packages | |
| 535 | |
| 536 8.0: TeX | |
| 537 * Q8.0.1:: Is there something better than LaTeX mode? | |
| 538 * Q8.0.2:: What is AUCTeX? Where do you get it? | |
| 539 * Q8.0.3:: Problems installing AUCTeX. | |
| 540 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline? | |
| 541 | |
| 542 8.1: Other Unbundled Packages | |
| 543 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 544 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets? | |
| 545 * Q8.1.3:: Is there a MatLab mode? | |
| 546 | |
| 547 8.2: Environments Built Around XEmacs | |
| 548 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop? | |
| 549 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21? | |
| 550 * Q8.2.3:: What is/was Energize? | |
| 551 * Q8.2.4:: What is Infodock? | |
| 552 | |
| 553 9 What the Future Holds | |
| 554 | |
| 555 9.0: Changes | |
| 556 * Q9.0.1:: What new features will be in XEmacs soon? | |
| 557 * Q9.0.2:: What's new in XEmacs 21.4? | |
| 558 * Q9.0.3:: What's new in XEmacs 21.1? | |
| 559 * Q9.0.4:: What's new in XEmacs 20.4? | |
| 560 * Q9.0.5:: What's new in XEmacs 20.3? | |
| 561 * Q9.0.6:: What's new in XEmacs 20.2? | |
| 562 | |
| 563 10 New information about old XEmacsen | |
| 564 | |
| 565 10.0: XEmacs 21.1 | |
| 566 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. | |
| 2559 | 567 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1. |
| 568 | |
| 428 | 569 @end detailmenu |
| 570 @end menu | |
| 571 | |
| 572 @node Introduction, Installation, Top, Top | |
| 573 @unnumbered 1 Introduction, Policy, Credits | |
| 574 | |
| 575 Learning XEmacs is a lifelong activity. Even people who have used Emacs | |
| 576 for years keep discovering new features. Therefore this document cannot | |
| 577 be complete. Instead it is aimed at the person who is either | |
| 578 considering XEmacs for their own use, or has just obtained it and is | |
| 579 wondering what to do next. It is also useful as a reference to | |
| 580 available resources. | |
| 581 | |
| 2417 | 582 The previous maintainer of the FAQ was |
| 583 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started | |
| 584 it, after getting tired of hearing JWZ complain about repeatedly | |
| 585 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then | |
| 586 took over and did a massive update reorganizing the whole thing. At | |
| 587 this point Anthony took back over, but then had to give it up again. | |
| 588 Some of the other contributors to this FAQ are listed later in this | |
| 589 document. | |
| 428 | 590 |
| 591 The previous version was converted to hypertext format, and edited by | |
| 592 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to | |
| 434 | 593 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then |
| 594 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it | |
| 2417 | 595 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}. |
| 596 | |
| 597 The current version of the FAQ has been heavily redone by | |
| 598 @email{ben@@xemacs.org, Ben Wing}. | |
| 428 | 599 |
| 600 If you notice any errors or items which should be added or amended to | |
| 2417 | 601 this FAQ please send email to @email{xemacs-beta@@xemacs.org}. |
| 602 Include @samp{XEmacs FAQ} on the Subject: line. | |
| 428 | 603 |
| 604 @menu | |
| 2537 | 605 1.0: What is XEmacs? |
| 2417 | 606 * Q1.0.1:: What is XEmacs? |
| 607 * Q1.0.2:: What is the current version of XEmacs? | |
| 2537 | 608 * Q1.0.3:: How do you pronounce XEmacs? |
| 609 * Q1.0.4:: What does XEmacs look like? | |
| 610 * Q1.0.5:: Who wrote XEmacs? | |
| 611 * Q1.0.6:: Who wrote the FAQ? | |
| 612 | |
| 613 1.1: Getting XEmacs | |
| 614 * Q1.1.1:: Where can I find XEmacs? | |
| 615 * Q1.1.2:: Are binaries available? | |
| 616 * Q1.1.3:: How do I get the bleeding-edge sources? | |
| 617 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 618 | |
| 619 1.2: Versions for Different Operating Systems | |
| 620 * Q1.2.1:: Do I need X11 to run XEmacs? | |
| 621 * Q1.2.2:: What versions of Unix does XEmacs run on? | |
| 622 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows? | |
| 623 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 624 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 625 * Q1.2.6:: What are the differences between the various MS Windows emacsen? | |
| 626 * Q1.2.7:: How does the port cope with differences in the Windows user interface? | |
| 627 * Q1.2.8:: Is there a port of XEmacs to the Macintosh? | |
| 628 * Q1.2.9:: Is there a port of XEmacs to MS-DOS? | |
| 629 * Q1.2.10:: Is there a port of XEmacs to OS/2? | |
| 630 * Q1.2.11:: Is there a port of XEmacs to NextStep? | |
| 631 * Q1.2.12:: Is there a port of XEmacs to VMS? | |
| 632 | |
| 633 1.3: Getting Started | |
| 634 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? | |
| 635 * Q1.3.2:: Where do I put my @file{init.el} file? | |
| 636 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs? | |
| 637 * Q1.3.4:: Any good XEmacs tutorials around? | |
| 638 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function? | |
| 639 * Q1.3.6:: And how do I bind it to a key? | |
| 640 * Q1.3.7:: What's the difference between a macro and a function? | |
| 641 * Q1.3.8:: What is @code{Custom}? | |
| 642 | |
| 643 1.4: Getting Help | |
| 644 * Q1.4.1:: Where can I get help? | |
| 645 * Q1.4.2:: Which mailing lists are there? | |
| 2559 | 646 * Q1.4.3:: Where are the mailing lists archived? |
| 647 * Q1.4.4:: How can I get two instances of info? | |
| 648 * Q1.4.5:: How do I add new Info directories? | |
| 2537 | 649 |
| 650 1.5: Contributing to XEmacs | |
| 651 * Q1.5.1:: How do I submit changes to the FAQ? | |
| 652 * Q1.5.2:: How do I become a beta tester? | |
| 653 * Q1.5.3:: How do I contribute to XEmacs itself? | |
| 2559 | 654 * Q1.5.4:: How do I get started developing XEmacs? |
| 655 * Q1.5.5:: What's the basic layout of the code? | |
| 2537 | 656 |
| 657 1.6: Politics (XEmacs vs. GNU Emacs) | |
| 658 * Q1.6.1:: What is GNU Emacs? | |
| 659 * Q1.6.2:: How does XEmacs differ from GNU Emacs? | |
| 660 * Q1.6.3:: How much does XEmacs differ? | |
| 661 * Q1.6.4:: Is XEmacs "GNU"? | |
| 662 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 663 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged? | |
| 664 | |
| 665 1.7: External Packages | |
| 2559 | 666 * Q1.7.1:: What is the package system? |
| 667 * Q1.7.2:: Which external packages are there? | |
| 668 * Q1.7.3:: Do I need to have the packages to run XEmacs? | |
| 669 * Q1.7.4:: Is there a way to find which package has particular functionality? | |
| 2537 | 670 |
| 671 1.8: Internationalization | |
| 672 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)? | |
| 673 * Q1.8.2:: How can I help with internationalization? | |
| 674 * Q1.8.3:: How do I type non-ASCII characters? | |
| 675 * Q1.8.4:: Can XEmacs messages come out in a different language? | |
| 676 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs | |
| 677 * Q1.8.6:: How do I portably code for MULE/XEmacs? | |
| 678 * Q1.8.7:: How about Cyrillic modes? | |
| 679 * Q1.8.8:: Does XEmacs support Unicode? | |
| 680 * Q1.8.9:: How does XEmacs display Unicode? | |
| 428 | 681 @end menu |
| 682 | |
| 2537 | 683 @unnumberedsec 1.0: What is XEmacs? |
| 2417 | 684 |
| 428 | 685 @node Q1.0.1, Q1.0.2, Introduction, Introduction |
| 686 @unnumberedsubsec Q1.0.1: What is XEmacs? | |
| 687 | |
| 479 | 688 XEmacs is a powerful, highly customizable open source text editor and |
| 2417 | 689 application development system, with full GUI support. It is |
| 690 protected under the GNU Public License and related to other versions | |
| 691 of Emacs, in particular GNU Emacs. Its emphasis is on modern | |
| 692 graphical user interface support and an open software development | |
| 693 model, similar to Linux. XEmacs has an active development community | |
| 694 numbering in the hundreds (and thousands of active beta testers on top | |
| 695 of this), and runs on all versions of MS Windows, on Mac OS X, on | |
| 696 Linux, and on nearly every other version of Unix in existence. | |
| 697 Support for XEmacs has been supplied by Sun Microsystems, University | |
| 698 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl | |
| 699 Corporation, BeOpen, and others, as well as the unpaid time of a great | |
| 700 number of individual developers. | |
| 428 | 701 |
| 702 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction | |
| 703 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs? | |
| 704 | |
| 2417 | 705 XEmacs versions 21.4.* are releases made from the current stable |
| 706 sources. XEmacs versions 21.5.* (which will be released as 22.0) are | |
| 707 releases made from the development sources. Check at | |
| 708 @uref{http://www.xemacs.org} for the current minor version. XEmacs | |
| 709 versions 21.1.* were the previous stable releases, now retired. | |
| 710 | |
| 711 XEmacs 20.4, released in February 1998, was the last release of v20. | |
| 712 | |
| 713 XEmacs 19.16, released in November, 1997. was the last release of v19, | |
| 714 and was also the last version without international language support. | |
| 428 | 715 |
| 716 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction | |
| 2537 | 717 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs? |
| 718 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
719 The most common pronounciation is @samp{Eks eemax}, @samp{Eks'im&ks} in |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
720 Kirshenbaum IPA. (See |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
721 @uref{http://www.kirshenbaum.net/IPA/ascii-ipa.pdf} if you know the IPA |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
722 already and want to know how to map from Kirshenbaum to it.) |
| 428 | 723 |
| 724 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction | |
| 2537 | 725 @unnumberedsubsec Q1.0.4: What does XEmacs look like? |
| 726 | |
| 727 Screen snapshots are available at | |
| 728 @uref{http://www.xemacs.org/About/Screenshots/index.html} | |
| 729 as part of the XEmacs website. | |
| 730 | |
| 731 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction | |
| 732 @unnumberedsubsec Q1.0.5: Who wrote XEmacs? | |
| 733 | |
| 734 XEmacs is the result of the time and effort of many people, and the | |
| 735 active developers have changed over time. There are two major | |
| 736 components of the XEmacs effort -- writing the code itself and providing | |
| 737 all the support work (testing the code, releasing beta and final | |
| 738 versions, handling patches, reading bug reports, maintaining the web | |
| 739 site, managing the mailing lists, etc. etc.). Neither component would | |
| 740 work without the other. | |
| 741 | |
| 742 @subheading CODING | |
| 743 | |
| 744 The primary code contributor over the years has been Ben Wing (active | |
| 745 since late 1992). Between 1991 and 1995, large amounts of coding was | |
| 746 contributed by Jamie Zawinski and Chuck Thompson. Many other people | |
| 747 have authored major subsystems or otherwise contributed large amounts of | |
| 748 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris, | |
| 749 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard | |
| 750 Mlynarik, Stig, William Perry and plenty of others. | |
| 751 | |
| 752 Primary XEmacs-specific subsystems and their authors: | |
| 753 | |
| 754 @table @asis | |
| 755 @item Objects | |
| 756 @itemize @minus | |
| 757 @item | |
| 758 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994 | |
| 759 @item | |
| 760 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz | |
| 761 @item | |
| 762 Portable dumper, object descriptions: Olivier Galibert | |
| 763 @item | |
| 764 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students | |
| 765 @item | |
| 766 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing | |
| 767 @item | |
| 768 Profiling: Ben Wing | |
| 769 @item | |
| 770 Some byte-compilation and hash-table improvements: Martin Buchholz | |
| 771 @item | |
| 772 Bignum: Jerry James | |
| 773 @end itemize | |
| 774 | |
| 775 @item Internationalization/Mule | |
| 776 @itemize @minus | |
| 777 @item | |
| 778 mostly Ben Wing; many ideas for future work, Stephen Turnbull | |
| 779 @end itemize | |
| 780 | |
| 781 @item I/O | |
| 782 @itemize @minus | |
| 783 @item | |
| 784 Basic event/event-stream implementation: Jamie Zawinski | |
| 785 @item | |
| 786 Most event work since 1994: Ben Wing | |
| 787 @item | |
| 788 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing | |
| 789 @item | |
| 790 Process method abstraction, Windows process work: Kirill Katsnelson | |
| 791 @item | |
| 792 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing | |
| 793 @item | |
| 794 Lstreams: Ben Wing | |
| 795 @end itemize | |
| 796 | |
| 797 @item Display | |
| 798 @itemize @minus | |
| 799 @item | |
| 800 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people | |
| 801 @item | |
| 802 Glyphs: mostly Ben Wing | |
| 803 @item | |
| 804 Specifiers: Ben Wing | |
| 805 @item | |
| 806 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing | |
| 807 @item | |
| 808 Widgets: Andy Piper | |
| 809 @item | |
| 810 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c}) | |
| 811 @item | |
| 812 Menus: Jamie Zawinski, someone at Lucid (Lucid menus) | |
| 813 @item | |
| 814 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar) | |
| 815 @item | |
| 816 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson | |
| 817 @item | |
| 818 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing | |
| 819 @item | |
| 820 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing | |
| 821 @item | |
| 822 Toolbars: implementation, chuck, much interface work, Ben Wing | |
| 823 @item | |
| 824 Gutters, tabs: andy piper | |
| 825 @end itemize | |
| 826 | |
| 827 @item Device subsystems | |
| 828 @itemize @minus | |
| 829 @item | |
| 4311 | 830 X Windows: Jamie Zawinski, Ben Wing, others |
| 2537 | 831 @item |
| 832 GTK: William Perry, Malcolm Purvis | |
| 833 @item | |
| 834 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing | |
| 835 @item | |
| 836 TTY: Chuck Thompson, Ben Wing | |
| 837 @item | |
| 838 Cygwin: Andy Piper | |
| 839 @end itemize | |
| 840 | |
| 841 @item Misc | |
| 842 @itemize @minus | |
| 843 @item | |
| 844 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz | |
| 845 @item | |
| 846 Most initialization-related code: Ben Wing | |
| 847 @item | |
| 848 Internals manual, much of Lisp manual: Ben Wing | |
| 849 @item | |
| 850 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing | |
| 851 @end itemize | |
| 852 @end table | |
| 853 | |
| 854 @subheading SUPPORT | |
| 855 | |
| 856 Currently, support duties are handled by many different people. | |
| 857 | |
| 858 Release managers have been | |
| 859 | |
| 860 @itemize @minus | |
| 861 @item | |
| 862 Stephen Turnbull (April 2001 - January 2003, March 2004 - present, 21.2.47 - 21.4.12, 21.5.2 - 21.5.7, 21.5.17 - present) | |
| 863 @item | |
| 864 Vin Shelton (May 2003 - present, 21.4.13 - present) | |
| 865 @item | |
| 866 Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16) | |
| 867 @item | |
| 868 Martin Buchholz (December 1998, November 1999 - May 2001, 21.2.7 - 21.2.8, 21.2.21 - 21.2.46, 21.5.0 - 21.5.1) | |
| 869 @item | |
| 870 Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20) | |
| 871 @item | |
| 872 Andy Piper (December 1998, 21.2.6) | |
| 873 @item | |
| 874 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14) | |
| 875 @item | |
| 876 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10) | |
| 877 @end itemize | |
| 878 | |
| 879 The recent overlapping dates are intentional, since two or three trees | |
| 880 are maintained simultaneously at any point. | |
| 881 | |
| 882 Other major support work: | |
| 883 | |
| 884 @itemize @minus | |
| 885 @item | |
| 886 Adrian Aichner wrote and maintains the web site. | |
| 887 @item | |
| 888 Stephen Turnbull has produced many of the beta and semi-stable releases | |
| 889 and has attempted to be the "face" of XEmacs on the newsgroups and | |
| 890 mailing lists. | |
| 891 @item | |
| 892 Steve Youngs currently produces the beta releases (???). | |
| 893 @item | |
| 4311 | 894 Steve Youngs, Ville Skyttä, and now Norbert Koch have taken turns |
| 2537 | 895 maintaining the packages. |
| 896 @item | |
| 897 Vin Shelton maintains the stable releases. | |
| 898 @item | |
| 899 Testing - #### Norbert, Adrian, ??? | |
| 900 @end itemize | |
| 901 | |
| 902 Portraits and email of some of the major developers: | |
| 903 | |
| 904 @itemize @bullet | |
| 905 @item @email{andy@@xemacs.org, Andy Piper} | |
| 906 @html | |
| 907 <br><img src="piper.png" alt="Portrait of Andy Piper"><br> | |
| 908 @end html | |
| 909 | |
| 910 @item @email{ben@@xemacs.org, Ben Wing} | |
| 911 @html | |
| 912 <br><img src="ben.png" alt="Portrait of Ben Wing"><br> | |
| 913 @end html | |
| 914 | |
| 915 @item @email{cthomp@@xemacs.org, Chuck Thompson} | |
| 916 @html | |
| 917 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br> | |
| 918 @end html | |
| 919 | |
| 920 @item @email{hniksic@@xemacs.org, Hrvoje Niksic} | |
| 921 | |
| 922 @html | |
| 923 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br> | |
| 924 @end html | |
| 925 | |
| 926 @item @email{jwz@@jwz.org, Jamie Zawinski} | |
| 927 @html | |
| 928 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br> | |
| 929 @end html | |
| 930 | |
| 931 @item @email{martin@@xemacs.org, Martin Buchholz} | |
| 932 @html | |
| 933 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br> | |
| 934 @end html | |
| 935 | |
| 936 @item @email{mly@@adoc.xerox.com, Richard Mlynarik} | |
| 937 @html | |
| 938 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br> | |
| 939 @end html | |
| 940 | |
| 941 @item @email{stephen@@xemacs.org, Stephen Turnbull} | |
| 942 | |
| 943 @item @email{steve@@xemacs.org, Steve Baur} | |
| 944 @html | |
| 945 <br><img src="slb.png" alt="Portrait of Steve Baur"><br> | |
| 946 @end html | |
| 947 @end itemize | |
| 948 | |
| 949 Many other people have contributed to XEmacs; this is partially | |
| 950 enumerated in the @samp{About XEmacs} option in the Help menu. | |
| 951 | |
| 952 @node Q1.0.6, Q1.1.1, Q1.0.5, Introduction | |
| 953 @unnumberedsubsec Q1.0.6: Who wrote the FAQ? | |
| 954 | |
| 955 The current version of this FAQ was created by @email{ben@@xemacs.org, | |
| 956 Ben Wing}. | |
| 957 | |
| 958 Previous contributors to the FAQ include | |
| 959 | |
| 960 @itemize @bullet | |
| 961 @item @email{steve@@xemacs.org, SL Baur} | |
| 962 | |
| 963 @item @email{hniksic@@xemacs.org, Hrvoje Niksic} | |
| 964 | |
| 965 @item @email{binge@@aloft.att.com, Curtis.N.Bingham} | |
| 966 | |
| 967 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} | |
| 968 | |
| 969 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley} | |
| 970 | |
| 971 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot} | |
| 972 | |
| 973 @item @email{daku@@nortel.ca, Mark Daku} | |
| 974 | |
| 975 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque} | |
| 976 | |
| 977 @item @email{eeide@@cs.utah.edu, Eric Eide} | |
| 978 | |
| 979 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet} | |
| 980 | |
| 981 @item @email{cflatter@@nrao.edu, Chris Flatters} | |
| 982 | |
| 983 @item @email{ginsparg@@adra.com, Evelyn Ginsparg} | |
| 984 | |
| 985 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall} | |
| 986 | |
| 987 @item @email{dkindred@@cmu.edu, Darrell Kindred} | |
| 988 | |
| 989 @item @email{dmoore@@ucsd.edu, David Moore} | |
| 990 | |
| 991 @item @email{arup+@@cmu.edu, Arup Mukherjee} | |
| 992 | |
| 993 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen} | |
| 994 | |
| 995 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell} | |
| 996 | |
| 997 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy} | |
| 998 | |
| 999 @item @email{stig@@hackvan.com, Stig} | |
| 1000 | |
| 1001 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari} | |
| 1002 @end itemize | |
| 1003 | |
| 1004 @unnumberedsec 1.1: Getting XEmacs | |
| 1005 | |
| 1006 @node Q1.1.1, Q1.1.2, Q1.0.6, Introduction | |
| 1007 @unnumberedsubsec Q1.1.1: Where can I find XEmacs? | |
| 1008 | |
| 1009 To download XEmacs, visit the XEmacs WWW page at | |
| 1010 @uref{http://www.xemacs.org/Download/}. The most up-to-date list of | |
| 1011 distribution sites can always be found there. Try to pick a site that | |
| 1012 is networkologically close to you. If you know of other mirrors of | |
| 1013 the XEmacs archives, please send e-mail to | |
| 1014 @uref{mailto:webmaster@@xemacs.org} and we will list them here as well. | |
| 1015 | |
| 1016 The canonical distribution point is ftp.xemacs.org, available either | |
| 1017 through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP | |
| 1018 (@uref{ftp://ftp.xemacs.org/pub/xemacs/}). | |
| 1019 | |
| 1020 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction | |
| 1021 @unnumberedsubsec Q1.1.2: Are binaries available? | |
| 2417 | 1022 |
| 1023 MS Windows binaries are available at | |
| 1024 @uref{http://www.xemacs.org/Download/win32/} for the native versions | |
| 1025 of 21.4 and 21.1. Cygwin binaries are now available as part of the | |
| 1026 standard Cygwin installation process. XEmacs also comes pre-built as | |
| 1027 part of many Linux distributions, such as Red Hat and SuSE. | |
| 1028 | |
| 1029 Otherwise, you will need to build XEmacs yourself or get your system | |
| 1030 administrator to do it. Generally, this is not a difficult process | |
| 1031 under Unix and Mac OS X, as XEmacs has been tested under all of the | |
| 1032 common Unix versions and under Mac OS X and comes with an extensive | |
| 1033 configure script that is able to automatically detect most aspects of | |
| 1034 the configuration of your particular system. | |
| 1035 | |
| 2537 | 1036 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction |
| 1037 @unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources? | |
| 1038 | |
| 1039 If you are interested in developing XEmacs, or getting the absolutely most | |
| 1040 recent, up-to-the-moment, bleeding-edge source code, you can directly | |
| 1041 access the master CVS source tree (read-only, of course, until you ask for | |
| 1042 and are granted permission to directly modify portions of the source tree) | |
| 1043 at cvs.xemacs.org. Directions on how to access the source tree are located | |
| 1044 at @uref{http://www.xemacs.org/Develop/cvsaccess.html}. | |
| 1045 | |
| 1046 Nightly CVS snapshots are available at | |
| 1047 @uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}. | |
| 1048 | |
| 1049 @node Q1.1.4, Q1.2.1, Q1.1.3, Introduction | |
| 1050 @unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 1051 | |
| 1052 Pre-printed manuals are not available. If you are familiar with | |
| 1053 TeX, you can generate your own manual from the XEmacs sources. | |
| 1054 | |
| 1055 HTML and Postscript versions of XEmacs manuals are available from the | |
| 1056 XEmacs web site at | |
| 1057 @uref{http://www.xemacs.org/Documentation/index.html}. | |
| 1058 | |
| 1059 @unnumberedsec 1.2: Versions for Different Operating Systems | |
| 1060 | |
| 1061 @node Q1.2.1, Q1.2.2, Q1.1.4, Introduction | |
| 1062 @unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs? | |
| 1063 | |
| 1064 No. The name @dfn{XEmacs} is unfortunate in the sense that it is | |
| 1065 @strong{not} an X Window System-only version of Emacs. XEmacs has | |
| 1066 full color support on a color-capable character terminal. | |
| 1067 | |
| 1068 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction | |
| 1069 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on? | |
| 1070 | |
| 2559 | 1071 XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD, |
| 1072 OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably | |
| 1073 others. It should work on all versions of Unix created in the last 10 | |
| 1074 years or so, perhaps with a bit of work on more obscure platforms to | |
| 1075 correct bit-rot. It uses a sophisticated configuration system to | |
| 1076 auto-detect zillions of features that are implemented differently in | |
| 1077 different versions of Unix, so it will probably work on your vendor's | |
| 1078 version, possibly with a bit of tweaking, even if we've never heard of | |
| 1079 it. | |
| 1080 | |
| 2537 | 1081 For problems with particular machines and versions of Unix, see the |
| 1082 @file{PROBLEMS} file. | |
| 1083 | |
| 1084 Much effort has gone into making XEmacs work on as many different | |
| 1085 machines, configurations, and compilers as possible. | |
| 1086 | |
| 1087 Much effort has gone into making XEmacs 64-bit clean. | |
| 1088 | |
| 1089 Much effort has gone into removing system-specific code, and replacing | |
| 1090 such code with autodetection at configure time. | |
| 1091 | |
| 1092 The XEmacs core should build "out of the box" on most Unix-like systems. | |
| 1093 | |
| 1094 XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix | |
| 1095 configurations as of 2001-02-10: | |
| 1096 | |
| 1097 @example | |
| 1098 alphaev56-dec-osf4.0e (both Compaq C and gcc) | |
| 1099 i386-unknown-freebsd4.2 | |
| 1100 i386-unknown-netbsdelf1.5 | |
| 1101 i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc) | |
| 1102 i686-pc-linux-gnu | |
| 1103 hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc) | |
| 1104 mips-sgi-irix6.5 (both MIPSpro cc and gcc) | |
| 1105 rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc) | |
| 1106 sparc-sun-solaris2.6 (both Sun's Forte C and gcc) | |
| 1107 sparc-sun-solaris2.7 (both Sun's Forte C and gcc) | |
| 1108 sparc-sun-sunos4.1.4 (gcc) | |
| 1109 @end example | |
| 1110 | |
| 3018 | 1111 Some systems have a dual mode 32-bit/64-bit compiler. On most of these, |
| 1112 XEmacs requires the @samp{--pdump} (in XEmacs 21.5, | |
| 1113 @samp{--enable-pdump}) configure option to build correctly with the | |
| 1114 64-bit version of the compiler. | |
| 2537 | 1115 |
| 1116 @example | |
| 1117 mips-sgi-irix6.5, CC="gcc -mabi=64" | |
| 1118 mips-sgi-irix6.5, CC="cc -64" | |
| 1119 rs6000-ibm-aix4.3.0.0, CC="cc -q64" | |
| 1120 @end example | |
| 1121 | |
| 1122 On most of these systems, XEmacs also builds with a C++ compiler, | |
| 1123 but not "out of the box". This feature is only for use by the | |
| 1124 maintainers. | |
| 1125 | |
| 1126 XEmacs 21.2 is known @emph{not} to work on any machines with m680x0 | |
| 1127 processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there. | |
| 1128 | |
| 1129 VMS has never been supported by XEmacs. In fact, all the old VMS code | |
| 1130 inherited from Emacs has been removed. Sorry, all you VMS fans out there. | |
| 1131 | |
| 1132 @node Q1.2.3, Q1.2.4, Q1.2.2, Introduction | |
| 1133 @unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows? | |
| 1134 | |
| 1135 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows | |
| 1136 and is fully-featured and actively developed. A group of dedicated | |
| 1137 developers actively maintains and improves the Windows-specific | |
| 1138 portions of the code. Some of the core developers, in fact, use | |
| 1139 Windows as their only development environment, and some features, such | |
| 1140 as printing, actually work better on Windows than native Unix and Mac | |
| 1141 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated | |
| 1142 to that effort (please use the -request address to | |
| 1143 subscribe). (Despite its name, XEmacs actually works on all versions | |
| 1144 of Windows.) | |
| 1145 | |
| 1146 The list name is misleading, as XEmacs supports and has been compiled on | |
| 1147 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows | |
| 1148 XP, and all newer versions of Windows. The MS Windows-specific code is | |
| 1149 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on | |
| 1150 MS-DOS. | |
| 1151 | |
| 1152 XEmacs also supports the Cygwin and MinGW development and runtime | |
| 1153 environments, where it also uses native Windows code for graphical | |
| 1154 features. In addition, under Cygwin it is possible to compile XEmacs | |
| 1155 to use an X server (and XFree86 is available as part of the standard | |
| 1156 Cygwin installation). | |
| 1157 | |
| 1158 @node Q1.2.4, Q1.2.5, Q1.2.3, Introduction | |
| 1159 @unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 1160 | |
| 1161 Yes, you can, but no you do not need to. In fact, we recommend that you | |
| 1162 use a native-GUI version unless you have a specific need for an X | |
| 1163 version. | |
| 1164 | |
| 1165 @node Q1.2.5, Q1.2.6, Q1.2.4, Introduction | |
| 1166 @unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 1167 | |
| 1168 To answer the second part of the question: No, you, you don't need | |
| 1169 Cygwin or MinGW to build or to run XEmacs. But if you have them and | |
| 1170 want to use them, XEmacs supports these environments. | |
| 1171 | |
| 1172 (One important reason to support Cygwin is that it lets the MS Windows | |
| 1173 developers test out their code in a Unix environment without actually | |
| 1174 having to have a Unix machine around. For this reason alone, Cygwin | |
| 1175 support is likely to remain supported for a long time in XEmacs. Same | |
| 1176 goes for the X support under Cygwin, for the same reasons. MinGW | |
| 1177 support, on the other hand, depends on volunteers to keep it up to date; | |
| 1178 but this is generally not hard.) | |
| 1179 | |
| 1180 Cygwin is a set of tools providing Unix-like API on top of Win32. | |
| 1181 It makes it easy to port large Unix programs without significant | |
| 1182 changes to their source code. It is a development environment as well | |
| 1183 as a runtime environment. | |
| 1184 | |
| 1185 When built with Cygwin, XEmacs supports all display types -- TTY, X & | |
| 1186 Win32 GUI, and can be built with support for all three simultaneously. | |
| 1187 If you build with Win32 GUI support then the Cygwin version uses the | |
| 1188 majority of the Windows-specific code, which is mostly related to | |
| 1189 display. If you want to build with X support you need X libraries (and | |
| 2559 | 1190 an X server to display XEmacs on); see @ref{Q2.3.7}. TTY and Win32 GUI |
| 2537 | 1191 require no additional libraries beyond what comes standard with Cygwin. |
| 1192 | |
| 1193 The advantages of the Cygwin version are that it integrates well with | |
| 1194 the Cygwin environment for existing Cygwin users; uses configure so | |
| 1195 building with different features is very easy; and actively supports X & | |
| 1196 TTY. Furthermore, the entire Cygwin environment and compiler are free, | |
| 1197 whereas Visual C++ costs money. | |
| 1198 | |
| 1199 The disadvantage is that it requires the whole Cygwin environment, | |
| 1200 whereas the native port requires only a suitable MS Windows compiler. | |
| 1201 Also, it follows the Unix filesystem and process model very closely | |
| 1202 (some will undoubtedly view this as an advantage). | |
| 1203 | |
| 1204 See @uref{http://www.cygwin.com/} for more information on | |
| 1205 Cygwin. | |
| 1206 | |
| 1207 MinGW is a collection of header files and import libraries that allow | |
| 1208 one to use GCC under the Cygwin environment to compile and produce | |
| 1209 exactly the same native Win32 programs that you can using Visual C++. | |
| 1210 Programs compiled with MinGW make use of the standard Microsoft runtime | |
| 1211 library @file{MSVCRT.DLL}, present on all Windows systems, and look, | |
| 1212 feel, and act like a standard Visual-C-produced application. (The only | |
| 1213 difference is the compiler.) This means that, unlike a | |
| 1214 standardly-compiled Cygwin application, no extra runtime support | |
| 1215 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the | |
| 1216 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y | |
| 1217 environment, for those die-hard Unix hackers out there), is the main | |
| 1218 advantage of MinGW. It is also potentially faster than Cygwin because | |
| 1219 it has less overhead when calling Windows, but you lose the POSIX | |
| 1220 emulation layer, which makes Unix programs harder to port. (But this is | |
| 1221 irrelevant for XEmacs since it's already ported to Win32.) | |
| 1222 | |
| 1223 See @uref{http://www.mingw.org/} for more information on MinGW. | |
| 1224 | |
| 1225 @node Q1.2.6, Q1.2.7, Q1.2.5, Introduction | |
| 1226 @unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen? | |
| 1227 | |
| 1228 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing. | |
| 1229 Could you briefly explain the differences between them? | |
| 1230 | |
| 1231 Here is a recount of various Emacs versions running on MS Windows: | |
| 1232 | |
| 1233 @itemize @bullet | |
| 1234 | |
| 1235 @item | |
| 1236 XEmacs | |
| 1237 | |
| 1238 @itemize @minus | |
| 1239 | |
| 1240 @item | |
| 1241 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned | |
| 1242 in such a way to allow clean support of multiple window systems. At | |
| 1243 this time the TTY support was added, making X and TTY the first two | |
| 1244 "window systems" supported by XEmacs. The 19.12 design is the basis for | |
| 1245 the current native MS Windows code. | |
| 1246 | |
| 1247 @item | |
| 1248 Some time during 1997, David Hobley (soon joined by Marc Paquette) | |
| 1249 imported some of the NT-specific portions of GNU Emacs, making XEmacs | |
| 1250 with X support compile under Windows NT, and creating the "X" port. | |
| 1251 | |
| 1252 @item | |
| 1253 Several months later, Jonathan Harris sent out initial patches to use | |
| 1254 the Win32 API, thus creating the native port. Since then, various | |
| 1255 people have contributed, including Kirill M. Katsnelson (contributed | |
| 1256 support for menubars, subprocesses and network, as well as loads of | |
| 1257 other code), Andy Piper (ported XEmacs to Cygwin environment, | |
| 1258 contributed Windows unexec, Windows-specific glyphs and toolbars code, | |
| 1259 and more), Ben Wing (loads of improvements; primary MS Windows developer | |
| 1260 since 2000), Jeff Sparkes (contributed scrollbars support) and many | |
| 1261 others. | |
| 1262 @end itemize | |
| 1263 | |
| 1264 @item | |
| 1265 NT Emacs | |
| 1266 | |
| 1267 @itemize @minus | |
| 1268 | |
| 1269 @item | |
| 1270 NT Emacs was an early version of GNU Emacs 19 modified to compile and | |
| 1271 run under MS Windows 95 and NT using the native Win32 API. It was | |
| 1272 written by Geoff Voelker, and has long since been incorporated into | |
| 1273 the mainline GNU Emacs distribution. | |
| 1274 @end itemize | |
| 1275 | |
| 1276 @item | |
| 1277 Win-Emacs | |
| 1278 | |
| 1279 @itemize @minus | |
| 1280 | |
| 1281 @item | |
| 1282 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X | |
| 1283 compatibility libraries. Win-Emacs was written by Ben Wing. The MS | |
| 1284 Windows code never made it back to Lucid Emacs, and its creator (Pearl | |
| 1285 Software) has long since gone out of business. | |
| 1286 @end itemize | |
| 1287 | |
| 1288 @item | |
| 1289 GNU Emacs for DOS | |
| 1290 | |
| 1291 @itemize @minus | |
| 1292 | |
| 1293 @item | |
| 1294 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS | |
| 1295 port of GCC). Such an Emacs is heavily underfeatured, because it does | |
| 1296 not support long file names, lacks proper subprocesses support, and | |
| 1297 is far too big compared with typical DOS editors. | |
| 1298 @end itemize | |
| 1299 | |
| 1300 @item | |
| 1301 GNU Emacs compiled with Win32 | |
| 1302 | |
| 1303 @itemize @minus | |
| 1304 | |
| 1305 @item | |
| 1306 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs | |
| 1307 under MS Windows using the DJGPP compiler and X libraries. The result | |
| 1308 is very similar to GNU Emacs compiled under MS DOS, only it works | |
| 1309 somewhat better because it runs in 32-bit mode, makes use of all the | |
| 1310 system memory, supports long file names, etc. | |
| 1311 @end itemize | |
| 1312 | |
| 1313 @end itemize | |
| 1314 | |
| 1315 @node Q1.2.7, Q1.2.8, Q1.2.6, Introduction | |
| 1316 @unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface? | |
| 1317 | |
| 1318 The XEmacs (and Emacs in general) user interface is pretty different | |
| 1319 from what is expected of a typical MS Windows program. How does the MS | |
| 1320 Windows port cope with it? | |
| 1321 | |
| 1322 As a general rule, we follow native MS Windows conventions as much as | |
| 1323 possible. 21.4 is a fairly complete Windows application, supporting | |
| 1324 native printing, system file dialog boxes, tool tips, etc. In cases | |
| 1325 where there's a clear UI conflict, we currently use normal Unix XEmacs | |
| 1326 behavior by default, but make sure the MS Windows "look and feel" (mark | |
| 1327 via shift-arrow, self-inserting deletes region, Alt selects menu items, | |
| 1328 etc.) is easily configurable (respectively: using the variable | |
| 1329 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact | |
| 1330 the default in these versions], or the @file{pc-select} package; using | |
| 1331 the @file{pending-del} package; and setting the variable | |
| 1332 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above). | |
| 1333 In fact, if you use the sample @file{init.el} file as your init file, | |
| 1334 you will get all these behaviors automatically turned on. | |
| 1335 | |
| 1336 In future versions, some of these features might be turned on by | |
| 1337 default in the MS Windows environment. | |
| 1338 | |
| 1339 @node Q1.2.8, Q1.2.9, Q1.2.7, Introduction | |
| 1340 @unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh? | |
| 1341 | |
| 1342 Yes. | |
| 1343 | |
| 1344 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly | |
| 1345 will not feel very much like a Mac application as it has no Mac-specific | |
| 1346 code in it. | |
| 1347 | |
| 1348 There is also a port of XEmacs 19.14 that works on all recent versions | |
| 1349 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com, | |
| 1350 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY | |
| 1351 mode only (one single Macintosh window, 25 colors), but has a large | |
| 1352 number of Mac-specific additions. It's available at | |
| 1353 @uref{http://homepage.mac.com/pjarvis/xemacs.html}. | |
| 1354 | |
| 1355 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction | |
| 2559 | 1356 @unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS? |
| 1357 | |
| 1358 No. We have never supported running on MS-DOS or Windows 3.1, and in | |
| 1359 fact have long since deleted all MS-DOS-related code. We're not | |
| 1360 particularly interested in patches for these platforms, as they would | |
| 1361 introduce huge amounts of code clutter due to the woefully | |
| 1362 underfeatured nature of these systems. (See GNU Emacs for a port to | |
| 1363 MS-DOS.) | |
| 2537 | 1364 |
| 1365 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction | |
| 2559 | 1366 @unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2? |
| 2537 | 1367 |
| 1368 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point | |
| 1369 working on it. | |
| 1370 | |
| 2559 | 1371 @node Q1.2.11, Q1.2.12, Q1.2.10, Introduction |
| 1372 @unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep? | |
| 2537 | 1373 |
| 1374 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did | |
| 1375 the port of GNU Emacs to NeXTstep and expressed interest in doing the | |
| 1376 XEmacs port, but never went any farther. | |
| 1377 | |
| 2559 | 1378 @node Q1.2.12, Q1.3.1, Q1.2.11, Introduction |
| 1379 @unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS? | |
| 2537 | 1380 |
| 1381 VMS has never been supported by XEmacs. In fact, all the old VMS code | |
| 1382 inherited from GNU Emacs has been removed. Sorry, all you VMS fans | |
| 1383 out there. | |
| 1384 | |
| 1385 @unnumberedsec 1.3: Getting Started | |
| 1386 | |
| 2559 | 1387 @node Q1.3.1, Q1.3.2, Q1.2.12, Introduction |
| 2537 | 1388 @unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one? |
| 1389 | |
| 1390 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to | |
| 1391 your tastes. Starting in 21.4, the preferred location for the init file | |
| 1392 is @file{~/.xemacs/init.el}; in previous versions, it was | |
| 1393 @file{~/.emacs}. 21.4 still accepts the old location, but the first | |
| 1394 time you run it, it will ask to migrate your file to the new location. | |
| 1395 If you answer yes, the file will be moved, and a "compatibility" | |
| 1396 @file{.emacs} file will be placed in the old location so that you can | |
| 1397 still run older versions of XEmacs, and versions of GNU Emacs, which | |
| 1398 expect the old location. The @file{.emacs} file present is just a stub | |
| 1399 that loads the real file in @file{~/.xemacs/init.el}. | |
| 1400 | |
| 1401 No two init files are alike, nor are they expected to be alike, but | |
| 1402 that's the point. The XEmacs distribution contains an excellent starter | |
| 1403 example in the @file{etc/} directory called @file{sample.init.el} | |
| 1404 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this | |
| 1405 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or | |
| 1406 @file{~/.emacs} in older versions, where @samp{~} means your home | |
| 1407 directory, of course. Then edit it to suit. | |
| 1408 | |
| 1409 You may bring the @file{sample.init.el} or @file{sample.emacs} file into | |
| 1410 an XEmacs buffer from the menubar. (The menu entry for it is always | |
| 1411 under the @samp{Help} menu, but its location under that has changed in | |
| 1412 various versions. Recently, look under the @samp{Samples} submenu.) To | |
| 1413 determine the location of the @file{etc/} directory type the command | |
| 1414 @kbd{C-h v data-directory @key{RET}}. | |
| 1415 | |
| 1416 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction | |
| 1417 @unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file? | |
| 1418 | |
| 1419 @file{init.el} is the name of the init file starting with 21.4, and is | |
| 1420 located in the subdirectory @file{.xemacs/} of your home directory. In | |
| 1421 prior versions, the init file is called @file{.emacs} and is located in | |
| 1422 your home directory. | |
| 1423 | |
| 1424 Your home directory under Windows is determined by the @samp{HOME} | |
| 1425 environment variable. If this is not set, it defaults to @samp{C:\}. | |
| 1426 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or | |
| 1427 select @samp{Control Panel->System->Advanced->Environment Variables...} | |
| 1428 under Windows NT/2000. | |
| 1429 | |
| 1430 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction | |
| 1431 @unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs? | |
| 1432 | |
| 1433 Yes. The sample @file{init.el} included in the XEmacs | |
| 1434 distribution will show you how to handle different versions and flavors | |
| 1435 of Emacs. | |
| 1436 | |
| 1437 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction | |
| 1438 @unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around? | |
| 1439 | |
| 1440 There's the XEmacs tutorial available from the Help Menu under | |
| 1441 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether | |
| 1442 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type | |
| 1443 the first letters of your preferred language, then type @key{RET}. | |
| 1444 | |
| 1445 @comment There's an Emacs Lisp tutorial at | |
| 1446 @comment | |
| 1447 @comment @example | |
| 1448 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}. | |
| 1449 @comment @end example | |
| 1450 @comment | |
| 1451 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web | |
| 1452 @comment page at | |
| 1453 @comment @iftex | |
| 1454 @comment @* | |
| 1455 @comment @end iftex | |
| 1456 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}. | |
| 1457 | |
| 1458 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction | |
| 1459 @unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function? | |
| 1460 | |
| 1461 The following function does a little bit of everything useful. It does | |
| 1462 something with the prefix argument, it examines the text around the | |
| 1463 cursor, and it's interactive so it may be bound to a key. It inserts | |
| 1464 copies of the current word the cursor is sitting on at the cursor. If | |
| 1465 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will | |
| 1466 insert 3 copies. | |
| 1467 | |
| 1468 @lisp | |
| 1469 (defun double-word (count) | |
| 1470 "Insert a copy of the current word underneath the cursor" | |
| 1471 (interactive "*p") | |
| 1472 (let (here there string) | |
| 1473 (save-excursion | |
| 1474 (forward-word -1) | |
| 1475 (setq here (point)) | |
| 1476 (forward-word 1) | |
| 1477 (setq there (point)) | |
| 1478 (setq string (buffer-substring here there))) | |
| 1479 (while (>= count 1) | |
| 1480 (insert string) | |
| 1481 (decf count)))) | |
| 1482 @end lisp | |
| 1483 | |
| 1484 The best way to see what is going on here is to let XEmacs tell you. | |
| 1485 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor | |
| 1486 sitting just to the right of the function you want explained. Eg. move | |
| 1487 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and | |
| 1488 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing | |
| 1489 this will tell you that the @code{*} requires a writable buffer, and | |
| 1490 @code{p} converts the prefix argument to a number, and | |
| 1491 @code{interactive} allows you to execute the command with @kbd{M-x}. | |
| 1492 | |
| 1493 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction | |
| 1494 @unnumberedsubsec Q1.3.6: And how do I bind it to a key? | |
| 1495 | |
| 1496 To bind to a key do: | |
| 1497 | |
| 1498 @lisp | |
| 1499 (global-set-key "\C-cd" 'double-word) | |
| 1500 @end lisp | |
| 1501 | |
| 1502 Or interactively, @kbd{M-x global-set-key} and follow the prompts. | |
| 1503 | |
| 1504 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction | |
| 1505 @unnumberedsubsec Q1.3.7: What's the difference between a macro and a function? | |
| 1506 | |
| 1507 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual: | |
| 1508 | |
| 1509 @dfn{Macros} enable you to define new control constructs and other | |
| 1510 language features. A macro is defined much like a function, but instead | |
| 1511 of telling how to compute a value, it tells how to compute another Lisp | |
| 1512 expression which will in turn compute the value. We call this | |
| 1513 expression the @dfn{expansion} of the macro. | |
| 1514 | |
| 1515 Macros can do this because they operate on the unevaluated expressions | |
| 1516 for the arguments, not on the argument values as functions do. They can | |
| 1517 therefore construct an expansion containing these argument expressions | |
| 1518 or parts of them. | |
| 1519 | |
| 1520 Do not confuse the two terms with @dfn{keyboard macros}, which are | |
| 1521 another matter, entirely. A keyboard macro is a key bound to several | |
| 1522 other keys. Refer to manual for details. | |
| 1523 | |
| 1524 @node Q1.3.8, Q1.4.1, Q1.3.7, Introduction | |
| 1525 @unnumberedsubsec Q1.3.8: What is @code{Custom}? | |
| 1526 | |
| 1527 @code{Custom} is a system for customizing XEmacs options. | |
| 1528 | |
| 1529 You can access @code{Advanced (Customize)} from the @code{Options} menu | |
| 1530 or invoking one of customize commands by typing eg. | |
| 1531 @kbd{M-x customize}, @kbd{M-x customize-face}, | |
| 1532 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}. | |
| 1533 | |
| 1534 There is also new @samp{browser} mode for Customize. | |
| 1535 Try it out with @kbd{M-x customize-browse} | |
| 1536 | |
| 1537 @unnumberedsec 1.4: Getting Help | |
| 1538 | |
| 1539 @node Q1.4.1, Q1.4.2, Q1.3.8, Introduction | |
| 1540 @unnumberedsubsec Q1.4.1: Where can I get help? | |
| 1541 | |
| 1542 Probably the easiest way, if everything is installed, is to use Info, by | |
| 1543 pressing @kbd{C-h i}, or looking for an Info item on the | |
| 1544 Help Menu. @kbd{M-x apropos} can be used to look for particular commands. | |
| 1545 | |
| 1546 For items not found in the manual, try reading this FAQ | |
| 1547 and reading the Usenet group comp.emacs.xemacs. | |
| 1548 | |
| 1549 If you choose to post to a newsgroup, @strong{please use | |
| 1550 comp.emacs.xemacs}. Please do not post XEmacs related questions to | |
| 1551 gnu.emacs.help. | |
| 1552 | |
| 1553 If you cannot post or read Usenet news, there is a corresponding mailing | |
| 1554 list @email{xemacs-news@@xemacs.org} which is available. It can be | |
| 1555 subscribed to via the Mailman Web interface or by sending mail to to | |
| 1556 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the | |
| 1557 body of the message. See also | |
| 1558 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a | |
| 1559 subscription, you may use the @email{xemacs-news-request@@xemacs.org} | |
| 1560 address or the Web interface. Send a message with a subject of | |
| 1561 @samp{unsubscribe} to be removed. | |
| 1562 | |
| 1563 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction | |
| 1564 @unnumberedsubsec Q1.4.2: Which mailing lists are there? | |
| 1565 | |
| 1566 For complete, up-to-date info on the lists and how to subscribe, see | |
| 1567 @uref{http://www.xemacs.org/Lists/}. | |
| 1568 | |
| 1569 @table @samp | |
| 1570 | |
| 1571 @item comp.emacs.xemacs | |
| 1572 is a Usenet newsgroup | |
| 1573 for XEmacs users to discuss problems and issues that arise | |
| 1574 for them. It's not generally an appropriate place to ask | |
| 1575 about apparent bugs (use @samp{xemacs-beta}), or future plans | |
| 1576 (use @samp{xemacs-design}). | |
| 1577 | |
| 1578 @item xemacs-announce | |
| 1579 is a read-only, low | |
| 1580 volume list for announcements concerning the XEmacs project | |
| 1581 and new releases of the XEmacs software. | |
| 1582 | |
| 1583 @item xemacs-beta | |
| 2559 | 1584 is an open list for bug reports about beta versions of XEmacs. This |
| 1585 includes the bug reports themselves, by both users and developers, as | |
| 1586 well as queries, follow-ups, and discussions further determining their | |
| 1587 nature and status. This is the primary channel for this kind of | |
| 1588 discussion; related code changes will usually not be applied until | |
| 1589 they have been discussed here. When such discussions touch on | |
| 1590 significant changes to the code (in particular, structural changes), | |
| 1591 or on changes to API's or external functionality, they should be moved | |
| 1592 to @samp{xemacs-design}. Requests and proposals for non-bug-related | |
| 1593 changes do not belong on @samp{xemacs-beta}, and should be sent to | |
| 1594 @samp{xemacs-design} instead. | |
| 2537 | 1595 |
| 1596 @item xemacs-beta-ja | |
| 1597 is an open list for bug | |
| 1598 reports and design discussion related to Mule features, | |
| 1599 including Japanese handling, in beta versions of XEmacs. | |
| 1600 Japanese is the preferred language of discussion. For most | |
| 1601 timely presentation to reviewers, please consider sending | |
| 1602 appropriate discussion to @samp{xemacs-mule} or | |
| 1603 @samp{xemacs-design} in English when convenient for | |
| 1604 the participants in discussion. When possible, bug reports | |
| 1605 not related to Mule (including Japanese) should be reported on | |
| 1606 @samp{xemacs-beta} in English. | |
| 1607 | |
| 1608 @item xemacs-buildreports | |
| 1609 is an open list for | |
| 1610 submission of build-reports on beta versions of XEmacs. For | |
| 1611 information on what the build-reports should contain, please | |
| 1612 see the `etc/BETA' file which is included in each beta | |
| 1613 distribution. | |
| 1614 | |
| 1615 @item xemacs-cvs | |
| 1616 is a read-only list for notices | |
| 1617 and information on what has been committed to the XEmacs CVS | |
| 1618 trees, by whom, and for what. | |
| 1619 | |
| 1620 @item xemacs-design | |
| 1621 is an open list for | |
| 1622 discussing the design of XEmacs. This includes discussion | |
| 1623 about planned and ongoing changes to functionality and API | |
| 1624 changes and additions as well as requests for them. This is | |
| 1625 the primary channel for this kind of discussion; related code | |
| 1626 changes will usually not be applied until they have been | |
| 1627 discussed here. This does not include bug reports, which go | |
| 1628 to @samp{xemacs-beta}. | |
| 1629 | |
| 1630 @item xemacs-mule | |
| 1631 is an open mailing list for | |
| 1632 discussion of International extensions to XEmacs including | |
| 1633 Mule, XIM, I18n issues, etc, and is not confined to | |
| 1634 developmental issues. This list is not restricted to | |
| 1635 English, postings in all languages are welcome. | |
| 1636 | |
| 1637 @item xemacs-news | |
| 1638 is an open list for discussion | |
| 1639 and bug reporting for XEmacs. This mailing list is | |
| 1640 bi-directionally gatewayed with the USENET newsgroup | |
| 1641 comp.emacs.xemacs. | |
| 1642 | |
| 1643 @item xemacs-nt | |
| 1644 is a developers-only mailing | |
| 1645 list and is intended for people who wish to work actively on | |
| 1646 the porting of XEmacs to Microsoft Windows NT and Microsoft | |
| 1647 Windows '95. | |
| 1648 | |
| 1649 @item xemacs-patches | |
| 1650 is an open, moderated | |
| 1651 list for submission of patches to the XEmacs distribution | |
| 1652 and its packages. Anyone may subscribe or submit to | |
| 1653 xemacs-patches, but all submissions are reviewed by the list | |
| 1654 moderator before they are distributed to the | |
| 1655 list. Discussion is not appropriate on xemacs-patches. | |
| 1656 | |
| 1657 @item xemacs-users-ja | |
| 1658 is an open list for | |
| 1659 discussion and bug reporting for XEmacs. Japanese is the | |
| 1660 preferred language of discussion. It is not gated to | |
| 1661 comp.emacs.xemacs or the @samp{xemacs} list. For | |
| 1662 fastest response, bugs not specifically related to Japanese | |
| 1663 or Mule features should be reported on | |
| 1664 @samp{xemacs-beta} (in English). | |
| 1665 | |
| 1666 @item xemacs-users-ru | |
| 1667 is an open list for | |
| 1668 discussion and bug reporting for XEmacs. Russian is the | |
| 1669 preferred language of discussion. It is not gated to | |
| 1670 comp.emacs.xemacs or the @samp{xemacs} list. For | |
| 1671 fastest response, bugs not specifically related to Russian | |
| 1672 or Mule features should be reported on | |
| 1673 @samp{xemacs-beta} (in English). | |
| 1674 @end table | |
| 1675 | |
| 1676 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction | |
| 1677 @unnumberedsubsec Q1.4.3: Where are the mailing lists archived? | |
| 1678 | |
| 1679 The archives can be found at @uref{http://list-archive.xemacs.org} | |
| 1680 | |
| 1681 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction | |
| 1682 @unnumberedsubsec Q1.4.4: How can I get two instances of info? | |
| 1683 | |
| 1684 Before 21.4, you can't. The @code{info} package does not provide for | |
| 1685 multiple info buffers. In 21.4, this should be fixed. #### how? | |
| 1686 | |
| 1687 @node Q1.4.5, Q1.5.1, Q1.4.4, Introduction | |
| 1688 @unnumberedsubsec Q1.4.5: How do I add new Info directories? | |
| 1689 | |
| 1690 You use something like: | |
| 1691 | |
| 1692 @lisp | |
| 1693 (setq Info-directory-list (cons | |
| 1694 (expand-file-name "~/info") | |
| 1695 Info-default-directory-list)) | |
| 1696 @end lisp | |
| 1697 | |
| 1698 @email{davidm@@prism.kla.com, David Masterson} writes: | |
| 1699 | |
| 1700 @quotation | |
| 1701 Emacs Info and XEmacs Info do many things differently. If you're trying to | |
| 1702 support a number of versions of Emacs, here are some notes to remember: | |
| 1703 | |
| 1704 @enumerate | |
| 1705 @item | |
| 1706 Emacs Info scans @code{Info-directory-list} from right-to-left while | |
| 1707 XEmacs Info reads it from left-to-right, so append to the @emph{correct} | |
| 1708 end of the list. | |
| 1709 | |
| 1710 @item | |
| 1711 Use @code{Info-default-directory-list} to initialize | |
| 1712 @code{Info-directory-list} @emph{if} it is available at startup, but not | |
| 1713 all Emacsen define it. | |
| 1714 | |
| 1715 @item | |
| 1716 Emacs Info looks for a standard @file{dir} file in each of the | |
| 1717 directories scanned from #1 and magically concatenates them together. | |
| 1718 | |
| 1719 @item | |
| 1720 XEmacs Info looks for a @file{localdir} file (which consists of just the | |
| 1721 menu entries from a @file{dir} file) in each of the directories scanned | |
| 1722 from #1 (except the first), does a simple concatenation of them, and | |
| 1723 magically attaches the resulting list to the end of the menu in the | |
| 1724 @file{dir} file in the first directory. | |
| 1725 @end enumerate | |
| 1726 | |
| 1727 Another alternative is to convert the documentation to HTML with | |
| 1728 texi2html and read it from a web browser like Lynx or W3. | |
| 1729 @end quotation | |
| 1730 | |
| 1731 @unnumberedsec 1.5: Contributing to XEmacs | |
| 1732 | |
| 1733 @node Q1.5.1, Q1.5.2, Q1.4.5, Introduction | |
| 1734 @unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ? | |
| 1735 | |
| 1736 The FAQ is actively maintained and modified regularly. All links should | |
| 1737 be up to date. Unfortunately, some of the information is out of date -- | |
| 1738 a situation which the FAQ maintainer is working on. All submissions are | |
| 1739 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ | |
| 1740 maintainers}. | |
| 1741 | |
| 1742 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line. | |
| 1743 If you think you have a better way of answering a question, or think a | |
| 1744 question should be included, we'd like to hear about it. Questions and | |
| 1745 answers included into the FAQ will be edited for spelling and grammar | |
| 1746 and will be attributed. Answers appearing without attribution are | |
| 1747 either from versions of the FAQ dated before May 1996 or are from | |
| 1748 previous FAQ maintainers. Answers quoted from Usenet news articles will | |
| 1749 always be attributed, regardless of the author. | |
| 1750 | |
| 1751 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction | |
| 1752 @unnumberedsubsec Q1.5.2: How do I become a beta tester? | |
| 1753 | |
| 1754 Send an email message to @email{xemacs-beta-request@@xemacs.org} with | |
| 1755 the line @samp{subscribe} in the body of the message. | |
| 1756 | |
| 1757 Be prepared to get your hands dirty, as beta testers are expected to | |
| 1758 identify problems as best they can. | |
| 1759 | |
| 2559 | 1760 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction |
| 2537 | 1761 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself? |
| 1762 | |
| 1763 It depends on the knowledge and time you possess. If you are able, by | |
| 1764 all means become a beta tester (@pxref{Q1.5.2}). If you are a | |
| 1765 programmer, try to build XEmacs and see if you can improve it. | |
| 1766 | |
| 1767 Otherwise, you can still help by using XEmacs as your everyday editor | |
| 1768 (for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you | |
| 1769 find to the mailing list. | |
| 1770 | |
| 1771 Another area where we need help is the documentation: We need good | |
| 1772 documentation for building XEmacs and for using it. This FAQ is a | |
| 1773 small step in that direction. | |
| 1774 | |
| 1775 Ben Wing @email{ben@@xemacs.org} writes: | |
| 1776 | |
| 1777 @quotation | |
| 1778 BTW if you have a wish list of things that you want added, you have to | |
| 1779 speak up about it! More specifically, you can do the following if you | |
| 1780 want a feature added (in increasing order of usefulness): | |
| 1781 | |
| 1782 @itemize @bullet | |
| 1783 @item | |
| 1784 Make a posting about a feature you want added. | |
| 1785 | |
| 1786 @item | |
| 1787 Become a beta tester and make more postings about those same features. | |
| 1788 | |
| 1789 @item | |
| 1790 Convince us that you're going to use the features in some cool and | |
| 1791 useful way. | |
| 1792 | |
| 1793 @item | |
| 1794 Come up with a clear and well-thought-out API concerning the features. | |
| 1795 | |
| 1796 @item | |
| 1797 Write the code to implement a feature and send us a patch. | |
| 1798 @end itemize | |
| 1799 | |
| 1800 (not that we're necessarily requiring you to write the code, but we can | |
| 1801 always hope :) | |
| 1802 @end quotation | |
| 1803 | |
| 2559 | 1804 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction |
| 1805 @unnumberedsubsec Q1.5.4: How do I get started developing XEmacs? | |
| 1806 | |
| 1807 First, get yourself set up under CVS so that you can access the CVS | |
| 1808 repositories containing the XEmacs sources and the XEmacs packages. | |
| 1809 | |
| 1810 Next, set up your layout. This is important, as a good layout will | |
| 1811 facilitate getting things done efficiently, while a bad layout will could | |
| 1812 lead to disaster, as you can't figure out which code is the most recent, | |
| 1813 which can be thrown away, etc. We suggest the following layout: (feel free | |
| 1814 to make changes) | |
| 1815 | |
| 1816 @itemize @bullet | |
| 1817 @item | |
| 1818 Everything goes under @file{/src/xemacs} (use a different directory if | |
| 1819 you want). From now, instead of saying @file{/src/xemacs}, we use | |
| 1820 @file{<xsrc-top>}, to make it easier in case someone picked a | |
| 1821 different directory. | |
| 1822 | |
| 1823 @item | |
| 1824 Package source is in @file{<xsrc-top>/package-src}. | |
| 1825 | |
| 1826 @item | |
| 1827 Installed packages go under @file{<xsrc-top>/xemacs-packages}, and | |
| 1828 @file{<xsrc-top>/mule-packages}. | |
| 1829 | |
| 1830 @item | |
| 1831 A "workspace" is a complete copy of the sources, in which you do work of | |
| 1832 a particular kind. Workspaces can be differentiated by which branch of | |
| 1833 the source tree they extend off of -- usually either the stable or | |
| 1834 experimental, unless other branches have been created (for example, Ben | |
| 1835 created a branch for his Mule work because (1) the project was long-term | |
| 1836 and involved an enormous number of changes, (2) people wanted to be able | |
| 1837 to look at what his work in progress, and (3) he wanted to be able to | |
| 1838 check things in and in general use source-code control, since it was a | |
| 1839 long-term project). Workspaces are also differentiated in what their | |
| 1840 purpose is -- general working workspace, workspace for particular | |
| 1841 projects, workspace keeping the latest copy of the code in one of the | |
| 1842 branches without mods, etc. | |
| 1843 | |
| 1844 @item | |
| 1845 Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.: | |
| 1846 | |
| 1847 @itemize @bullet | |
| 1848 @item | |
| 1849 @file{<xsrc-top>/working} (the workspace you're actively working on, | |
| 1850 periodically synched up with the latest trunk) | |
| 1851 | |
| 1852 @item | |
| 1853 @file{<xsrc-top>/stable} (for making changes to the stable version of | |
| 1854 XEmacs, which sits on a branch) | |
| 1855 | |
| 1856 @item | |
| 1857 @file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult | |
| 1858 task that's going to affect lots of source and take a long time, and | |
| 1859 so best done in its own workspace without the interference of other | |
| 1860 work you're doing. Also, you can commit just this one large change, | |
| 1861 separate from all the other changes). | |
| 1862 | |
| 1863 @item | |
| 1864 @file{<xsrc-top>/latest} (a copy of the latest sources on the trunk, | |
| 1865 i.e. the experimental version of XEmacs, with no patches in it; | |
| 1866 either update it periodically, by hand, or set up a cron job to do it | |
| 1867 automatically). Set it up so it can be built, and build it so you | |
| 1868 have a working XEmacs. (Building it might also go into the cron job.) | |
| 1869 | |
| 1870 This workspace serves a number of purposes: | |
| 1871 @enumerate | |
| 1872 @item | |
| 1873 You always have a recent version of XEmacs you can compare | |
| 1874 against when something you're working on breaks. It's true | |
| 1875 that you can do this with cvs diff, but when you need to do | |
| 1876 some serious investigation, this method just fails. | |
| 1877 @item | |
| 1878 You (almost) always have a working, up-to-date executable that | |
| 1879 can be used when your executable is crashing and you need to | |
| 1880 keep developing it, or when you need an `xemacs' to build | |
| 1881 packages, etc. | |
| 1882 @item | |
| 1883 When creating new workspaces, you can just copy the `latest' | |
| 1884 workspace using GNU @code{cp -a}. You have all the .elc's built, | |
| 1885 everything else probably configured, any spare files in place | |
| 1886 (e.g. some annoying xpm.dll under Windows, etc.). | |
| 1887 @end enumerate | |
| 1888 | |
| 1889 @item | |
| 1890 @file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but | |
| 1891 for the Stable branch of XEmacs, rather than the Experimental branch | |
| 1892 of XEmacs). This may or may not be necessary depending on how much | |
| 1893 development you do of the stable branch. | |
| 1894 @end itemize | |
| 1895 | |
| 1896 @item | |
| 1897 @file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs | |
| 1898 web site. | |
| 1899 | |
| 1900 @item | |
| 1901 @file{<xsrc-top>/in-patches} for patches received from email and saved | |
| 1902 to files. | |
| 1903 | |
| 1904 @item | |
| 1905 @file{<xsrc-top>/out-patches} for locally-generated patches to be sent | |
| 1906 to @email{xemacs-patches@@xemacs.org}. Less useful now that the | |
| 1907 patcher util has been developed. | |
| 1908 | |
| 1909 @item | |
| 1910 @file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with | |
| 1911 various configuration options turned off and on. The scripts in | |
| 1912 xemacs-builds/ben (see below) can be used to automate building XEmacs | |
| 1913 workspaces with many different configuration options and automatically | |
| 1914 filtering out the normal output so that you see only the abnormal | |
| 1915 output. | |
| 1916 | |
| 1917 @item | |
| 1918 @file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need | |
| 1919 to check out separately in CVS. This contains scripts used for building | |
| 1920 XEmacs, automating and simplifying using CVS, etc. Under various | |
| 1921 people's directories are their own build and other scripts. The | |
| 1922 currently most-maintained scripts are under ben/, where there are easily | |
| 1923 configurable scripts that can be used to easily build any workspace | |
| 1924 (esp. if you've more or less followed the layout presented above) | |
| 1925 unattended, with one or more configuration states (there's a | |
| 1926 pre-determined list of the most useful, but it's easy to change). The | |
| 1927 output is filtered and split up in various ways so that you can identify | |
| 1928 which output came from where, and you can see the output either full or | |
| 1929 with all "normal" output except occasional status messages filtered so | |
| 1930 that you only see the abnormal ones. | |
| 1931 @end itemize | |
| 1932 | |
| 1933 @node Q1.5.5, Q1.6.1, Q1.5.4, Introduction | |
| 1934 @unnumberedsubsec Q1.5.5: What's the basic layout of the code? | |
| 1935 | |
| 1936 The file @file{configure} is a shell script to acclimate XEmacs to the | |
| 1937 oddities of your processor and operating system. It will create a | |
| 1938 file named @file{Makefile} (a script for the @file{make} program), which helps | |
| 1939 automate the process of building and installing emacs. See INSTALL | |
| 1940 for more detailed information. | |
| 1941 | |
| 1942 The file @file{configure.in} is the input used by the autoconf program to | |
| 1943 construct the @file{configure} script. Since XEmacs has configuration | |
| 1944 requirements that autoconf can't meet, @file{configure.in} uses an unholy | |
| 1945 marriage of custom-baked configuration code and autoconf macros; it | |
| 1946 may be wise to avoid rebuilding @file{configure} from @file{configure.in} when | |
| 1947 possible. | |
| 1948 | |
| 1949 The file @file{Makefile.in} is a template used by @file{configure} to create | |
| 1950 @file{Makefile}. | |
| 1951 | |
| 1952 There are several subdirectories: | |
| 1953 | |
| 1954 @enumerate | |
| 1955 @item | |
| 1956 @file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its | |
| 1957 primitives, the redisplay code, and some basic editing functions). | |
| 1958 @item | |
| 1959 @file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else). | |
| 1960 @item | |
| 1961 @file{lib-src} holds the source code for some utility programs for use by | |
| 1962 or with XEmacs, like movemail and etags. | |
| 1963 @item | |
| 1964 @file{etc} holds miscellaneous architecture-independent data files | |
| 1965 XEmacs uses, like the tutorial text. The contents of the @file{lisp}, | |
| 1966 @file{info} and @file{man} subdirectories are architecture-independent too. | |
| 1967 @item | |
| 1968 @file{lwlib} holds the C code for the X toolkit objects used by XEmacs. | |
| 1969 @item | |
| 1970 @file{info} holds the Info documentation tree for XEmacs. | |
| 1971 @item | |
| 1972 @file{man} holds the source code for the XEmacs online documentation. | |
| 1973 @item | |
| 1974 @file{nt} holds files used compiling XEmacs under Microsoft Windows. | |
| 1975 @end enumerate | |
| 1976 | |
| 2537 | 1977 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs) |
| 1978 | |
| 2559 | 1979 @node Q1.6.1, Q1.6.2, Q1.5.5, Introduction |
| 2537 | 1980 @unnumberedsubsec Q1.6.1: What is GNU Emacs? |
| 1981 | |
| 1982 GNU Emacs and XEmacs are related open-source text editors. Both | |
| 1983 derive from GNU Emacs version 18; the split between the two happened | |
| 1984 in 1991 (for comparison, the oldest versions of GNU Emacs date from | |
| 1985 1984). For information on GNU Emacs, see | |
| 1986 @uref{http://www.gnu.org/software/emacs/emacs.html}. | |
| 1987 | |
| 1988 @node Q1.6.2, Q1.6.3, Q1.6.1, Introduction | |
| 1989 @unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs? | |
| 428 | 1990 |
| 1991 For a detailed description of the differences between GNU Emacs and | |
| 1992 XEmacs and a detailed history of XEmacs, check out the | |
| 1993 @example | |
| 430 | 1994 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file} |
| 428 | 1995 @end example |
| 1996 | |
| 2417 | 1997 @table @strong |
| 1998 @item User-Visible Editing Features | |
| 1999 XEmacs in general tries hard to conform to exist user-interface | |
| 2000 standards, and to work "out-of-the-box" without the need for obscure | |
| 2001 customization changes. GNU Emacs, particularly version 21, has gotten | |
| 2002 better about this (in many cases by copying the XEmacs behavior!), but | |
| 2003 still has some weirdnesses. For example, the standard method of | |
| 2004 selecting text using the Shift key works out-of-the-box in XEmacs. | |
| 2005 | |
| 2006 XEmacs has a built-in toolbar. Four toolbars can actually be configured | |
| 2007 simultaneously: top, bottom, left, and right toolbars. | |
| 2008 | |
| 2009 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19 | |
| 2010 (which provides a primitive form of vertical scrollbar), these are true | |
| 2011 toolkit scrollbars. A look-alike Motif scrollbar is provided for those | |
| 2012 who don't have Motif. (Even for those who do, the look-alike may be | |
| 2013 preferable as it is faster.) | |
| 2014 | |
| 2015 XEmacs has buffer tabs along the top of the frame (although the | |
| 2016 position can be changed) that make it very easy to switch buffers. | |
| 2017 | |
| 2018 The menubar under XEmacs is better-designed, with more thought put into | |
| 2019 it. | |
| 2020 | |
| 2021 XEmacs can ask questions using popup dialog boxes. Any command executed | |
| 2022 from a menu will ask yes/no questions with dialog boxes, while commands | |
| 2023 executed via the keyboard will use the minibuffer. | |
| 2024 | |
| 2025 XEmacs under MS Windows provides uses the standard file-dialog box for | |
| 2026 opening and saving files. Standard menu-accelerator behavior can easily | |
| 2027 be enabled using the Options menu, and integrates well into the existing | |
| 2028 keymap. | |
| 2029 | |
| 2030 XEmacs has (still experimental) support for widgets of various sorts -- | |
| 2031 buttons, text boxes, sliders, progress bars, etc. A progress bar is | |
| 2032 used in font lock to show the progress. | |
| 2033 | |
| 2034 Experimental support for drag-and-drop protocols is provided from | |
| 2035 XEmacs 21. | |
| 2036 | |
| 2037 @item General Platform Support | |
| 2038 If you're running on a machine with audio hardware, you can specify | |
| 2039 sound files for XEmacs to play instead of the default X beep. See the | |
| 2040 documentation of the function load-sound-file and the variable | |
| 2041 sound-alist. XEmacs also supports the network sound protocols NAS and | |
| 2042 EsounD. | |
| 2043 | |
| 2044 XEmacs 21 supports database protocols with LISP bindings, currently | |
| 2045 including Berkeley DB, LDAP, and PostgreSQL (21.2 only). | |
| 2046 | |
| 2047 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method | |
| 2048 servers directly, as well as through the X Input Method (XIM) | |
| 2049 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen | |
| 2050 support the Quail family of input methods (implemented in LISP) for many | |
| 2051 languages. | |
| 2052 | |
| 2053 XEmacs provides support for ToolTalk on systems that have | |
| 2054 it. | |
| 2055 | |
| 2056 @item Packaged LISP Libraries | |
| 2057 Many more packages are provided standard with XEmacs than with GNU Emacs | |
| 2058 19 or 20. | |
| 2059 | |
| 2060 XEmacs 21 supports an integrated package management system which uses | |
| 2061 EFS to download, then automatically install prebuilt LISP | |
| 2062 libraries. This allows XEmacs users much more straightforward access to | |
| 2063 the "latest and greatest" version of any given library. | |
| 2064 | |
| 2065 We are working on a standard method for enabling, disabling and | |
| 2066 otherwise controlling packages, which should make them very easy to use. | |
| 2067 | |
| 2068 @item LISP Programming | |
| 2069 From XEmacs 20 on, characters are a separate type. Characters can be | |
| 2070 converted to integers (and many integers can be converted to | |
| 2071 characters), but characters are not integers. GNU Emacs 19, XEmacs 19, | |
| 2072 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs | |
| 2073 20 (incorporating Mule 3 and later Mule 4) represent them as integers. | |
| 2074 | |
| 2075 From XEmacs 20 on, the buffer is treated as an array of characters, and | |
| 2076 the representation of buffer text is not exposed to LISP. The GNU Emacs | |
| 2077 20 functions like buffer-as-multibyte are not supported. | |
| 2078 | |
| 2079 In XEmacs, events are first-class objects. GNU Emacs 19 represents them | |
| 2080 as integers, which obscures the differences between a key gesture and | |
| 2081 the ancient ASCII code used to represent a particular overlapping subset | |
| 2082 of them. | |
| 2083 | |
| 2084 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19 | |
| 2085 represents them as complicated combinations of association lists and | |
| 2086 vectors. If you use the advertised functional interface to manipulation | |
| 2087 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU | |
| 2088 Emacs 19; if your code depends on the underlying implementation of | |
| 2089 keymaps, it will not. | |
| 2090 | |
| 2091 XEmacs uses "extents" to represent all non-textual aspects of buffers; | |
| 2092 GNU Emacs 19 uses two distinct objects, "text properties" and | |
| 2093 "overlays", which divide up the functionality between them. Extents are | |
| 2094 a superset of the union of the functionality of the two GNU Emacs data | |
| 2095 types. The full GNU Emacs 19 interface to text properties and overlays | |
| 2096 is supported in XEmacs (with extents being the underlying | |
| 2097 representation). | |
| 2098 | |
| 2099 Extents can be made to be copied into strings, and then restored, by | |
| 2100 kill and yank. Thus, one can specify this behavior on either "extents" | |
| 2101 or "text properties", whereas in GNU Emacs 19 text properties always | |
| 2102 have this behavior and overlays never do. | |
| 2103 | |
| 2104 @item Window System Programming Interface | |
| 2105 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes | |
| 2106 it be a more well-behaved X citizen (and also improves portability). A | |
| 2107 result of this is that it is possible to include other Xt "Widgets" in | |
| 2108 the XEmacs window. Also, XEmacs understands the standard Xt command-line | |
| 2109 arguments. | |
| 2110 | |
| 2111 XEmacs supports Motif applications, generic Xt (e.g. Athena) | |
| 2112 applications, and raw Xlib applications. An XEmacs variant which | |
| 2113 supports GTK+ is available (integration as an option in the XEmacs | |
| 2114 mainline is planned for XEmacs 22), although code to take advantage of | |
| 2115 the support is as yet scarce. | |
| 2116 | |
| 2117 An XEmacs frame can be placed within an "external client widget" managed | |
| 2118 by another application. This allows an application to use an XEmacs | |
| 2119 frame as its text pane rather than the standard Text widget that is | |
| 2120 provided with Motif or Athena. | |
| 2121 | |
| 2122 @item Community Participation | |
| 2459 | 2123 Joining the XEmacs development team is simple. Mail to |
| 2124 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If | |
| 2125 you want to be, of course. You're also welcome to just post | |
| 2126 development-related questions and bug reports.) The GNU Emacs | |
| 2417 | 2127 development team and internal mailing lists are still by invitation |
| 2128 only. | |
| 2129 | |
| 2130 The "bleeding edge" of mainline XEmacs development is available by | |
| 2131 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk | |
| 2132 module for the latest in GUI features!) | |
| 2133 | |
| 2134 Development and maintenance of Lisp libraries is separated from the core | |
| 2135 editor development at a fairly low level. This provides better | |
| 2136 modularization and a better division of responsibility between external | |
| 2137 library maintainers and the XEmacs core development team. Even for | |
| 2138 packages the size of Gnus, XEmacs users normally have access to a | |
| 2139 pre-built version within a few weeks of a major release, and minor | |
| 2140 updates often within days. | |
| 2141 | |
| 2142 CVS commit authority is broadly dispersed. Recognized maintainers of | |
| 2143 LISP libraries who are willing to maintain XEmacs packaged versions | |
| 2144 automatically qualify for CVS accounts for their packages. | |
| 2145 @end table | |
| 2146 | |
| 2537 | 2147 @node Q1.6.3, Q1.6.4, Q1.6.2, Introduction |
| 2148 @unnumberedsubsec Q1.6.3: How much does XEmacs differ? | |
| 2417 | 2149 |
| 2150 RMS has asserted at times that XEmacs is merely a "patch" on top of | |
| 2537 | 2151 GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the |
| 2417 | 2152 code, if that, remains unchanged, and nearly 14 years of work has gone |
| 2153 into XEmacs at this point. (GNU Emacs itself is only than 20 years | |
| 2154 old, and thus XEmacs has existed as a separate product for over 2/3 of | |
| 2155 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has | |
| 2156 perhaps 65,000 more lines of C code than GNU Emacs 21.2. | |
| 2157 | |
| 2158 However, the XEmacs developers strive to keep their code compatible with | |
| 2159 GNU Emacs, especially on the Lisp level. Much effort goes into | |
| 2160 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to | |
| 2161 benefit from GNU Emacs development work. (In contrast, almost no code | |
| 2162 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs | |
| 2163 developers are instructed by RMS not to even look at XEmacs source code! | |
| 2164 This stems from self-imposed licensing restrictions on the part of GNU | |
| 2165 Emacs -- and almost certainly out of hostility, as well.) | |
| 2166 | |
| 2537 | 2167 @node Q1.6.4, Q1.6.5, Q1.6.3, Introduction |
| 2168 @unnumberedsubsec Q1.6.4: Is XEmacs "GNU"? | |
| 2417 | 2169 |
| 2170 RMS insists on the term "GNU XEmacs" and maintains that | |
| 2171 | |
| 2172 @quotation | |
| 2173 XEmacs is GNU software because it's a modified version of a | |
| 2174 GNU program. And it is GNU software because the FSF is the copyright | |
| 2175 holder for most of it, and therefore the legal responsibility for | |
| 2176 protecting its free status falls on us whether we want it or not. This | |
| 2177 is why the term "GNU XEmacs" is legitimate. | |
| 2178 @end quotation | |
| 2179 | |
| 2180 In fact, FSF is @emph{not} the copyright holder for most of the code, | |
| 2537 | 2181 as very little unmodified FSF code remains (@pxref{Q1.6.3}). |
| 2417 | 2182 |
| 2183 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre | |
| 2184 to the XEmacs developers given RMS's hostility and general lack of | |
| 2185 interest in cooperation. "GNU" software in general is part of the GNU | |
| 2186 Project, is distributed by it on their FTP site, and receives support | |
| 2187 (or at least cooperation), as well as implicit endorsement, from it. | |
| 2188 The GNU Project, however, has never supported XEmacs and never | |
| 2189 distributed XEmacs, and RMS's hostility is the farthest thing possible | |
| 2190 from an endorsement. In fact, the GNU Project distributes a number of | |
| 2191 non-GNU software projects on the FSF web site, but again XEmacs is not | |
| 2192 one of them. | |
| 2193 | |
| 2537 | 2194 @node Q1.6.5, Q1.6.6, Q1.6.4, Introduction |
| 2195 @unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 2417 | 2196 |
| 2197 Unfortunately even the naming of these two applications has become | |
| 2198 politicized. Much of this stems from RMS, who has a history of | |
| 2199 politicizing similar issues. (Compare the controversy over "Lignux" | |
| 2200 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU | |
| 2201 Emacs" be used, which are neutral and acceptable to most people. RMS, | |
| 2202 however, is not willing to accept these terms. He insists that, if | |
| 2203 his product is called "GNU Emacs", then ours must be called "GNU | |
| 2537 | 2204 XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other |
| 2417 | 2205 hand, if our product is to be called "XEmacs", as we prefer, then his |
| 2206 product must simply be called "Emacs". The intent of this seems | |
| 2207 clear: RMS wants to make sure the names reflect his view that his | |
| 2208 version is the "real" Emacs and ours is merely a derivative, | |
| 2537 | 2209 second-class product (@pxref{Q1.6.3}). |
| 2417 | 2210 |
| 2211 The XEmacs developers hope that you will use the neutral terms | |
| 2212 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on | |
| 2213 the other hand, is a generic term for a class of programmable text | |
| 2214 editors with a similar look-and-feel, and usually a Lisp-based | |
| 2215 extension language. These trace themselves back to early editors such | |
| 2216 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,, | |
| 2217 internals, XEmacs Internals Manual}. | |
| 2218 | |
| 2219 We also call upon RMS, in the spirit of furthering cooperation, to | |
| 2220 stop politicizing this issue and use the neutral terms "XEmacs" and | |
| 2221 "GNU Emacs". We have already acceded to RMS' wishes in this respect, | |
| 2222 and we expect him to do the same. (In the past, the XEmacs developers | |
| 2223 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in | |
| 2224 reference to GNU Emacs; these terms were apparently modeled after RMS' | |
| 2225 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress | |
| 2226 Emacs, produced by James Gosling. RMS, however, considers such terms | |
| 2227 to be insulting, so we refrain from using them as much as possible in | |
| 2228 preference to GNU Emacs.) | |
| 2229 | |
| 2537 | 2230 @node Q1.6.6, Q1.7.1, Q1.6.5, Introduction |
| 2231 @unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged? | |
| 2417 | 2232 |
| 2233 There are currently irreconcilable differences in the views about | |
| 2234 technical, programming, design, organizational and legal matters | |
| 2235 between Richard Stallman (RMS), the author and leader of the GNU Emacs | |
| 2236 project, and the XEmacs development team which provide little hope for | |
| 2237 a merge to take place in the short-term future. There have been | |
| 2238 repeated attempts at merging by all of the major XEmacs developers, | |
| 2239 starting from the early days of Lucid Emacs (in 1991), but they have | |
| 2240 all failed. RMS has very strong views about how GNU Emacs should be | |
| 2241 structured and how his project should be run, and during the repeated | |
| 2242 merge efforts has never demonstrated any realistic interest in | |
| 2243 sufficiently compromising or ceding control to allow a middle ground | |
| 2244 to be found. The basic problem seems to be the very different goals | |
| 2245 of RMS and the XEmacs project. The primary goals of the XEmacs | |
| 2246 project are technical and organizational -- we want to create the best | |
| 2247 editor possible, and to make it as easy as possible for people around | |
| 2248 the world to contribute. The primary goals of RMS, on the other hand, | |
| 2249 are political, and GNU Emacs, and any potential merge efforts with | |
| 2250 XEmacs, are strictly subservient to these goals. In fact, in many | |
| 2251 ways RMS sees GNU Emacs as the "poster child" of his aims, the one | |
| 2252 program in the GNU project that above all others must set an example | |
| 2253 to the world. (This has to do with the fact that GNU Emacs was the | |
| 2254 first program in the GNU project, and the only one that he is still | |
| 2255 personally involved with on a day-to-day basis.) Given his goals, his | |
| 2256 position is completely reasonable -- but unfortunately, makes any | |
| 2257 merge impossible. | |
| 2258 | |
| 2259 From the XEmacs perspective, the most intractable issues appear to be | |
| 2260 legal and organizational, specifically: | |
| 428 | 2261 |
| 2262 @itemize @bullet | |
| 2263 @item | |
| 2417 | 2264 RMS requires "legal papers" to be signed for all contributions of code |
| 2265 to GNU Emacs over 10 lines or so, transferring the copyright and all | |
| 2266 legal rights to the code to the Free Software Foundation. XEmacs does | |
| 2267 not and has never required this, since it has the practical effect of | |
| 2268 discouraging individual and in particular corporate contributions -- | |
| 2269 corporations will almost never sign away their legal rights to code | |
| 2270 since it makes it impossible to reuse the code in any product that | |
| 2271 whose license is not compatible with the GNU General Public License. | |
| 2272 Since RMS has shown no inclination to compromise on this issue, a | |
| 2273 merge would require that most of the existing XEmacs code would need | |
| 2274 to be thrown away and rewritten -- something the XEmacs developers are | |
| 2275 understandably reluctant to do. | |
| 2276 | |
| 2277 @item | |
| 2278 A repeated stumbling block in the merge talks has been the issue of | |
| 2279 organizational control over the resulting product. RMS has made it | |
| 2280 clear that he intends to have final say over design issues in a merged | |
| 2281 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly | |
| 2282 clashed over design decisions, and RMS' insistence on getting his way | |
| 2283 in such disagreements was the very reason for the split in the first | |
| 2284 place. This same issue has come up again and again in merge talks and | |
| 2285 we have never been able to come to a satisfactory resolution. To the | |
| 2286 extent that RMS is willing to compromise at all, it appears to be of a | |
| 2287 purely political rather than technical nature -- "If we support this | |
| 2288 feature of yours, we also get to support this other feature of mine." | |
| 2289 The XEmacs developers cannot see how such a process would lead to | |
| 2290 anything but a mess of incompatible things hodgepodged together. | |
| 2291 | |
| 2292 @item | |
| 2293 Because of the years of separate development, distinct and | |
| 2294 incompatible interfaces have developed and merging would be extremely | |
| 2295 difficult even with the above non-technical issues resolved. The | |
| 2296 problem has been exacerbated by the issue of legal papers -- because | |
| 2297 XEmacs code is not "kosher" from RMS' perspective, he discourages | |
| 2298 developers from even looking at it out of legal concerns. Although it | |
| 2299 is still possible to read the XEmacs documentation and run the | |
| 2300 program, the practical effect of this prohibition has been to strongly | |
| 2301 discourage code-sharing and cooperative development -- although a | |
| 2302 great deal of GNU Emacs code has been incorporated into XEmacs, | |
| 2303 practically none has gone the other direction. | |
| 428 | 2304 @end itemize |
| 2305 | |
| 2306 If you have a comment to add regarding the merge, it is a good idea to | |
| 2417 | 2307 avoid posting to the newsgroups, because of the very heated flamewars |
| 2308 that often result. Mail your questions to | |
| 2309 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}. | |
| 2310 | |
| 2537 | 2311 @unnumberedsec 1.7: External Packages |
| 2312 | |
| 2559 | 2313 @node Q1.7.1, Q1.7.2, Q1.6.6, Introduction |
| 2314 @unnumberedsubsec Q1.7.1: What is the package system? | |
| 2315 | |
| 2316 In order to reduce the size and increase the maintainability of | |
| 2317 XEmacs, the majority of the Elisp packages that came with previous | |
| 2318 releases have been unbundled. They have been replaced by the package | |
| 2319 system. Each elisp add-on (or groups of them when they are small) now | |
| 2320 comes in its own tarball that contains a small search hierarchy. | |
| 2321 | |
| 2322 You select just the ones you need. Install them by untarring them into | |
| 2323 the right place. On startup XEmacs will find them, set up the load | |
| 2324 path correctly, install autoloads, etc, etc. | |
| 2325 | |
| 2326 @xref{Q2.1.1}, for more info on how to download and install the packages. | |
| 2327 | |
| 2328 @node Q1.7.2, Q1.7.3, Q1.7.1, Introduction | |
| 2329 @unnumberedsubsec Q1.7.2: Which external packages are there? | |
| 2537 | 2330 |
| 2331 @subheading Normal Packages | |
| 2332 | |
| 2333 A very broad collection of elisp packages. | |
| 2417 | 2334 |
| 2335 @table @asis | |
| 2537 | 2336 @item Sun |
| 2337 Support for Sparcworks. | |
| 2338 | |
| 2339 @item ada | |
| 2340 Ada language support. | |
| 2341 | |
| 2342 @item apel | |
| 2343 A Portable Emacs Library. Used by XEmacs MIME support. | |
| 2344 | |
| 2345 @item auctex | |
| 2346 Basic TeX/LaTeX support. | |
| 2347 | |
| 2348 @item bbdb | |
| 2349 The Big Brother Data Base: a rolodex-like database program. | |
| 2350 | |
| 2351 @item build | |
| 2352 Build XEmacs from within (UNIX, Windows). | |
| 2353 | |
| 2354 @item c-support | |
| 2355 Basic single-file add-ons for editing C code. | |
| 2356 | |
| 2357 @item calc | |
| 2358 Emacs calculator. | |
| 2359 | |
| 2360 @item calendar | |
| 2361 Calendar and diary support. | |
| 2362 | |
| 2363 @item cc-mode | |
| 2364 C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support. | |
| 2365 | |
| 2366 @item clearcase | |
| 2367 New Clearcase Version Control for XEmacs (UNIX, Windows). | |
| 2368 | |
| 2369 @item clearcase | |
| 2370 Support for the Clearcase version control system. | |
| 2371 | |
| 2372 @item cookie | |
| 2373 "Fortune cookie"-style messages. Includes Spook (suspicious phrases) | |
| 2374 and Yow (Zippy quotes). | |
| 2375 | |
| 2376 @item crisp | |
| 2377 Crisp/Brief emulation. | |
| 2378 | |
| 2379 @item debug | |
| 2380 GUD, gdb, dbx debugging support. | |
| 2381 | |
| 2382 @item dictionary | |
| 2383 Interface to RFC2229 dictionary servers. | |
| 2384 | |
| 2385 @item dired | |
| 2386 The DIRectory EDitor is for manipulating, and running commands on | |
| 2387 files in a directory. | |
| 2388 | |
| 2389 @item docbookide | |
| 2390 DocBook editing support. | |
| 2391 | |
| 2392 @item ecb | |
| 2393 Emacs source code browser. | |
| 2394 | |
| 2395 @item ecrypto | |
| 2396 Crypto functionality in Emacs Lisp. | |
| 2397 | |
| 2398 @item edebug | |
| 2399 An Emacs Lisp debugger. | |
| 2400 | |
| 2401 @item ediff | |
| 2402 Interface over GNU patch. | |
| 2403 | |
| 2404 @item edit-utils | |
| 2405 Miscellaneous editor extensions, you probably need this. | |
| 2406 | |
| 2407 @item edt | |
| 2408 DEC EDIT/EDT emulation. | |
| 2409 | |
| 2410 @item efs | |
| 2411 Treat files on remote systems the same as local files. | |
| 2412 | |
| 2413 @item eieio | |
| 2414 Enhanced Implementation of Emacs Interpreted Objects. | |
| 2415 | |
| 2416 @item elib | |
| 2417 Portable Emacs Lisp utilities library. | |
| 2418 | |
| 2419 @item emerge | |
| 2420 Another interface over GNU patch. | |
| 2421 | |
| 2422 @item erc | |
| 2423 ERC is an Emacs InternetRelayChat client. | |
| 2424 | |
| 2425 @item escreen | |
| 2426 Multiple editing sessions withing a single frame (like screen). | |
| 2427 | |
| 2428 @item eshell | |
| 2429 Command shell implemented entirely in Emacs Lisp. | |
| 2430 | |
| 2431 @item ess | |
| 2432 ESS: Emacs Speaks Statistics. | |
| 2433 | |
| 2434 @item eterm | |
| 2435 Terminal emulation. | |
| 2436 | |
| 2437 @item eudc | |
| 2438 Emacs Unified Directory Client (LDAP, PH). | |
| 2439 | |
| 2440 @item footnote | |
| 2441 Footnoting in mail message editing modes. | |
| 2442 | |
| 2443 @item forms | |
| 2444 Forms editing support (obsolete, use Widget instead). | |
| 2445 | |
| 2446 @item fortran-modes | |
| 2447 Fortran support. | |
| 2448 | |
| 2449 @item fortran-modes | |
| 2450 Fortran language support. | |
| 2451 | |
| 2452 @item frame-icon | |
| 2453 Set up mode-specific icons for each frame under XEmacs. | |
| 2454 | |
| 2455 @item fsf-compat | |
| 2456 GNU Emacs compatibility files. | |
| 2457 | |
| 2458 @item games | |
| 2459 Tetris, Sokoban, and Snake. | |
| 2460 | |
| 2461 @item general-docs | |
| 2462 General documentation. Presently, empty. | |
| 2463 | |
| 2464 @item gnats | |
| 2465 XEmacs bug reports. | |
| 2466 | |
| 2467 @item gnus | |
| 2468 The Gnus Newsreader and Mailreader. | |
| 2469 | |
| 2470 @item haskell-mode | |
| 2471 Haskell editing support. | |
| 2472 | |
| 2473 @item hm--html-menus | |
| 2474 HTML editing. | |
| 2475 | |
| 2476 @item hyperbole | |
| 2477 Hyperbole: The Everyday Info Manager. | |
| 2478 | |
| 2479 @item ibuffer | |
| 2480 Advanced replacement for buffer-menu. | |
| 2481 | |
| 2482 @item idlwave | |
| 2483 Editing and Shell mode for the Interactive Data Language. | |
| 2484 | |
| 2485 @item igrep | |
| 2486 Enhanced front-end for Grep. | |
| 2487 | |
| 2488 @item ilisp | |
| 2489 Front-end for interacting with Inferior Lisp (external lisps). | |
| 2490 | |
| 2491 @item ispell | |
| 2492 Spell-checking with GNU ispell. | |
| 2493 | |
| 2494 @item jde | |
| 2495 Integrated Development Environment for Java. | |
| 2496 | |
| 2497 @item liece | |
| 2498 IRC (Internet Relay Chat) client for Emacs. Note, this package is | |
| 2499 deprecated and will be removed, use riece instead. | |
| 2500 | |
| 2501 @item mail-lib | |
| 2502 Fundamental lisp files for providing email support. | |
| 2503 | |
| 2504 @item mailcrypt | |
| 2505 Support for messaging encryption with PGP. | |
| 2506 | |
| 2507 @item mew | |
| 2508 Messaging in an Emacs World; a MIME-based email program. | |
| 2509 | |
| 2510 @item mh-e | |
| 2511 The XEmacs Interface to the MH Mail System. | |
| 2512 | |
| 2513 @item mine | |
| 2514 Elisp implementation of the game 'Minehunt'. | |
| 2515 | |
| 2516 @item misc-games | |
| 2517 Other amusements and diversions. | |
| 2518 | |
| 2519 @item mmm-mode | |
| 2520 Support for Multiple Major Modes within a single buffer. | |
| 2521 | |
| 2522 @item net-utils | |
| 2523 Miscellaneous Networking Utilities. | |
| 2524 | |
| 2525 @item ocaml | |
| 2526 Objective Caml editing support. | |
| 2527 | |
| 2528 @item oo-browser | |
| 2529 OO-Browser: The Multi-Language Object-Oriented Code Browser. | |
| 2530 | |
| 2531 @item ocaml | |
| 2532 Objective Caml editing support. | |
| 2533 | |
| 2534 @item os-utils | |
| 2535 Miscellaneous single-file O/S utilities, for printing, archiving, | |
| 2536 compression, remote shells, etc. | |
| 2537 | |
| 2538 @item pc | |
| 2539 PC style interface emulation. | |
| 2540 | |
| 2541 @item pcl-cvs | |
| 2542 CVS frontend. | |
| 2543 | |
| 2544 @item pcomplete | |
| 2545 Provides programmatic completion. | |
| 2546 | |
| 2547 @item perl-modes | |
| 2548 Perl support. | |
| 2549 | |
| 2550 @item pgg | |
| 2551 Emacs interface to various PGP implementations. | |
| 2552 | |
| 2553 @item prog-modes | |
| 2554 Support for various programming languages. | |
| 2555 | |
| 2556 @item ps-print | |
| 2557 Printing functions and utilities. | |
| 2558 | |
| 2559 @item psgml | |
| 2560 Validated HTML/SGML editing. | |
| 2561 | |
| 2562 @item psgml-dtds | |
| 2563 A collection of DTDs for psgml. Note that this package is deprecated | |
| 2564 and will be removed in the future, most likely Q2/2003. Instead of using | |
| 2565 this, you should install needed DTDs yourself. | |
| 2566 | |
| 2567 @item python-modes | |
| 2568 Python language support. | |
| 2569 | |
| 2570 @item reftex | |
| 2571 Emacs support for LaTeX cross-references, citations. | |
| 2572 | |
| 2573 @item riece | |
| 2574 IRC (Internet Relay Chat) client for Emacs. | |
| 2575 | |
| 2576 @item rmail | |
| 2577 An obsolete Emacs mailer. If you do not already use it don't start. | |
| 2578 | |
| 2579 @item ruby-modes | |
| 2580 Ruby support. | |
| 2581 | |
| 2582 @item sasl | |
| 2583 Simple Authentication and Security Layer (SASL) library. | |
| 2584 | |
| 2585 @item scheme | |
| 2586 Front-end support for Inferior Scheme. | |
| 2587 | |
| 2588 @item semantic | |
| 2589 Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator. | |
| 2590 | |
| 2591 @item sgml | |
| 2592 SGML/Linuxdoc-SGML editing. | |
| 2593 | |
| 2594 @item sh-script | |
| 2595 Support for editing shell scripts. | |
| 2596 | |
| 2597 @item sieve | |
| 2598 Manage Sieve email filtering scripts. | |
| 2599 | |
| 2600 @item slider | |
| 2601 User interface tool. | |
| 2602 | |
| 2603 @item sml-mode | |
| 2604 SML editing support. | |
| 2605 | |
| 2606 @item sounds-au | |
| 2607 XEmacs Sun sound files. | |
| 2608 | |
| 2609 @item sounds-wav | |
| 2610 XEmacs Microsoft sound files. | |
| 2611 | |
| 2612 @item speedbar | |
| 2613 Provides a separate frame with convenient references. | |
| 2614 | |
| 2615 @item strokes | |
| 2616 Mouse enhancement utility. | |
| 2617 | |
| 2618 @item supercite | |
| 2619 An Emacs citation tool for News & Mail messages. | |
| 2620 | |
| 2621 @item texinfo | |
| 2622 XEmacs TeXinfo support. | |
| 2623 | |
| 2624 @item text-modes | |
| 2625 Miscellaneous support for editing text files. | |
| 2626 | |
| 2627 @item textools | |
| 2628 Miscellaneous TeX support. | |
| 2629 | |
| 2630 @item time | |
| 2631 Display time & date on the modeline. | |
| 2632 | |
| 2633 @item tm | |
| 2634 Emacs MIME support. Not needed for gnus >= 5.8.0. | |
| 2635 | |
| 2636 @item tooltalk | |
| 2637 Support for building with Tooltalk. | |
| 2638 | |
| 2639 @item tpu | |
| 2640 DEC EDIT/TPU support. | |
| 2641 | |
| 2642 @item tramp | |
| 2643 Remote shell-based file editing. This is similar to EFS or Ange-FTP, | |
| 2644 but works with rsh/ssh and rcp/scp. | |
| 2645 | |
| 2646 @item vc | |
| 2647 Version Control for Free systems. | |
| 2648 | |
| 2649 @item vc-cc | |
| 2650 Version Control for ClearCase (UnFree) systems. | |
| 2651 | |
| 2652 @item vhdl | |
| 2653 Support for VHDL. | |
| 2654 | |
| 2655 @item view-process | |
| 2656 A Unix process browsing tool. | |
| 2657 | |
| 2658 @item viper | |
| 2659 VI emulation support. | |
| 2660 | |
| 2661 @item vm | |
| 2662 An Emacs mailer. | |
| 2663 | |
| 2664 @item w3 | |
| 2665 A Web browser. | |
| 2666 | |
| 2667 @item x-symbol | |
| 2668 Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts. | |
| 2669 | |
| 2670 @item xemacs-base | |
| 2671 Fundamental XEmacs support, you almost certainly need this. | |
| 2672 | |
| 2673 @item xemacs-devel | |
| 2674 XEmacs Lisp developer support. This package contains utilities for | |
| 2675 supporting Lisp development. It is a single-file package so it may be | |
| 2676 tailored. | |
| 2677 | |
| 2678 @item xlib | |
| 2679 Emacs interface to X server. | |
| 2680 | |
| 2681 @item xslide | |
| 2682 XSL editing support. | |
| 2683 | |
| 2684 @item xslt-process | |
| 2685 A minor mode for (X)Emacs which allows running an XSLT processor on a | |
| 2686 buffer. | |
| 2687 | |
| 2688 @item xwem | |
| 2689 X Emacs Window Manager. | |
| 2690 | |
| 2691 @item zenirc | |
| 2692 ZENIRC IRC Client. | |
| 2417 | 2693 @end table |
| 2694 | |
| 2537 | 2695 @subheading Mule Support (mule) |
| 2696 | |
| 2697 MULti-lingual Enhancement. Support for world scripts such as | |
| 2698 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc. | |
| 2699 To use these packages your XEmacs must be compiled with Mule | |
| 2700 support. | |
| 2701 | |
| 2702 @table @asis | |
| 2703 @item edict | |
| 2704 MULE: Lisp Interface to EDICT, Kanji Dictionary. | |
| 2705 | |
| 2706 @item egg-its | |
| 2707 MULE: Wnn (4.2 and 6) support. SJ3 support. | |
| 2708 | |
| 2709 @item latin-unity | |
| 2710 MULE: find single ISO 8859 character set to encode a buffer. | |
| 2711 | |
| 2712 @item latin-unity | |
| 2713 Unify character sets in a buffer. When characters belong to disjoint | |
| 2714 character sets, this attempts to translate the characters so | |
| 2715 that they belong to one character set. If the buffer coding system is | |
| 2716 not sufficient, this suggests different coding systems. | |
| 2717 | |
| 2718 @item leim | |
| 2719 MULE: Quail. All non-English and non-Japanese language support. | |
| 2720 | |
| 2721 @item locale | |
| 2722 MULE: Localized menubars and localized splash screens. | |
| 2723 | |
| 2724 @item lookup | |
| 2725 Dictionary support. (This isn't an English dictionary program) | |
| 2726 | |
| 2727 @item mule-base | |
| 2728 MULE: Basic Mule support, required for building with Mule. | |
| 2729 | |
| 2730 @item mule-ucs | |
| 2731 MULE: Extended coding systems (including Unicode) for XEmacs. | |
| 2732 | |
| 2733 @item mule-ucs | |
| 2734 Extended coding systems (including Unicode) for XEmacs. | |
| 2735 | |
| 2736 @item skk | |
| 2737 Another Japanese Language Input Method. Can be used without a | |
| 2738 separate process running as a dictionary server. | |
| 2739 @end table | |
| 2740 | |
| 2559 | 2741 @node Q1.7.3, Q1.7.4, Q1.7.2, Introduction |
| 2742 @unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs? | |
| 2743 | |
| 2744 Strictly speaking, no. XEmacs will build and install just fine without | |
| 2745 any packages installed. However, only the most basic editing functions | |
| 2746 will be available with no packages installed, so installing packages is | |
| 2747 an essential part of making your installed XEmacs _useful_. | |
| 2748 | |
| 2749 @node Q1.7.4, Q1.8.1, Q1.7.3, Introduction | |
| 2750 @unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality? | |
| 2751 | |
| 2752 If you want to find out which package contains the functionality you | |
| 2753 are looking for, use @kbd{M-x package-get-package-provider}, and give it a | |
| 2754 symbol that is likely to be in that package. | |
| 2755 | |
| 2756 For example, if some code you want to use has a @code{(require 'thingatpt)} | |
| 2757 in it: | |
| 2758 | |
| 2759 @example | |
| 2760 M-x package-get-package-provider RET thingatpt RET | |
| 2761 @end example | |
| 2762 | |
| 2763 which will return something like: @samp{(fsf-compat "1.08").} | |
| 2764 | |
| 2537 | 2765 @unnumberedsec 1.8: Internationalization |
| 2766 | |
| 2559 | 2767 @node Q1.8.1, Q1.8.2, Q1.7.4, Introduction |
| 2537 | 2768 @unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)? |
| 442 | 2769 |
| 2770 Both the stable and development versions of XEmacs include | |
| 1135 | 2771 internationalization support (aka MULE). MULE currently (21.4) works on |
| 2772 UNIX and Linux systems. It is possible to build with MULE on Windows | |
| 2773 systems, but if you really need MULE on Windows, it is recommended that | |
| 2774 you build and use the development (21.5) version, and deal with the | |
| 2775 instability of the development tree. Binaries compiled without MULE | |
| 2776 support run faster than MULE capable XEmacsen. | |
| 428 | 2777 |
| 2537 | 2778 @node Q1.8.2, Q1.8.3, Q1.8.1, Introduction |
| 2779 @unnumberedsubsec Q1.8.2: How can I help with internationalization? | |
| 430 | 2780 |
| 2781 If you would like to help, you may want to join the | |
| 2782 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are | |
| 2783 people who speak/write languages other than English, who are willing to | |
| 2784 use XEmacs/MULE regularly, and have some experience with Elisp. | |
| 428 | 2785 |
| 1135 | 2786 Translations of the TUTORIAL and man page are welcome, and XEmacs does |
| 2787 support multilingual menus, but we have few current translations. | |
| 2788 | |
| 2537 | 2789 @xref{Q1.5.2, How do I become a Beta Tester?}. |
| 2790 | |
| 2791 @node Q1.8.3, Q1.8.4, Q1.8.2, Introduction | |
| 2792 @unnumberedsubsec Q1.8.3: How do I type non-ASCII characters? | |
| 2417 | 2793 |
| 2459 | 2794 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in |
| 2417 | 2795 part 3 of this FAQ, for some simple methods that also work in non-MULE |
| 2796 builds of XEmacs (but only for one-octet coded character sets, and | |
| 2797 mostly for ISO 8859/1). Many of the methods available for Cyrillic | |
| 2537 | 2798 (@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE |
| 2799 has more general capabilities. @xref{Q1.8.5, Please explain the | |
| 2417 | 2800 various input methods in MULE/XEmacs}. |
| 2801 | |
| 2459 | 2802 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers |
| 2417 | 2803 display of non-ASCII characters. |
| 2804 | |
| 2537 | 2805 @node Q1.8.4, Q1.8.5, Q1.8.3, Introduction |
| 2806 @unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language? | |
| 428 | 2807 |
| 1135 | 2808 The message-catalog support was written but is badly bit-rotted. XEmacs |
| 2809 20 and 21 did @emph{not} support it, and early releases of XEmacs 22 | |
| 2810 will not either. | |
| 2811 | |
| 2812 However, menubar localization @emph{does} work. To enable it, add to | |
| 2813 your @file{Emacs} file entries like this: | |
| 428 | 2814 |
| 2815 @example | |
| 440 | 2816 Emacs*XlwMenu.resourceLabels: True |
| 2817 Emacs*XlwMenu.file.labelString: Fichier | |
| 442 | 2818 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen |
| 428 | 2819 @end example |
| 2820 | |
| 2821 The name of the resource is derived from the non-localized entry by | |
| 2822 removing punctuation and capitalizing as above. | |
| 2823 | |
| 2537 | 2824 @node Q1.8.5, Q1.8.6, Q1.8.4, Introduction |
| 2825 @unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs | |
| 428 | 2826 |
| 1135 | 2827 Mule supports a wide variety of input methods. There are three basic |
| 2828 classes: Lisp implementations, generic platform support, and library | |
| 2829 interfaces. | |
| 2830 | |
| 2831 @emph{Lisp implementations} include Quail, which provides table-driven input | |
| 2832 methods for almost all the character sets that Mule supports (including | |
| 2833 all of the ISO 8859 family, the Indic languages, Thai, and so on), and | |
| 2834 SKK, for Japanese. (SKK also supports an interface to an external | |
| 2835 "dictionary server" process.) Quail supports both typical "dead-key" | |
| 2836 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN | |
| 2837 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic | |
| 2838 methods used for Asian ideographic languages like Chinese. | |
| 2839 | |
| 2840 Lisp implementations can be less powerful (but they are not perceptibly | |
| 2841 inefficient), and of course are not portable to non-Emacs applications. | |
| 2842 The incompatibility can be very annoying. On the other hand, they | |
| 2843 require no special platform support or external libraries, so if you can | |
| 2844 display the characters, Mule can input them for you and you can edit, | |
| 2845 anywhere. | |
| 2846 | |
| 2847 @emph{Generic platform support} is currently limited to the X Input | |
| 2848 Method (XIM) framework, although support for MSIME (for MS Windows) is | |
| 2849 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework) | |
| 2850 support is extremely desirable. XIM is enabled at build time by use of | |
| 2851 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see | |
| 2852 your platform documentation. However, normally the input method you use | |
| 2853 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment | |
| 2854 variables. | |
| 2855 | |
| 2856 Of course, input skills are portable across most applications. However, | |
| 2857 especially in modern GUI systems the habit of using bucky bits has | |
| 2858 fallen into sad disuse, and many XIM systems are poorly configured for | |
| 2859 use with Emacs. For example, the kinput2 input manager (a separate | |
| 2860 process providing an interface between Japanese dictionary servers such | |
| 2861 as Canna and Wnn, and the application) tends to gobble up keystrokes | |
| 2862 generating Meta characters. This means that to edit while using an XIM | |
| 2863 input method, you must toggle the input method off every time you want | |
| 2864 to use @kbd{M-f}. Your mileage may vary. | |
| 2865 | |
| 2866 @emph{Library interfaces} are most common for Japanese, although Wnn | |
| 2867 supports Chinese (traditional and simplified) and Korean. There are | |
| 2868 Chinese and Korean input servers available, but we do not know of any | |
| 2869 patches for XEmacs to use them directly. You can use them via | |
| 2870 IM-enabled terminals, by manipulating the terminal coding systems. We | |
| 2871 describe only the Japanese-oriented systems here. The advantage of | |
| 2872 these systems is that they are very powerful, and on platforms where | |
| 2873 they are available there is typically a wide range of applications that | |
| 2874 support them. Thus your input skills are portable across applications. | |
| 2875 | |
| 2876 Mule provides built-in interfaces to the following input methods: Wnn4, | |
| 2877 Wnn6, Canna, and SJ3. These can be configured at build time. There are | |
| 2878 patches available (no URL, sorry) to support the SKK server, as well. | |
| 2879 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna | |
| 2880 is specialized to Canna. | |
| 428 | 2881 |
| 2882 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto | |
| 1135 | 2883 University. It is a powerful and complex system. Wnn4 is free and Wnn6 |
| 2884 is not. Wnn uses grammatical hints and probability of word association, | |
| 2885 so in principle Wnn can be cleverer than other methods. | |
| 2886 | |
| 2887 Canna, made by NEC, supports only Japanese. It is a simple and powerful | |
| 2888 system. Canna uses only grammar, but its grammar and dictionary are | |
| 2889 quite sophisticated. So for standard modern Japanese, Canna seems | |
| 2890 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now | |
| 2891 there is a Microsoft Windows version). | |
| 2892 | |
| 2893 SJ3, by Sony, supports only Japanese. | |
| 428 | 2894 |
| 2895 Egg consists of following parts: | |
| 2896 | |
| 2897 @enumerate | |
| 2898 @item | |
| 2899 Input character Translation System (ITS) layer. | |
| 2900 It translates ASCII inputs to Kana/PinYin/Hangul characters. | |
| 2901 | |
| 2902 @item | |
| 2903 Kana/PinYin/Hangul to Kanji transfer layer. | |
| 1135 | 2904 The interface layer to network Kana-Kanji server (Wnn and Sj3). |
| 428 | 2905 @end enumerate |
| 2906 | |
| 1135 | 2907 These input methods are modal. They have a raw (alphabet) mode, a |
| 2908 phonetic input mode, and Kana-Kanji transfer mode. However there are | |
| 2909 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a | |
| 2910 mode-less input method running on Egg. For Canna, @samp{canna.el} has a | |
| 2911 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some | |
| 2912 boiled-egg-like utilities. | |
| 2913 | |
| 2914 Much of this information was provided by @email{morioka@@jaist.ac.jp, | |
| 2915 MORIOKA Tomohiko}. | |
| 428 | 2916 |
| 2537 | 2917 @node Q1.8.6, Q1.8.7, Q1.8.5, Introduction |
| 2918 @unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs? | |
| 428 | 2919 |
| 1135 | 2920 MULE has evolved rapidly over the last few years, and the original third |
| 2921 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite | |
| 2922 different implementations. The APIs also vary although recent versions | |
| 2923 of XEmacs have tended to converge to the GNU Emacs standard. | |
| 2924 | |
| 2925 MULE implementations are going to continue to evolve. Both GNU Emacs | |
| 2926 and XEmacs are working hard on Unicode support, which will involve new | |
| 2927 APIs and probably variations on old ones. For XEmacs 22, the old ISO | |
| 2928 2022-based system for recognizing encodings will be replaced by a much | |
| 2929 more flexible system, which should improve accuracy of automatic coding | |
| 2930 detections, but will also involve new APIs. | |
| 2931 | |
| 428 | 2932 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes: |
| 2933 | |
| 2934 @quotation | |
| 1135 | 2935 The application implementor must write separate code for these mule |
| 2936 variants. [Please don't hesitate to report these variants to us; they | |
| 2937 are not, strictly speaking, bugs, but they give third-party developers | |
| 2938 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.] | |
| 428 | 2939 |
| 2940 MULE and the next version of Emacs are similar but the symbols are very | |
| 2941 different---requiring separate code as well. | |
| 2942 | |
| 2943 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of | |
| 2944 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called | |
| 1135 | 2945 @code{emu} to provide a common interface. [There is an XEmacs package |
| 2946 of APEL which provides much more comprehensive coverage. Be careful, | |
| 2947 however; APEL has problems of its own. -- Ed.] | |
| 428 | 2948 |
| 2949 I have the following suggestions about dealing with mule variants: | |
| 2950 | |
| 2951 @itemize @bullet | |
| 2952 @item | |
| 2953 @code{(featurep 'mule)} @code{t} on all mule variants | |
| 2954 | |
| 2955 @item | |
| 2956 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version | |
| 2957 of Emacs will not have this symbol. | |
| 2958 | |
| 2959 @item | |
| 2960 MULE has a variable @code{mule-version}. Perhaps the next version of | |
| 2961 Emacs will have this variable as well. | |
| 2962 @end itemize | |
| 2963 | |
| 2964 Following is a sample to distinguish mule variants: | |
| 2965 | |
| 2966 @lisp | |
| 2967 (if (featurep 'mule) | |
| 2968 (cond ((boundp 'MULE) | |
| 2969 ;; for original Mule | |
| 2970 ) | |
| 440 | 2971 ((string-match "XEmacs" emacs-version) |
| 2972 ;; for XEmacs with Mule | |
| 2973 ) | |
| 2974 (t | |
| 2975 ;; for next version of Emacs | |
| 2976 )) | |
| 428 | 2977 ;; for old emacs variants |
| 2978 ) | |
| 2979 @end lisp | |
| 2980 @end quotation | |
| 2981 | |
| 2537 | 2982 @node Q1.8.7, Q1.8.8, Q1.8.6, Introduction |
| 2983 @unnumberedsubsec Q1.8.7: How about Cyrillic modes? | |
| 428 | 2984 |
| 2985 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes: | |
| 2986 | |
| 2987 @quotation | |
| 2988 There is a cyrillic mode in the file @file{mysetup.zip} in | |
| 2989 @iftex | |
| 2990 @* | |
| 2991 @end iftex | |
| 2992 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a | |
| 2993 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el} | |
| 2994 which can be obtained from | |
| 2995 @end quotation | |
| 2996 | |
| 871 | 2997 @uref{http://www.math.uga.edu/~valery/russian.el}. |
| 428 | 2998 |
| 2999 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes: | |
| 3000 | |
| 3001 @quotation | |
| 3002 There is another cyrillic mode for both GNU Emacs and XEmacs by | |
| 3003 @email{manin@@camelot.mssm.edu, Dmitrii | |
| 3004 (Mitya) Manin} at | |
| 3005 @iftex | |
| 3006 | |
| 3007 @end iftex | |
| 3008 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}. | |
| 3009 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead. | |
| 3010 @c Changed to russian host instead | |
| 3011 @end quotation | |
| 3012 | |
| 3013 @email{rebecca.ore@@op.net, Rebecca Ore} writes: | |
| 3014 | |
| 3015 @quotation | |
| 3016 The fullest resource I found on Russian language use (in and out of | |
| 661 | 3017 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html} |
| 428 | 3018 @end quotation |
| 3019 | |
| 2537 | 3020 @node Q1.8.8, Q1.8.9, Q1.8.7, Introduction |
| 3021 @unnumberedsubsec Q1.8.8: Does XEmacs support Unicode? | |
| 2417 | 3022 |
| 3023 To get Unicode support, you need a Mule-enabled XEmacs. | |
| 3024 | |
| 3025 21.5 has internal support for Unicode and supports it fully, although we | |
| 3026 don't yet use it as the internal encoding. | |
| 3027 | |
| 3028 21.4 supports Unicode partially -- as an external encoding for files, | |
| 2537 | 3029 processes, and terminals, but without font support. @xref{Q1.8.9, How |
| 2417 | 3030 does XEmacs display Unicode?}. To get Unicode support in 21.4, |
| 3031 install Mule-UCS from packages in the usual way, and put | |
| 745 | 3032 |
| 1616 | 3033 @example |
| 745 | 3034 (require 'un-define) |
| 3035 (set-coding-priority-list '(utf-8)) | |
| 1616 | 3036 (set-coding-category-system 'utf-8 'utf-8) |
| 3037 @end example | |
| 3038 | |
| 3039 in your init file to enable the UTF-8 coding system. You may wish to | |
| 3040 view the documentation of @code{set-coding-priority-list} if you find | |
| 3041 that files that are not UTF-8 are being mis-recognized as UTF-8. | |
| 745 | 3042 |
| 2417 | 3043 Install standard national fonts (not Unicode fonts) for all character |
| 2537 | 3044 sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}. |
| 745 | 3045 |
| 3046 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not | |
| 3047 support 31-bit forms of Unicode (UTF-32 or UCS-4). | |
| 3048 | |
| 2537 | 3049 @node Q1.8.9, , Q1.8.8, Introduction |
| 3050 @unnumberedsubsec Q1.8.9: How does XEmacs display Unicode? | |
| 745 | 3051 |
| 3052 Mule doesn't have a Unicode charset internally, so there's nothing to | |
| 3053 bind a Unicode registry to. It would not be straightforward to create, | |
| 3054 either, because Unicode is not ISO 2022-compatible. You'd have to | |
| 3055 translate it to multiple 96x96 pages. | |
| 3056 | |
| 3057 This means that Mule-UCS uses ordinary national fonts for display. This | |
| 3058 is not really a problem, except for those languages that use the Unified | |
| 3059 Han characters. The problem here is that Mule-UCS maps from Unicode | |
| 3060 code points to national character sets in a deterministic way. By | |
| 3061 default, this means that Japanese fonts are tried first, then Chinese, | |
| 3062 then Korean. To change the priority ordering, use the command | |
| 3063 `un-define-change-charset-order'. | |
| 3064 | |
| 3065 It also means you can't use Unicode fonts directly, at least not without | |
| 3066 extreme hackery. You can run -nw with (set-terminal-coding-system | |
| 3067 'utf-8) if you really want a Unicode font for some reason. | |
| 3068 | |
| 3069 Real Unicode support will be introduced in XEmacs 22.0. | |
| 3070 | |
| 2459 | 3071 @node Installation, Editing, Introduction, Top |
| 2417 | 3072 @unnumbered 2 Installation and Troubleshooting |
| 428 | 3073 |
| 3074 This is part 2 of the XEmacs Frequently Asked Questions list. This | |
| 2417 | 3075 section is devoted to Installation, Maintenance and Troubleshooting. |
| 428 | 3076 |
| 3077 @menu | |
| 2559 | 3078 2.0: Installation (General) |
| 3079 * Q2.0.1:: How do I build and install XEmacs? | |
| 3080 * Q2.0.2:: Where do I find external libraries? | |
| 3081 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files? | |
| 3082 * Q2.0.4:: Running XEmacs without installing | |
| 3083 * Q2.0.5:: XEmacs is too big | |
| 3084 | |
| 3085 2.1: Package Installation | |
| 3086 * Q2.1.1:: How do I install the packages? | |
| 3087 * Q2.1.2:: Can I install the packages individually? | |
| 3088 * Q2.1.3:: Can I install the packages automatically? | |
| 3089 * Q2.1.4:: Can I upgrade or remove packages? | |
| 3090 * Q2.1.5:: Which packages to install? | |
| 3091 * Q2.1.6:: Can you describe the package location process in more detail? | |
| 3092 * Q2.1.7:: EFS fails with "500 AUTH not understood" | |
| 3093 | |
| 3094 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) | |
| 3095 * Q2.2.1:: Libraries in non-standard locations | |
| 3096 * Q2.2.2:: Why can't I strip XEmacs? | |
| 3404 | 3097 * Q2.2.3:: X11/bitmaps/gray (or other X11-related file) not found. |
| 2559 | 3098 |
| 3099 2.3: Windows Installation (Windows, Cygwin, MinGW) | |
| 3100 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows? | |
| 3101 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs? | |
| 3102 * Q2.3.3:: How do I compile the native port? | |
| 3103 * Q2.3.4:: What do I need for Cygwin? | |
| 3104 * Q2.3.5:: How do I compile under Cygwin? | |
| 3105 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 3106 * Q2.3.7:: How do I compile with X support? | |
| 3107 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 3108 | |
| 3109 2.4: General Troubleshooting | |
| 3110 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running? | |
| 3111 * Q2.4.2:: Help! XEmacs just crashed on me! | |
| 3112 * Q2.4.3:: XEmacs crashes and I compiled it myself. | |
| 3113 * Q2.4.4:: How to debug an XEmacs problem with a debugger | |
| 3114 * Q2.4.5:: I get a cryptic error message when trying to do something. | |
| 3115 * Q2.4.6:: XEmacs hangs when I try to do something. | |
| 3116 * Q2.4.7:: I get an error message when XEmacs is running in batch mode. | |
| 3117 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 3118 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken? | |
| 3119 * Q2.4.10:: How do I debug process-related problems? | |
| 3120 * Q2.4.11:: XEmacs is outputting lots of X errors. | |
| 3121 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more! | |
| 3122 | |
| 3123 2.5: Startup-Related Problems | |
| 3124 * Q2.5.1:: XEmacs cannot connect to my X Terminal! | |
| 3125 * Q2.5.2:: Startup problems related to paths or package locations. | |
| 3126 * Q2.5.3:: XEmacs won't start without network. | |
| 3127 * Q2.5.4:: Startup warnings about deducing proper fonts? | |
| 3128 * Q2.5.5:: Warnings from incorrect key modifiers. | |
| 3129 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? | |
| 428 | 3130 @end menu |
| 3131 | |
| 2559 | 3132 @unnumberedsec 2.0: Installation (General) |
| 2417 | 3133 |
| 428 | 3134 @node Q2.0.1, Q2.0.2, Installation, Installation |
| 2559 | 3135 @unnumberedsubsec Q2.0.1: How do I build and install XEmacs? |
| 3136 | |
| 3137 See the file @file{etc/NEWS} for information on new features and other | |
| 3138 user-visible changes since the last version of XEmacs. | |
| 3139 | |
| 3140 The file @file{INSTALL} in the top-level directory says how to bring | |
| 3141 up XEmacs on Unix and Cygwin, once you have loaded the entire subtree | |
| 3142 of this directory. | |
| 3143 | |
| 3144 See the file @file{nt/README} for instructions on building XEmacs for | |
| 3145 Microsoft Windows. | |
| 3146 | |
| 3147 @xref{Q2.1.1}, for the installation of (essential) add on packages. | |
| 2417 | 3148 |
| 3149 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation | |
| 2559 | 3150 @unnumberedsubsec Q2.0.2: Where do I find external libraries? |
| 2417 | 3151 |
| 2459 | 3152 All external libraries used by XEmacs can be found on the XEmacs web |
| 2417 | 3153 site |
| 3154 @iftex | |
| 3155 @* | |
| 3156 @end iftex | |
| 2459 | 3157 @uref{http://www.xemacs.org/Download/optLibs.html}. |
| 2417 | 3158 |
| 3159 The library versions available here are known to work with XEmacs. | |
| 3160 (Newer versions will probably work as well but we can't guarantee it.) | |
| 3161 We try to keep the libraries up-to-date but may not always succeed. | |
| 2459 | 3162 Check the above page for the canonical locations of the external libraries, |
| 3163 allowing you to download the latest, bleeding-edge versions. | |
| 2417 | 3164 |
| 2559 | 3165 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation |
| 3166 @unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files? | |
| 2417 | 3167 |
| 3168 You can specify what paths to use by using a number of different flags | |
| 3169 when running configure. See the section MAKE VARIABLES in the top-level | |
| 3170 file INSTALL in the XEmacs distribution for a listing of those flags. | |
| 3171 | |
| 3172 Most of the time, however, the simplest fix is: @strong{do not} specify | |
| 3173 paths as you might for GNU Emacs. XEmacs can generally determine the | |
| 3174 necessary paths dynamically at run time. The only path that generally | |
| 3175 needs to be specified is the root directory to install into. That can | |
| 3176 be specified by passing the @code{--prefix} flag to configure. For a | |
| 3177 description of the XEmacs install tree, please consult the @file{NEWS} | |
| 3178 file. | |
| 3179 | |
| 2559 | 3180 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation |
| 3181 @unnumberedsubsec Q2.0.4: Running XEmacs without installing | |
| 442 | 3182 |
| 3183 How can I just try XEmacs without installing it? | |
| 428 | 3184 |
| 3185 XEmacs will run in place without requiring installation and copying of | |
| 3186 the Lisp directories, and without having to specify a special build-time | |
| 3187 flag. It's the copying of the Lisp directories that requires so much | |
| 3188 space. XEmacs is largely written in Lisp. | |
| 3189 | |
| 3190 A good method is to make a shell alias for xemacs: | |
| 3191 | |
| 3192 @example | |
| 2459 | 3193 alias xemacs=/src/xemacs-21.5/src/xemacs |
| 428 | 3194 @end example |
| 3195 | |
| 3196 (You will obviously use whatever directory you downloaded the source | |
| 2459 | 3197 tree to instead of @file{/src/xemacs-21.5}). |
| 428 | 3198 |
| 3199 This will let you run XEmacs without massive copying. | |
| 3200 | |
| 2559 | 3201 @node Q2.0.5, Q2.1.1, Q2.0.4, Installation |
| 3202 @unnumberedsubsec Q2.0.5: XEmacs is too big | |
| 428 | 3203 |
| 442 | 3204 The space required by the installation directories can be |
| 428 | 3205 reduced dramatically if desired. Gzip all the .el files. Remove all |
| 442 | 3206 the packages you'll never want to use. Remove the TexInfo manuals. |
| 428 | 3207 Remove the Info (and use just hardcopy versions of the manual). Remove |
| 3208 most of the stuff in etc. Remove or gzip all the source code. Gzip or | |
| 3209 remove the C source code. Configure it so that copies are not made of | |
| 1138 | 3210 the support lisp. |
| 428 | 3211 |
| 3212 These are all Emacs Lisp source code and bytecompiled object code. You | |
| 3213 may safely gzip everything named *.el here. You may remove any package | |
| 3214 you don't use. @emph{Nothing bad will happen if you delete a package | |
| 3215 that you do not use}. You must be sure you do not use it though, so be | |
| 3216 conservative at first. | |
| 3217 | |
| 1648 | 3218 Any package with the possible exceptions of xemacs-base, and EFS are |
| 3219 candidates for removal. Ask yourself, @emph{Do I ever want to use this | |
| 3220 package?} If the answer is no, then it is a candidate for removal. | |
| 428 | 3221 |
| 3222 First, gzip all the .el files. Then go about package by package and | |
| 3223 start gzipping the .elc files. Then run XEmacs and do whatever it is | |
| 1648 | 3224 you normally do. If nothing bad happens, then remove the package. You |
| 3225 can remove a package via the PUI interface | |
| 3226 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages | |
| 3227 you wish to delete, and then @kbd{x} to delete them. | |
| 3228 | |
| 3229 Another method is to do @code{M-x package-get-delete-package}. | |
| 428 | 3230 |
| 2559 | 3231 @unnumberedsec 2.1: Package Installation |
| 3232 | |
| 3233 @node Q2.1.1, Q2.1.2, Q2.0.5, Installation | |
| 3234 @unnumberedsubsec Q2.1.1: How do I install the packages? | |
| 3235 | |
| 3236 There are three ways to install the packages. | |
| 3237 | |
| 3238 @enumerate | |
| 3239 @item | |
| 3240 Manually, all at once, using the 'Sumo Tarball'. | |
| 3241 @item | |
| 3242 Manually, using individual package tarballs. | |
| 3243 @item | |
| 3244 Automatically, using the package tools from XEmacs. | |
| 3245 @end enumerate | |
| 3246 | |
| 3247 If you don't want to mess with the packages, it is easiest to just | |
| 3248 grab them manually, all at once. (For the other two ways, | |
| 3249 @xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file | |
| 3250 | |
| 3251 @file{xemacs-sumo.tar.gz} | |
| 3252 | |
| 3253 For an XEmacs compiled with Mule you also need | |
| 3254 | |
| 3255 @file{xemacs-mule-sumo.tar.gz} | |
| 3256 | |
| 3257 These are in the @file{packages} directory on your XEmacs mirror | |
| 3258 archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its | |
| 3259 mirrors. N.B. They are called 'Sumo Tarballs' for good reason. They | |
| 3260 are currently about 19MB and 4.5MB (gzipped) respectively. | |
| 3261 | |
| 3262 Install them on Unix and Mac OS X using the shell/Terminal command | |
| 3263 | |
| 3264 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -} | |
| 3265 | |
| 3266 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to | |
| 3267 @file{configure}, and defaults to @file{/usr/local}. | |
| 3268 | |
| 3269 If you have GNU tar you can use: | |
| 3270 | |
| 3271 @code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>} | |
| 3272 | |
| 3018 | 3273 If you have the packages somewhere nonstandard and don't want to bother |
| 3274 with @samp{$prefix} (for example, you're a developer and are compiling | |
| 3275 the packages yourself, and want your own private copy of everything), | |
| 3276 you can also directly specify this using @file{configure}. To do this | |
| 3179 | 3277 with 21.5 and above use the @samp{--with-late-packages} parameter to |
| 3018 | 3278 specify the directory under which you untarred the above tarballs. |
| 3279 Under 21.4 and previous you need to use @samp{--package-path}. Using | |
| 3280 these options looks something like this: | |
| 2559 | 3281 |
| 3282 @example | |
| 3283 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ... | |
| 3284 @end example | |
| 3285 | |
| 3286 Under Windows, you need to place the above @samp{tar.gz} files in the | |
| 3287 directory specified using the @samp{PACKAGE_PREFIX} value in | |
| 3288 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}. | |
| 3289 (To untar a @samp{tar.gz} file you will need to use a utility such as | |
| 3290 WinZip, unless you have Cygwin or a similar environment installed, in | |
| 3291 which case the above Unix shell command should work fine.) If you want | |
| 3292 the packages somewhere else, just change @samp{PACKAGE_PREFIX}. | |
| 3293 | |
| 3294 Note that XEmacs finds the packages automatically anywhere underneath | |
| 3295 the directory tree where it expects to find the packages. All you | |
| 3296 need to do is put stuff there; you don't need to run any program to | |
| 4311 | 3297 tell XEmacs to find the packages, or do anything of that sort. |
| 2559 | 3298 |
| 3299 However, XEmacs will only notice newly installed packages when it | |
| 3300 starts up, so you will have to restart if you are already running | |
| 3301 XEmacs. | |
| 3302 | |
| 3303 For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's | |
| 3304 Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}. | |
| 3305 | |
| 3306 As the Sumo tarballs are not regenerated as often as the individual | |
| 3307 packages, it is recommended that you use the automatic package tools | |
| 3308 afterwards to pick up any recent updates. | |
| 3309 | |
| 3310 @emph{NOTE}: For detailed information about how the package | |
| 3311 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp | |
| 3312 Reference Manual}. | |
| 3313 | |
| 3314 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation | |
| 3315 @unnumberedsubsec Q2.1.2: Can I install the packages individually? | |
| 3316 | |
| 3317 Yes, you can download individual packages from the FTP site (@pxref{Q2.1.1}). Since packages are automatically noticed at startup, you just have to put them in the right place. | |
| 3318 | |
| 3319 Note: If you are upgrading packages already installed, it's best to | |
| 3320 remove the old package first (@pxref{Q2.1.4}). | |
| 3321 | |
| 3322 For example if we are installing the @samp{xemacs-base} | |
| 3323 package (version 1.48): | |
| 3324 | |
| 3325 @example | |
| 3326 mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet | |
| 3327 cd $prefix/lib/xemacs/xemacs-packages RET | |
| 3328 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET | |
| 3329 @end example | |
| 3330 | |
| 3331 Or if you have GNU tar, the last step can be: | |
| 3332 | |
| 3333 @example | |
| 3334 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET | |
| 3335 @end example | |
| 3336 | |
| 3337 For MULE related packages, it is best to untar into the @samp{mule-packages} | |
| 3338 hierarchy, i.e. for the @samp{mule-base} package, version 1.37: | |
| 3339 | |
| 3340 @example | |
| 3341 mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet | |
| 3342 cd $prefix/lib/xemacs/mule-packages RET | |
| 3343 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET | |
| 3344 @end example | |
| 3345 | |
| 3346 Or if you have GNU tar, the last step can be: | |
| 3347 | |
| 3348 @example | |
| 3349 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET | |
| 3350 @end example | |
| 3351 | |
| 3352 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation | |
| 3353 @unnumberedsubsec Q2.1.3: Can I install the packages automatically? | |
| 3354 | |
| 3355 XEmacs comes with some tools to make the periodic updating and | |
| 3356 installing easier. It will notice if new packages or versions are | |
| 3357 available and will fetch them from the FTP site. | |
| 3358 | |
| 3359 Unfortunately this requires that a few packages are already in place. | |
| 3360 You will have to install them by hand as above or use a SUMO tarball. | |
| 3361 This requirement will hopefully go away in the future. The packages | |
| 3362 you need are: | |
| 3363 | |
| 3364 @example | |
| 3365 efs - To fetch the files from the FTP site or mirrors. | |
| 3366 xemacs-base - Needed by efs. | |
| 3367 @end example | |
| 3368 | |
| 3369 and optionally: | |
| 3370 | |
| 3371 @example | |
| 3372 mailcrypt - For PGP verification of the package-index file. | |
| 3373 @end example | |
| 3374 | |
| 3375 After installing these by hand, fire up XEmacs and follow these | |
| 3376 steps. | |
| 3377 | |
| 3378 @enumerate | |
| 3379 @item | |
| 3380 Choose a download site. | |
| 3381 @itemize @bullet | |
| 3382 @item | |
| 3383 via menu: Tools -> Packages -> Set Download Site | |
| 3384 @item | |
| 3385 via keyb: M-x customize-variable RET package-get-remote RET | |
| 3386 (put in the details of remote host and directory) | |
| 3387 @end itemize | |
| 3388 | |
| 3389 If the package tarballs _AND_ the package-index file are in a | |
| 3390 local directory, you can: M-x pui-set-local-package-get-directory RET | |
| 3391 | |
| 3392 @item | |
| 3393 Obtain a list of packages and display the list in a buffer named | |
| 3394 "*Packages*". | |
| 3395 @itemize @bullet | |
| 3396 @item | |
| 3397 menu: Tools -> Packages -> List & Install | |
| 3398 @item | |
| 3399 keyb: M-x pui-list-packages RET | |
| 3400 @end itemize | |
| 3401 | |
| 3402 XEmacs will now connect to the remote site and download the | |
| 3403 latest package-index file. | |
| 3404 | |
| 3405 The resulting buffer, "*Packages*" has brief instructions at the | |
| 3406 end of the buffer. | |
| 3407 | |
| 3408 @item | |
| 3409 Choose the packages you wish to install. | |
| 3410 @itemize @bullet | |
| 3411 @item | |
| 3412 mouse: Click button 2 on the package name. | |
| 3413 @item | |
| 3414 keyb: RET on the package name | |
| 3415 @end itemize | |
| 3416 | |
| 3417 @item | |
| 3418 Make sure you have everything you need. | |
| 3419 @itemize @bullet | |
| 3420 @item | |
| 3421 menu: Packages -> Add Required | |
| 3422 @item | |
| 3423 keyb: r | |
| 3424 @end itemize | |
| 3425 | |
| 3426 XEmacs will now search for packages that are required by the | |
| 3427 ones that you have chosen to install and offer to select | |
| 3428 those packages also. | |
| 3429 | |
| 3430 For novices and gurus alike, this step can save your bacon. | |
| 3431 It's easy to forget to install a critical package. | |
| 3432 | |
| 3433 @item | |
| 3434 Download and install the packages. | |
| 3435 @itemize @bullet | |
| 3436 @item | |
| 3437 menu: Packages -> Install/Remove Selected | |
| 3438 @item | |
| 3439 keyb: x | |
| 3440 @end itemize | |
| 3441 @end enumerate | |
| 3442 | |
| 3443 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation | |
| 3444 @unnumberedsubsec Q2.1.4: Can I upgrade or remove packages? | |
| 3445 | |
| 3446 As the exact files and their locations contained in a package may | |
| 3447 change it is recommended to remove a package first before installing a | |
| 4311 | 3448 new version. In order to facilitate removal each package contains a |
| 3449 pkginfo/MANIFEST.pkgname file which lists all the files belonging to | |
| 3450 the package. M-x package-admin-delete-binary-package RET can be used | |
| 3451 to remove a package using this file. | |
| 2559 | 3452 |
| 3453 Note that the interactive package tools included with XEmacs already do | |
| 3454 this for you. | |
| 3455 | |
| 3456 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation | |
| 3457 @unnumberedsubsec Q2.1.5: Which packages to install? | |
| 3458 | |
| 3459 Unless you are an advanced user, just install everything. | |
| 3460 | |
| 3461 If you really want to install only what's absolutely needed, a good | |
| 3462 minimal set of packages for XEmacs-latin1 would be | |
| 3463 | |
| 3464 @example | |
| 3465 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs, | |
| 3466 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes, | |
| 3467 text-modes, time, mailcrypt | |
| 3468 @end example | |
| 3469 | |
| 3470 If you are using the XEmacs package tools, don't forget to do: | |
| 3471 | |
| 3472 @example | |
| 3473 Packages -> Add Required | |
| 3474 @end example | |
| 3475 | |
| 3476 To make sure you have everything that the packages you have chosen to | |
| 3477 install need. | |
| 3478 | |
| 3479 @xref{Q1.7.2}, for a description of the various packages. | |
| 3480 | |
| 3481 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation | |
| 3482 @unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail? | |
| 3483 | |
| 3484 On startup XEmacs looks for packages in so-called package hierarchies. | |
| 3485 Normally, there are three system wide hierarchies, like this: | |
| 3486 | |
| 3487 @example | |
| 3488 $prefix/lib/xemacs/xemacs-packages/ | |
| 3489 Normal packages go here. | |
| 3490 | |
| 3491 $prefix/lib/xemacs/mule-packages/ | |
| 3492 Mule packages go here and are only searched by MULE-enabled XEmacsen. | |
| 3493 | |
| 3494 $prefix/lib/xemacs/site-packages/ | |
| 3495 Local and 3rd party packages go here. | |
| 3496 @end example | |
| 3497 | |
| 3498 This is what you get when you untar the SUMO tarballs under | |
| 3499 @file{$prefix/lib/xemacs}. | |
| 3500 | |
| 3501 @file{$prefix} is specified using the @samp{--prefix} parameter to | |
| 3502 @file{configure}, and defaults to @file{usr/local}. | |
| 3503 | |
| 3504 If the package path is not explicitly specified, XEmacs looks for the | |
| 3505 package directory @file{xemacs-packages} (and @file{mule-packages} and | |
| 3506 @file{site-packages}) first under @samp{~/.xemacs}, then for a sister | |
| 3507 directory @file{lib/xemacs-VERSION} of the directory in which the | |
| 3508 XEmacs executable is located, then for a sister directory | |
| 3509 @file{lib/xemacs}. The XEmacs executable (under Unix at least) is | |
| 3510 installed by default in @file{/usr/local/bin}; this explains why | |
| 3511 XEmacs in its default installation will find packages that you put | |
| 3512 under @file{/usr/local/lib/xemacs}. | |
| 3513 | |
| 3514 You can specify where exactly XEmacs looks for packages by using the | |
| 3179 | 3515 @samp{--with-user-packages} (an alias for @samp{--with-early-packages}) |
| 3516 or @samp{--with-system-packages} (an alias for | |
| 3517 @samp{--with-late-packages}) or @samp{--with-legacy-packages} | |
| 3518 (an alias for @samp{--with-last-packages}) | |
| 3519 parameters to @file{configure} (or the equivalent settings in | |
| 3520 @file{config.inc}, under Windows), or setting the | |
| 3521 @samp{EMACSEARLYPACKAGES}, @samp{EMACSLATEPACKAGES}, and | |
| 3522 @samp{EMACSLASTPACKAGES} environment variables (which have the same | |
| 3523 format as the configure options). @xref{Q2.1.1}. | |
| 2559 | 3524 |
| 3525 See @file{configure.usage} for more info about the format of these | |
| 3526 @file{configure} parameters. | |
| 3527 | |
| 3528 In addition to the system wide packages, each user can have his own | |
| 3529 packages installed under @file{~/.xemacs/}. If you want to install | |
| 3530 packages there using the interactive tools, you need to set | |
| 3531 @code{package-get-install-to-user-init-directory} to @code{t}. | |
| 3532 | |
| 3533 The site-packages hierarchy replaces the old @file{site-lisp} | |
| 3534 directory. XEmacs no longer looks into a @file{site-lisp} directly by | |
| 3535 default. A good place to put @file{site-start.el} would be in | |
| 3536 @file{$prefix/lib/xemacs/site-packages/lisp/}. | |
| 3537 | |
| 3538 @node Q2.1.7, Q2.2.1, Q2.1.6, Installation | |
| 3539 @unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW) | |
| 2417 | 3540 |
| 3541 A typical error: FTP Error: USER request failed; 500 AUTH not understood. | |
| 3542 | |
| 4311 | 3543 Thanks to Giacomo Boffi @email{giacomo.boffi@@polimi.it} who recommends |
| 2417 | 3544 on comp.emacs.xemacs: |
| 3545 | |
| 3546 tell your ftp client to not attempt AUTH authentication (or do not | |
| 3547 use FTP servers that don't understand AUTH) | |
| 3548 | |
| 3549 and notes that you need to add an element (often "-u") to | |
| 3550 `efs-ftp-program-args'. Use M-x customize-variable, and verify the | |
| 3551 needed flag with `man ftp' or other local documentation. | |
| 3552 | |
| 2559 | 3553 @unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) |
| 3554 | |
| 3555 @node Q2.2.1, Q2.2.2, Q2.1.7, Installation | |
| 3556 @unnumberedsubsec Q2.2.1: Libraries in non-standard locations | |
| 428 | 3557 |
| 2459 | 3558 If your libraries are in a non-standard location, you can specify the location |
| 3018 | 3559 using the following flags to @file{configure}. Under 21.4 or earlier: |
| 2459 | 3560 |
| 3561 @example | |
| 3562 --site-libraries=WHATEVER | |
| 3563 --site-includes=WHATEVER | |
| 3564 @end example | |
| 3565 | |
| 3018 | 3566 Under 21.5 or later: |
| 3567 | |
| 3568 @example | |
| 3569 --with-site-libraries=WHATEVER | |
| 3570 --with-site-includes=WHATEVER | |
| 3571 @end example | |
| 3572 | |
| 2459 | 3573 If you have multiple paths to specify, use the following syntax: |
| 428 | 3574 |
| 3575 @example | |
| 3576 --site-libraries='/path/one /path/two /path/etc' | |
| 3577 @end example | |
| 3578 | |
| 3018 | 3579 If the libraries and headers reside in the directories @samp{lib} and |
| 3580 @samp{include} of a common root (say @samp{/sw}) then both can be | |
| 3581 specified with a single option: | |
| 3582 | |
| 3583 @example | |
| 3584 --site-prefixes=WHATEVER | |
| 3585 @end example | |
| 3586 | |
| 3587 or for 21.5: | |
| 3588 | |
| 3589 @example | |
| 3590 --with-site-prefixes=WHATEVER | |
| 3591 @end example | |
| 3592 | |
| 3404 | 3593 @node Q2.2.2, Q2.2.3, Q2.2.1, Installation |
| 2559 | 3594 @unnumberedsubsec Q2.2.2: Why can't I strip XEmacs? |
| 428 | 3595 |
| 3596 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes: | |
| 3597 | |
| 3598 @quotation | |
| 3599 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The | |
| 3600 link gives you a bare-boned emacs (called temacs). temacs is then run, | |
| 3601 preloading some of the lisp files. The result is then dumped into a new | |
| 3602 executable, named xemacs, which will contain all of the preloaded lisp | |
| 3603 functions and data. | |
| 3604 | |
| 3605 Now, during the dump itself, the executable (code+data+symbols) is | |
| 3606 written on disk using a special unexec() function. This function is | |
| 3607 obviously heavily system dependent. And on some systems, it leads to an | |
| 3608 executable which, although valid, cannot be stripped without damage. If | |
| 3609 memory serves, this is especially the case for AIX binaries. On other | |
| 462 | 3610 architectures it might work OK. |
| 428 | 3611 |
| 3612 The Right Way to strip the emacs binary is to strip temacs prior to | |
| 3613 dumping xemacs. This will always work, although you can do that only if | |
| 3614 you install from sources (as temacs is @file{not} part of the binary | |
| 3615 kits). | |
| 3616 @end quotation | |
| 3617 | |
| 3618 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes: | |
| 3619 | |
| 3620 @quotation | |
| 3621 Here is the trick: | |
| 3622 | |
| 3623 @enumerate | |
| 3624 @item | |
| 3625 [ ./configure; make ] | |
| 3626 | |
| 3627 @item | |
| 3628 rm src/xemacs | |
| 3629 | |
| 3630 @item | |
| 3631 strip src/temacs | |
| 3632 | |
| 3633 @item | |
| 3634 make | |
| 3635 | |
| 3636 @item | |
| 3637 cp src/xemacs /usr/local/bin/xemacs | |
| 3638 | |
| 3639 @item | |
| 3640 cp lib-src/DOC-19.16-XEmacs | |
| 3641 @iftex | |
| 3642 \ @* | |
| 3643 @end iftex | |
| 3644 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout | |
| 3645 @end enumerate | |
| 3646 @end quotation | |
| 3647 | |
| 3404 | 3648 @node Q2.2.3, Q2.3.1, Q2.2.2, Installation |
| 3649 @unnumberedsubsec Q2.2.3: X11/bitmaps/gray (or other X11-related file) not found. | |
| 3650 | |
| 3651 The X11R6 distribution was monolithic, but the X11R7 distribution is | |
| 3652 much more modular. Many OS distributions omit these bitmaps (assuming | |
| 3653 nobody uses them, evidently). Your OS distribution should have a | |
| 3654 developer's package containing these files, probably with a name | |
| 3655 containing the string "bitmap". Known package names (you may need to | |
| 3656 add an extension such as .deb or .rpm) include x11/xbitmaps (Ubuntu) | |
| 3657 and xorg-x11-xbitmaps (Fedora Core 5). | |
| 3658 | |
| 2559 | 3659 @unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW) |
| 3660 | |
| 3404 | 3661 @node Q2.3.1, Q2.3.2, Q2.2.3, Installation |
| 2559 | 3662 @unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows? |
| 2417 | 3663 |
| 3664 XEmacs can be built in several ways in the MS Windows environment. | |
| 3665 | |
| 3666 The standard way is what we call the "native" port. It uses the Win32 | |
| 3667 API and has no connection with X whatsoever -- it does not require X | |
| 3668 libraries to build, nor does it require an X server to run. The native | |
| 3669 port is the most reliable version and provides the best graphical | |
| 3670 support. Almost all development is geared towards this version, and | |
| 3671 there is little reason not to use it. | |
| 3672 | |
| 3673 The second way to build is the Cygwin port. It takes advantage of | |
| 2537 | 3674 Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin |
| 2417 | 3675 and MinGW, and do I need them to run XEmacs?}, for more information. |
| 3676 | |
| 3677 A third way is the MinGW port. It uses the Cygwin environment to | |
| 2537 | 3678 build but does not require it at runtime. @xref{Q1.2.5, What are |
| 2417 | 3679 Cygwin and MinGW, and do I need them to run XEmacs?}, for more |
| 3680 information. | |
| 3681 | |
| 3682 Finally, you might also be able to build the non-Cygwin, non-MinGW "X" | |
| 3683 port. This was actually the first version of XEmacs that ran under MS | |
| 3684 Windows, and although the code is still in XEmacs, it's essentially | |
| 3685 orphaned and it's unlikely it will compile without a lot of work. If | |
| 3686 you want an MS Windows versin of XEmacs that supports X, use the Cygwin | |
| 3687 version. (The X support there is actively maintained, so that Windows | |
| 3688 developers can test the X support in XEmacs.) | |
| 3689 | |
| 2559 | 3690 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation |
| 3691 @unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs? | |
| 2417 | 3692 |
| 3693 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have | |
| 3694 some beta testers currently trying to compile with VC.NET, aka version | |
| 3695 7.0, but we can't yet report complete success.) For the Cygwin and | |
| 3696 MinGW versions, you need the Cygwin environment, which comes with GCC, | |
| 2537 | 3697 the compiler used for those versions. @xref{Q1.2.5, What are Cygwin |
| 2417 | 3698 and MinGW, and do I need them to run XEmacs?}, for more information on |
| 3699 Cygwin and MinGW. | |
| 3700 | |
| 2559 | 3701 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation |
| 3702 @unnumberedsubsec Q2.3.3: How do I compile the native port? | |
| 2417 | 3703 |
| 3704 Please read the file @file{nt/README} in the XEmacs distribution, which | |
| 3705 contains the full description. | |
| 3706 | |
| 2559 | 3707 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation |
| 3708 @unnumberedsubsec Q2.3.4: What do I need for Cygwin? | |
| 2417 | 3709 |
| 3710 You can find the Cygwin tools and compiler at: | |
| 3711 | |
| 3712 @uref{http://www.cygwin.com/} | |
| 3713 | |
| 3714 Click on the @samp{Install or update now!} link, which will download a | |
| 3715 file @file{setup.exe}, which you can use to download everything | |
| 3716 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is | |
| 3717 probably the best.) You should go ahead and install everything -- | |
| 3718 you'll get various ancillary libraries that XEmacs needs or likes, | |
| 3719 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you | |
| 3720 want to compile under X. | |
| 3721 | |
| 3722 If you want to compile without X, you will need the @file{xpm-nox} | |
| 3723 library, which must be specifically selected in the Cygwin netinstaller; | |
| 3724 it is not selected by default. The package has had various names. | |
| 3725 Currently it is called @file{cygXpm-noX4.dll}. | |
| 3726 | |
| 2559 | 3727 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation |
| 3728 @unnumberedsubsec Q2.3.5: How do I compile under Cygwin? | |
| 2417 | 3729 |
| 3730 Similar as on Unix; use the usual `configure' and `make' process. | |
| 3731 Some problems to watch out for: | |
| 3732 | |
| 3733 @itemize @bullet | |
| 3734 @item | |
| 3735 make sure HOME is set. This controls where you | |
| 3736 @file{init.el} file comes from; | |
| 3737 | |
| 3738 @item | |
| 3739 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work; | |
| 3740 | |
| 3741 @item | |
| 3742 picking up some other grep or other UNIX-like tools can kill configure; | |
| 3743 | |
| 3744 @item | |
| 3745 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive | |
| 3746 number; | |
| 3747 | |
| 3748 @item | |
| 3749 (Unconfirmed) The Cygwin version doesn't understand | |
| 3750 @file{//machine/path} type paths so you will need to manually mount a | |
| 3751 directory of this form under a unix style directory for a build to work | |
| 3752 on the directory; | |
| 3753 | |
| 3754 @item | |
| 3755 If you're building @strong{WITHOUT} X11, don't forget to change symlinks | |
| 3756 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to | |
| 3757 the non-X versions of these libraries. By default they point to the X | |
| 3758 versions. So: | |
| 3759 | |
| 3760 @example | |
| 3761 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a | |
| 3762 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a | |
| 3763 @end example | |
| 3764 | |
| 3765 (This advice may now be obsolete because of the availability of the | |
| 3766 cygXpm-noX4.dll package from Cygwin. Send confirmation to | |
| 3767 @email{faq@@xemacs.org}.) | |
| 3768 | |
| 3769 @item | |
| 3770 Other problems are listed in the @file{PROBLEMS} file, in the top-level | |
| 3771 directory of the XEmacs sources. | |
| 3772 | |
| 3773 @end itemize | |
| 3774 | |
| 3775 | |
| 2559 | 3776 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation |
| 3777 @unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 2417 | 3778 |
| 3779 Similar to the method for Unix. Things to remember: | |
| 3780 | |
| 3781 @itemize @bullet | |
| 3782 @item | |
| 3783 Specify the target host on the command line for @file{./configure}, e.g. | |
| 3784 @samp{./configure i586-pc-mingw32}. | |
| 3785 | |
| 3786 @item | |
| 3787 Be sure that your build directory is mounted such that it has the | |
| 3788 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows | |
| 3789 path (@file{c:\build\xemacs}). | |
| 3790 | |
| 3791 @item | |
| 3792 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng}, | |
| 3793 @file{compface}, etc. | |
| 3794 | |
| 3795 @item | |
| 3796 Specify the target location of the extra libs on the command line | |
| 3018 | 3797 to @file{configure}, e.g.for 21.4 or earlier |
| 3798 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32} and for | |
| 3799 21.5 or later | |
| 3800 @samp{./configure --with-site-prefixes=/build/libs i586-pc-mingw32}. | |
| 2417 | 3801 @end itemize |
| 3802 | |
| 2559 | 3803 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation |
| 3804 @unnumberedsubsec Q2.3.7: How do I compile with X support? | |
| 2417 | 3805 |
| 3806 To compile under Cygwin, all you need to do is install XFree86, which | |
| 3807 is available as part of the standard Cygwin installation. | |
| 3808 @uref{http://www.cygwin.com/}. Once installed, @file{configure} | |
| 3809 should automatically find the X libraries and compile with X support. | |
| 3810 | |
| 3811 As noted above, the non-Cygwin X support is basically orphaned, and | |
| 3812 probably won't work. But if it want to try, it's described in | |
| 3813 @file{nt/README} in some detail. Basically, you need to get X11 | |
| 2459 | 3814 libraries from @uref{http://ftp.x.org}, and compile them. If the |
| 2417 | 3815 precompiled versions are available somewhere, we don't know of it. |
| 3816 | |
| 2559 | 3817 @node Q2.3.8, Q2.4.1, Q2.3.7, Installation |
| 3818 @unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 1058 | 3819 |
| 3820 The Cygwin binary distributed with the netinstaller uses an external DLL | |
| 3821 to handle XPM images (such as toolbar buttons). You may get an error like | |
| 3822 | |
| 2559 | 3823 @example |
| 3824 This application has failed to start because cygXpm-noX4.dll was not found. | |
| 3825 Re-installing the application may fix this problem. | |
| 3826 @end example | |
| 1058 | 3827 |
| 3828 Andy Piper <andy@@xemacs.org> sez: | |
| 3829 | |
| 2559 | 3830 @example |
| 3831 cygXpm-noX4 is part of the cygwin distribution under libraries or | |
| 3832 graphics, but is not installed by default. You need to run the | |
| 3833 cygwin setup again and select this package. | |
| 3834 @end example | |
| 1058 | 3835 |
| 3836 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs | |
| 3837 distribution. | |
| 3838 | |
| 2559 | 3839 @unnumberedsec 2.4: General Troubleshooting |
| 3840 | |
| 3841 @node Q2.4.1, Q2.4.2, Q2.3.8, Installation | |
| 3842 @unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running? | |
| 3843 | |
| 3844 The file @file{PROBLEMS} contains information on many common problems that | |
| 3845 occur in building, installing and running XEmacs. | |
| 3846 | |
| 3847 Reports of bugs in XEmacs should be sent to | |
| 3848 @email{xemacs-beta@@xemacs.org}. You can also post to the newsgroup | |
| 3849 comp.emacs.xemacs (or equivalentlt, send to the mailing list | |
| 3850 @email{xemacs@@xemacs.org}), but it is less likely that the developers | |
| 3851 will see it in a timely fashion. @xref{Bugs,,, xemacs, the XEmacs | |
| 3852 User's Manual}, for more information on how to report bugs. | |
| 3853 @xref{Q1.4.2}, for more information on mailing lists relating to | |
| 3854 XEmacs. | |
| 3855 | |
| 3856 There are three ways to read the Bugs section. | |
| 3857 | |
| 3858 @enumerate | |
| 3859 @item | |
| 3860 In a printed copy of the XEmacs manual. | |
| 3861 | |
| 3862 @item | |
| 3863 With Info. First, start XEmacs. From the menu, select | |
| 3864 @samp{Help->Info (Online Docs)->Info Contents} to enter Info, then | |
| 3865 click on @samp{XEmacs}, then on @samp{Bugs}. Or, use the keyboard: do | |
| 3866 @kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs | |
| 3867 manual, then @kbd{m Bugs RET} to get to the section on bugs. Or use | |
| 3868 standalone Info in a like manner. (Standalone Info is part of the | |
| 3869 Texinfo distribution, not part of the XEmacs distribution.) | |
| 3870 | |
| 3871 @item | |
| 3872 By hand. Do | |
| 3873 @example | |
| 3874 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs," | |
| 3875 @end example | |
| 3876 @end enumerate | |
| 3877 | |
| 3878 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation | |
| 3879 @unnumberedsubsec Q2.4.2: Help! XEmacs just crashed on me! | |
| 428 | 3880 |
| 3881 First of all, don't panic. Whenever XEmacs crashes, it tries extremely | |
| 3882 hard to auto-save all of your files before dying. (The main time that | |
| 3883 this will not happen is if the machine physically lost power or if you | |
| 3884 killed the XEmacs process using @code{kill -9}). The next time you try | |
| 3885 to edit those files, you will be informed that a more recent auto-save | |
| 3886 file exists. You can use @kbd{M-x recover-file} to retrieve the | |
| 3887 auto-saved version of the file. | |
| 3888 | |
| 462 | 3889 You can use the command @kbd{M-x recover-session} after a crash to pick |
| 3890 up where you left off. | |
| 428 | 3891 |
| 3892 Now, XEmacs is not perfect, and there may occasionally be times, or | |
| 3893 particular sequences of actions, that cause it to crash. If you can | |
| 3894 come up with a reproducible way of doing this (or even if you have a | |
| 3895 pretty good memory of exactly what you were doing at the time), the | |
| 2417 | 3896 maintainers would be very interested in knowing about it. The best |
| 3897 way to report a bug is using @kbd{M-x report-emacs-bug} (or by | |
| 3898 selecting @samp{Send Bug Report...} from the Help menu). If that | |
| 3899 won't work (e.g. you can't get XEmacs working at all), send ordinary | |
| 3900 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include | |
| 3901 the output from the crash, especially including the Lisp backtrace, as | |
| 3902 well as the XEmacs configuration from @kbd{M-x describe-installation} | |
| 3903 (or equivalently, the file @file{Installation} in the top of the build | |
| 3904 tree). Note that the developers do @emph{not} usually follow | |
| 3905 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for | |
| 3906 general questions about XEmacs than bug reports. | |
| 428 | 3907 |
| 1183 | 3908 If at all possible, include a C stack backtrace of the core dump that |
| 2417 | 3909 was produced. This shows where exactly things went wrong, and makes |
| 3910 it much easier to diagnose problems. To do this under Unix and Mac OS | |
| 3911 X, you need to locate the core file (it's called @file{core}, and is | |
| 3912 usually sitting in the directory that you started XEmacs from, or your | |
| 3913 home directory if that other directory was not writable). Then, go to | |
| 3914 that directory and execute a command like: | |
| 428 | 3915 |
| 3916 @example | |
| 3917 gdb `which xemacs` core | |
| 3918 @end example | |
| 3919 | |
| 3920 and then issue the command @samp{where} to get the stack backtrace. You | |
| 3921 might have to use @code{dbx} or some similar debugger in place of | |
| 3922 @code{gdb}. If you don't have any such debugger available, complain to | |
| 3923 your system administrator. | |
| 3924 | |
| 2417 | 3925 It's possible that a core file didn't get produced or the stack trace |
| 3926 from gdb is garbage, in which case you're out of luck unless you can | |
| 3927 reproduce the bug. A nonexistent core file can happen in some | |
| 3928 circumstances on some operating systems, depending on what exactly | |
| 3929 triggered the crash. It's also possible, however, that your limits | |
| 3930 are set to turn them off. You may be able to reenable them using a | |
| 3931 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find | |
| 3932 out how your limits are set, use the command @samp{limit}.) However, if | |
| 3933 you didn't explicitly set your limits this way, go complain to your | |
| 3934 system administrator and tell him not to disable core files by | |
| 3935 default. | |
| 3936 | |
| 3937 A garbaged stack trace can happen for various reasons. Some versions | |
| 3938 of gdb are broken on certain operating systems and aren't able to read | |
| 3939 the core file. It's also possible that the stack got overwritten | |
| 3940 during the crash. A very simple reason, however, is that your version | |
| 3941 of XEmacs was compiled without debugging information or had the | |
| 3942 debugging information stripped. A compilation with optimization can | |
| 3943 also result in partly or completely garbaged stack trace. In such | |
| 3944 cases, you will need to recompile XEmacs with debugging information | |
| 2559 | 3945 and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem |
| 2417 | 3946 with a debugger}. Note also that core files currently don't work at |
| 3947 all under Cygwin, and the only way to get a backtrace is to run XEmacs | |
| 3948 from gdb. | |
| 3949 | |
| 3950 If you cannot get a backtrace from the core dump, but can reproduce | |
| 3951 the problem, try running XEmacs under gdb. The goal is to get clean C | |
| 3952 and Lisp backtraces and submit a bug report including full | |
| 3953 configuration information as described above, as this will greatly | |
| 3954 assist in the process of tracking down the bug. However, even partial | |
| 3955 information is better than none. The process of getting backtraces | |
| 2559 | 3956 from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs |
| 2417 | 3957 problem with a debugger}. |
| 428 | 3958 |
| 1183 | 3959 If you're under Microsoft Windows, you're out of luck unless you happen |
| 3960 to have a debugging aid installed on your system, for example Visual | |
| 3961 C++. In this case, the crash will result in a message giving you the | |
| 3962 option to enter a debugger (for example, by pressing @samp{Cancel}). Do | |
| 3963 this and locate the stack-trace window. (If your XEmacs was built | |
| 3964 without debugging information, the stack trace may not be very useful.) | |
| 3965 | |
| 428 | 3966 When making a problem report make sure that: |
| 3967 | |
| 3968 @enumerate | |
| 3969 @item | |
| 3970 Report @strong{all} of the information output by XEmacs during the | |
| 3971 crash. | |
| 3972 | |
| 3973 @item | |
| 2417 | 3974 You mention what O/S and Hardware you are running XEmacs on. |
| 428 | 3975 |
| 3976 @item | |
| 3977 What version of XEmacs you are running. | |
| 3978 | |
| 3979 @item | |
| 3980 What build options you are using. | |
| 3981 | |
| 3982 @item | |
| 2417 | 3983 If the problem is related to graphics and you are running Unix or Mac |
| 3984 OS X, we will also need to know what version of the X Window System | |
| 3985 you are running, and what window manager you are using. | |
| 1183 | 3986 |
| 3987 @item | |
| 3988 If the problem happened on a TTY, please include the terminal type. | |
| 2417 | 3989 |
| 3990 @item | |
| 3991 Try very hard to get both C and Lisp backtraces, as described above. | |
| 428 | 3992 @end enumerate |
| 3993 | |
| 1135 | 3994 Much of the information above is automatically generated by @kbd{M-x |
| 3995 report-emacs-bug}. Even more, and often useful, information can be | |
| 3996 generated by redirecting the output of @code{make} and @code{make check} | |
| 3997 to a file (@file{beta.err} is the default used by @code{build-report}), | |
| 3998 and executing @kbd{M-x build-report}. | |
| 3999 | |
| 2417 | 4000 |
| 2559 | 4001 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation |
| 4002 @unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself. | |
| 2417 | 4003 |
| 4004 There have been a variety of reports of crashes due to compilers with | |
| 4005 buggy optimizers. If you are compiling with optimization, consider | |
| 2559 | 4006 turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a |
| 2417 | 4007 debugger}) and recompiling. |
| 4008 | |
| 4009 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in | |
| 4010 the top-level source directory) to read what it says about your | |
| 4011 platform. | |
| 4012 | |
| 3018 | 4013 If you compiled XEmacs 21.4 or ealier using @samp{--use-union-type}, or |
| 4014 21.5 or later using @samp{--enable-union-type} (or in either case used | |
| 4015 the option @samp{USE_UNION_TYPE} in @file{config.inc} under Windows), | |
| 4016 try recompiling again without it. The union type has been known to | |
| 4017 trigger compiler errors in a number of cases. | |
| 2417 | 4018 |
| 2559 | 4019 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation |
| 4020 @unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger | |
| 428 | 4021 |
| 4022 If XEmacs does crash on you, one of the most productive things you can | |
| 4023 do to help get the bug fixed is to poke around a bit with the debugger. | |
| 4024 Here are some hints: | |
| 4025 | |
| 4026 @itemize @bullet | |
| 4027 @item | |
| 4028 First of all, if the crash is at all reproducible, consider very | |
| 563 | 4029 strongly recompiling your XEmacs with debugging symbols and with no |
| 4030 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} -- | |
| 4031 that's an "oh" followed by a zero), and with the configure options | |
| 3018 | 4032 @samp{--debug=yes} and @samp{--error-checking=all} |
| 4033 (@samp{--enable-debug=yes} and @samp{--enable-error-checking=all} on | |
| 4034 XEmacs 21.5 or later). This will make your XEmacs run somewhat slower, | |
| 4035 but you are a lot more likely to catch the problem earlier (closer to | |
| 4036 its source). It makes it a lot easier to determine what's going on with | |
| 4037 a debugger. The way to control the compiler flags is with the | |
| 4038 configuration option @samp{--cflags} (@samp{--with-cflags} in 21.5). If | |
| 4039 you have a recent version of 21.5, you should use | |
| 2417 | 4040 @samp{--without-optimization} in preference to directly setting |
| 4041 @samp{--cflags}. | |
| 1258 | 4042 |
| 4043 @item | |
| 4044 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie | |
| 4045 process), or it's inconvenient to run XEmacs again because XEmacs is | |
| 4046 already running or is running in batch mode as part of a bunch of | |
| 4047 scripts, you may be able to attach to the existing process with your | |
| 2417 | 4048 debugger. Under Unix and Mac OS X, the typical way to do this is to |
| 4049 first use some variant of the @samp{ps} command to figure out the | |
| 4050 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under | |
| 4051 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V, | |
| 4052 or @samp{ps -aW | grep xemacs} under Cygwin. Then run | |
| 4053 | |
| 4054 @example | |
| 4055 gdb /path/to/xemacs/xemacs #### | |
| 4056 @end example | |
| 4057 | |
| 4058 Where @code{####} is the process id of your XEmacs. (If you're not | |
| 4059 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs | |
| 4060 will stop and you can type @samp{where} in gdb to get a stack trace as | |
| 4061 usual. To get things moving again, you can just type @samp{quit} in | |
| 4062 gdb. It'll tell you the program is running and ask if you want to | |
| 4063 quit anyways. Say @samp{y} and it'll quit and have your emacs | |
| 4064 continue from where it was at. | |
| 4065 | |
| 4066 If you're running another debugger, a similar method may work, or you | |
| 4067 may have to run the debugger first and then use the @code{attach} | |
| 4068 command or something similar. | |
| 4069 | |
| 4070 Under Microsoft Windows, use the menu item @samp{Build->Start | |
| 4071 Debug->Attach to Process...} and select the XEmacs process from the list | |
| 4072 given. | |
| 1258 | 4073 |
| 4074 @item | |
| 4075 If you're able to run XEmacs under a debugger and reproduce the crash, | |
| 4076 here are some things you can do: | |
| 428 | 4077 |
| 4078 @item | |
| 4079 If XEmacs is hitting an assertion failure, put a breakpoint on | |
| 4080 @code{assert_failed()}. | |
| 4081 | |
| 4082 @item | |
| 4083 If XEmacs is hitting some weird Lisp error that's causing it to crash | |
| 4084 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is | |
| 2417 | 4085 declared static in @file{eval.c}. |
| 428 | 4086 |
| 4087 @item | |
| 563 | 4088 If XEmacs is outputting lots of X errors, put a breakpoint on |
| 2417 | 4089 @code{x_error_handler()}; that will tell you which call is causing |
| 4090 them. Note that the result may not be very useful by default because | |
| 4091 X Windows normally operates asynchronously: A bunch of commands are | |
| 4092 buffered up and then sent to the server all at once. This greatly | |
| 4093 improves performance over a network but means that an error may not be | |
| 4094 reported until the server receives the commands, which can be long | |
| 4095 after XEmacs made the erroneous calls. For best results, you need to | |
| 4096 make the X server synchronous before getting the backtrace. This can | |
| 4097 be done by starting XEmacs with the @samp{-sync} option or executing | |
| 4098 the Lisp code @code{(x-debug-mode t)}. | |
| 563 | 4099 |
| 4100 @item | |
| 428 | 4101 Internally, you will probably see lots of variables that hold objects of |
| 1258 | 4102 type @code{Lisp_Object}. These are references to Lisp objects. |
| 4103 Printing them out with the debugger probably won't be too | |
| 4104 useful---you'll likely just see a number. To decode them, do this: | |
| 428 | 4105 |
| 4106 @example | |
| 2417 | 4107 call debug_print (OBJECT) |
| 428 | 4108 @end example |
| 4109 | |
| 4110 where @var{OBJECT} is whatever you want to decode (it can be a variable, | |
| 1258 | 4111 a function call, etc.). This uses the Lisp printing routines to out a |
| 4112 readable representation on the TTY from which the xemacs process was | |
| 4113 invoked. | |
| 428 | 4114 |
| 2417 | 4115 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent |
| 4116 of @code{debug_print}. You can also try @code{dpa} if you can't see | |
| 4117 the output from @code{debug_print} (this will return a string containing | |
| 4118 the output), or use @code{debug_p3} if @code{debug_print} itself triggers | |
| 4119 a crash (this is a less comprehensive but super-safe way to print out | |
| 4120 a Lisp object). | |
| 4121 | |
| 428 | 4122 @item |
| 4123 If you want to get a Lisp backtrace showing the Lisp call | |
| 4124 stack, do this: | |
| 4125 | |
| 4126 @example | |
| 2417 | 4127 call debug_backtrace () |
| 428 | 4128 @end example |
| 4129 | |
| 2417 | 4130 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent |
| 4131 of @code{debug_backtrace}. | |
| 4132 | |
| 4133 @item | |
| 4134 Using @code{debug_print} and @code{debug_backtrace} has two | |
| 4135 disadvantages - they can only be used with a running (including hung | |
| 4136 or zombie) xemacs process, and they do not display the internal C | |
| 4137 structure of a Lisp Object. Even if all you've got is a core dump, | |
| 4138 all is not lost. | |
| 428 | 4139 |
| 4140 If you're using GDB, there are some macros in the file | |
| 438 | 4141 @file{src/.gdbinit} in the XEmacs source distribution that should make |
| 4142 it easier for you to decode Lisp objects. This file is automatically | |
| 4143 read by gdb if gdb is run in the directory where xemacs was built, and | |
| 4144 contains these useful macros to inspect the state of xemacs: | |
| 4145 | |
| 4146 @table @code | |
| 4147 @item pobj | |
| 4148 Usage: pobj lisp_object @* | |
| 4149 Print the internal C representation of a lisp object. | |
| 4150 | |
| 4151 @item xtype | |
| 4152 Usage: xtype lisp_object @* | |
| 4153 Print the Lisp type of a lisp object. | |
| 4154 | |
| 4155 @item lbt | |
| 4156 Usage: lbt @* | |
| 4157 Print the current Lisp stack trace. | |
| 1258 | 4158 Requires a running xemacs process. (It works by calling the db |
| 4159 routine described above.) | |
| 438 | 4160 |
| 4161 @item ldp | |
| 4162 Usage: ldp lisp_object @* | |
| 4163 Print a Lisp Object value using the Lisp printer. | |
| 1258 | 4164 Requires a running xemacs process. (It works by calling the dp |
| 4165 routine described above.) | |
| 438 | 4166 |
| 4167 @item run-temacs | |
| 4168 Usage: run-temacs @* | |
| 4169 Run temacs interactively, like xemacs. | |
| 4170 Use this with debugging tools (like purify) that cannot deal with dumping, | |
| 4171 or when temacs builds successfully, but xemacs does not. | |
| 4172 | |
| 4173 @item dump-temacs | |
| 4174 Usage: dump-temacs @* | |
| 4175 Run the dumping part of the build procedure. | |
| 4176 Use when debugging temacs, not xemacs! | |
| 4177 Use this when temacs builds successfully, but xemacs does not. | |
| 4178 | |
| 4179 @item check-xemacs | |
| 4180 Usage: check-xemacs @* | |
| 4181 Run the test suite. Equivalent to 'make check'. | |
| 4182 | |
| 4183 @item check-temacs | |
| 4184 Usage: check-temacs @* | |
| 4185 Run the test suite on temacs. Equivalent to 'make check-temacs'. | |
| 4186 Use this with debugging tools (like purify) that cannot deal with dumping, | |
| 4187 or when temacs builds successfully, but xemacs does not. | |
| 4188 @end table | |
| 428 | 4189 |
| 4190 If you are using Sun's @file{dbx} debugger, there is an equivalent file | |
| 438 | 4191 @file{src/.dbxrc}, which defines the same commands for dbx. |
| 428 | 4192 |
| 4193 @item | |
| 4194 If you're using a debugger to get a C stack backtrace and you're seeing | |
| 4195 stack traces with some of the innermost frames mangled, it may be due to | |
| 4196 dynamic linking. (This happens especially under Linux.) Consider | |
| 3018 | 4197 reconfiguring with @samp{--dynamic=no} (@samp{--with-dynamic=no} in 21.5 |
| 4198 or later). Also, sometimes (again under Linux), stack backtraces of | |
| 4199 core dumps will have the frame where the fatal signal occurred mangled; | |
| 4200 if you can obtain a stack trace while running the XEmacs process under a | |
| 4201 debugger, the stack trace should be clean. | |
| 428 | 4202 |
| 1183 | 4203 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so |
| 4204 version 1.8 if dynamic linking and debugging is a problem on Linux. | |
| 428 | 4205 |
| 4206 @item | |
| 4207 If you're using a debugger to get a C stack backtrace and you're | |
| 4208 getting a completely mangled and bogus stack trace, it's probably due to | |
| 4209 one of the following: | |
| 4210 | |
| 4211 @enumerate a | |
| 4212 @item | |
| 4213 Your executable has been stripped. Bad news. Tell your sysadmin not to | |
| 4214 do this---it doesn't accomplish anything except to save a bit of disk | |
| 4215 space, and makes debugging much much harder. | |
| 4216 | |
| 4217 @item | |
| 4218 Your stack is getting trashed. Debugging this is hard; you have to do a | |
| 4219 binary-search type of narrowing down where the crash occurs, until you | |
| 4220 figure out exactly which line is causing the problem. Of course, this | |
| 1258 | 4221 only works if the bug is highly reproducible. Also, in many cases if |
| 4222 you run XEmacs from the debugger, the debugger can protect the stack | |
| 4223 somewhat. However, if the stack is being smashed, it is typically the | |
| 4224 case that there is a wild pointer somewhere in the program, often quite | |
| 4225 far from where the crash occurs. | |
| 428 | 4226 |
| 4227 @item | |
| 4228 If your stack trace has exactly one frame in it, with address 0x0, this | |
| 4229 could simply mean that XEmacs attempted to execute code at that address, | |
| 4230 e.g. through jumping to a null function pointer. Unfortunately, under | |
| 4231 those circumstances, GDB under Linux doesn't know how to get a stack | |
| 1183 | 4232 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I |
| 428 | 4233 have no idea why GDB under Linux is so bogus. Complain to the GDB |
| 1183 | 4234 authors, or to comp.os.linux.development.system.) Again, you'll have to |
| 428 | 4235 use the narrowing-down process described above. |
| 4236 | |
| 4237 @item | |
| 462 | 4238 You will get a Lisp backtrace output when XEmacs crashes, so you'll have |
| 4239 something useful. | |
| 428 | 4240 |
| 4241 @end enumerate | |
| 4242 | |
| 4243 @item | |
| 4244 If you compile with the newer gcc variants gcc-2.8 or egcs, you will | |
| 438 | 4245 also need gdb 4.17 or above. Earlier releases of gdb can't handle the |
| 4246 debug information generated by the newer compilers. | |
| 428 | 4247 |
| 4248 @item | |
| 438 | 4249 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named |
| 4250 @file{src/gdbinit}. This had the disadvantage of not being sourced | |
| 4251 automatically by gdb, so you had to set that up yourself. | |
| 428 | 4252 |
| 1183 | 4253 @item |
| 4254 If you are running Microsoft Windows, the the file @file{nt/README} for | |
| 4255 further information about debugging XEmacs. | |
| 4256 | |
| 428 | 4257 @end itemize |
| 4258 | |
| 2559 | 4259 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation |
| 4260 @unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something. | |
| 2417 | 4261 |
| 4262 When I try to use some particular option of some particular package, I | |
| 4263 get a cryptic error message in the minibuffer. | |
| 4264 | |
| 4265 If the message went by too quickly, use @samp{Help->Recent Messages} | |
| 4266 from the menubar (or type @kbd{C-h l}) to see recent messages. | |
| 4267 | |
| 4268 If you can't figure out what's going on, select | |
| 4269 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or | |
| 4270 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make | |
| 4271 the error happen again. This will put in the debugger (you can get | |
| 4272 out of this and continue what you were doing before by typing @kbd{c}) | |
| 4273 and give you a backtrace that may be enlightening. If not, try | |
| 4274 reading through this FAQ; if that fails, you could try posting to | |
| 4275 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and | |
| 4276 someone may be able to help. If you can identify which XEmacs Lisp | |
| 4277 source file the error is coming from you can get a more detailed stack | |
| 4278 backtrace by doing the following: | |
| 428 | 4279 |
| 4280 @enumerate | |
| 4281 @item | |
| 2417 | 4282 Visit the .el file in an XEmacs buffer. |
| 4283 | |
| 4284 @item | |
| 4285 Issue the command @kbd{M-x eval-current-buffer}. | |
| 4286 | |
| 4287 @item | |
| 4288 Reproduce the error. | |
| 428 | 4289 @end enumerate |
| 4290 | |
| 2417 | 4291 For more information on debugging Lisp code, @xref{Debugging,,, |
| 4292 lispref, XEmacs Lisp Reference Manual}. | |
| 4293 | |
| 2559 | 4294 @node Q2.4.6, Q2.4.7, Q2.4.5, Installation |
| 4295 @unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something. | |
| 2417 | 4296 |
| 4297 XEmacs might just be slow; some operations take a long time. XEmacs | |
| 4298 may also be waiting on a response from the network, for example when | |
| 4299 you are trying to send mail. | |
| 4300 | |
| 4301 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for | |
| 4302 example, Lisp code explicitly disabled this by setting | |
| 4303 @code{inhibit-quit}), you can use the "critical quit" mechanism by | |
| 4304 typing @kbd{Control-Shift-G}. This should also pop you into the | |
| 4305 debugger and give you a backtrace, which can tell you where the | |
| 2559 | 4306 problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a |
| 2417 | 4307 debugger}). (Note that setting @code{debug-on-quit} or selecting |
| 4308 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular | |
| 4309 @kbd{C-g} to enter the debugger and give you a backtrace.) | |
| 4310 | |
| 4311 If you can't interrupt XEmacs this way, or for some reason XEmacs is | |
| 4312 not talking to the keyboard, you can try sending the @samp{SIGINT} | |
| 4313 signal using the @samp{kill} command. | |
| 4314 | |
| 4315 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that | |
| 4316 you can't interrupt it at all, you could try attaching to the process | |
| 2559 | 4317 and getting a C stack backtrace. @xref{Q2.4.4, How to debug an XEmacs |
| 2417 | 4318 problem with a debugger}. |
| 4319 | |
| 2559 | 4320 @node Q2.4.7, Q2.4.8, Q2.4.6, Installation |
| 4321 @unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode. | |
| 2417 | 4322 |
| 4323 Typically this happens when you are trying to compile some Elisp code. | |
| 4324 If you are doing this as part of XEmacs or the XEmacs packages, you | |
| 4325 should automatically get a backtrace, which can help you determine the | |
| 4326 source of the problem. In other cases, you can get equivalent results | |
| 4327 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq | |
| 4328 stack-trace-on-error t load-always-display-messages t | |
| 4329 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages | |
| 4330 t)} (this needs to be all on one line; to set an environment variable, | |
| 4331 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh}, | |
| 4332 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and | |
| 4333 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be | |
| 4334 executed at startup time. | |
| 4335 | |
| 4336 If the backtrace is not sufficiently useful in helping you diagnose | |
| 4337 the problem, you should consider using a debugger such as GDB. | |
| 2559 | 4338 @xref{Q2.4.4, How to debug an XEmacs problem with a debugger}. You |
| 2417 | 4339 probably want to set a breakpoint on @code{signal_1}. Since such |
| 4340 errors often occur during compiling, which is often triggered by a | |
| 4341 complex command run from a make suite, it may be easier to attach to | |
| 4342 the process once it's running. | |
| 4343 | |
| 3018 | 4344 Under Microsoft Windows (and perhaps other operating systems), there is |
| 4345 another useful trick you can do if you have configured with debugging | |
| 4346 support (configure option @samp{--debug} (@samp{--with-debug} in 21.5) | |
| 4347 or setting @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the | |
| 4348 environment variable @samp{XEMACSDEBUG} (as described above) to | |
| 4349 @samp{(setq debug-on-error t)}. Then, when an error occurs | |
| 4350 noninteractively, instead of trying to invoke the Lisp debugger (which | |
| 4351 obviously won't work), XEmacs will break out to a C debugger using | |
| 2417 | 4352 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs |
| 4353 @code{abort()}!!! (As well as and after executing INT 3 under MS | |
| 4354 Windows, which should invoke a debugger if it's active.) This is | |
| 4355 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to | |
| 4356 die anyway, and if no debugger is present, this will usefully dump | |
| 4357 core.) | |
| 4358 | |
| 2559 | 4359 @node Q2.4.8, Q2.4.9, Q2.4.7, Installation |
| 4360 @unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 2417 | 4361 |
| 4362 XEmacs has various facilities for debugging event handling. | |
| 4363 | |
| 4364 First, try setting the variable @code{debug-emacs-events} to non-zero. | |
| 4365 This will output various information showing which events are being | |
| 4366 received and how they are being translated. This may show you, for | |
| 4367 example, that a key command is getting intercepted using | |
| 4368 @code{key-translation-map}; this problem can otherwise be very tricky | |
| 4369 to debug. | |
| 4370 | |
| 4371 Under X, you can see exactly which events are being received from the | |
| 4372 window system by setting @code{x-debug-events} to non-zero. (The value | |
| 4373 @samp{1} gives you regular output, and @samp{2} gives you verbose | |
| 4374 output, including all parameters.) | |
| 4375 | |
| 4376 A similar facility exists under MS Windows: Set | |
| 4377 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives | |
| 4378 you regular output. The value @samp{2} gives you verbose output, | |
| 4379 including all parameters. The value @samp{3} gives you | |
| 4380 super-gorily-detailed output.) | |
| 4381 | |
| 2559 | 4382 @node Q2.4.9, Q2.4.10, Q2.4.8, Installation |
| 4383 @unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me. Is it broken? | |
| 2417 | 4384 |
| 4385 @kbd{C-g} does work for most people in most circumstances. If it | |
| 4386 doesn't, there are two possible explanations: | |
| 4387 | |
| 4388 @enumerate | |
| 4389 @item | |
| 4390 XEmacs is hung in a way that prevents @kbd{C-g} from working. This | |
| 4391 can happen when code is wrapped with a binding of @code{inhibit-quit} | |
| 4392 to @code{t}; you should still be able interrupt XEmacs using "critical | |
| 4393 quit". On the other hand, XEmacs may be seriously wedged. (If you're | |
| 4394 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.) | |
| 2559 | 4395 @xref{Q2.4.6, XEmacs hangs when I try to do something.}. |
| 2417 | 4396 |
| 4397 @item | |
| 4398 @kbd{C-g} is indeed broken on your system. To test, try executing | |
| 4399 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g} | |
| 4400 doesn't interrupt, then it's broken. This used to happen with systems | |
| 4401 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined. | |
| 4402 However, there may not be very many such systems nowadays. | |
| 4403 @end enumerate | |
| 4404 | |
| 2559 | 4405 @node Q2.4.10, Q2.4.11, Q2.4.9, Installation |
| 4406 @unnumberedsubsec Q2.4.10: How do I debug process-related problems? | |
| 2417 | 4407 |
| 4408 Under MS Windows, you can set the variable | |
| 4409 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get | |
| 4410 information on exactly what is getting passed to a process. This can | |
| 4411 be useful in determining problems with quoting. (Under Unix, a process | |
| 4412 receives each argument separately, but under MS Windows a single | |
| 4413 command line is received, and arguments with spaces or other special | |
| 4414 characters in them must be quoted. Unfortunately this means that each | |
| 4415 process, potentially at least, has its own quoting conventions, and | |
| 4416 the code to process quoting conventions in @file{cmd.exe}, the Visual | |
| 4417 C++ startup code and the like is baroque and poorly documented. | |
| 4418 XEmacs uses the variable | |
| 4419 @code{mswindows-construct-process-command-line-alist} to construct a | |
| 4420 command line from a list of arguments based on the command to be run, | |
| 4421 but it is (and cannot be) a perfect solution.) | |
| 4422 | |
| 2559 | 4423 @node Q2.4.11, Q2.4.12, Q2.4.10, Installation |
| 4424 @unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors. | |
| 563 | 4425 |
| 4426 If this is happening, we would very much like to know what's causing | |
| 2559 | 4427 them. To find this out, see @ref{Q2.4.4, How to debug an XEmacs |
| 2417 | 4428 problem with a debugger}. Try to get both a C and Lisp backtrace, and |
| 4429 send them along with the full error output to | |
| 4430 @email{xemacs-beta@@xemacs.org}. | |
| 4431 | |
| 2559 | 4432 @node Q2.4.12, Q2.5.1, Q2.4.11, Installation |
| 4433 @unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more! | |
| 2417 | 4434 |
| 4435 You have been used to doing `foo', but now when you invoke it (or | |
| 4436 click the toolbar button or select the menu item), nothing (or an | |
| 4437 error) happens. The simplest explanation is that you are missing a | |
| 4438 package that is essential to you. You can either track it down and | |
| 4439 install it (there is a list of packages and brief descriptions of | |
| 4440 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball' | |
| 2559 | 4441 (@pxref{Q2.1.2, How do I figure out which packages to install?}). |
| 2417 | 4442 |
| 4443 @c #### should xref to XEmacs manual here | |
| 4444 | |
| 2559 | 4445 @unnumberedsec 2.5: Startup-Related Problems |
| 4446 | |
| 4447 @node Q2.5.1, Q2.5.2, Q2.4.12, Installation | |
| 4448 @unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal! | |
| 2417 | 4449 |
| 4450 Help! I can not get XEmacs to display on my Envizex X-terminal! | |
| 4451 | |
| 4452 Try setting the @code{DISPLAY} variable using the numeric IP address of | |
| 4453 the host you are running XEmacs from. | |
| 4454 | |
| 2559 | 4455 @node Q2.5.2, Q2.5.3, Q2.5.1, Installation |
| 4456 @unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations. | |
| 4457 | |
| 4458 First of all, if XEmacs can't find the packages, check to make sure | |
| 4459 that you put the packages in the right place, or that you told XEmacs | |
| 4460 where to look for the packages when you compiled it. @xref{Q2.1.1}. | |
| 4461 | |
| 4462 If something is still going wrong, or you get a startup warning about | |
| 4463 not being able to deduce some paths, you can get detailed information | |
| 4464 on the path-searching process at startup by setting the environment | |
| 4465 variable @samp{EMACSDEBUGPATHS} to a non-null value. One thing to | |
| 4466 look for if you're having package problems is the value of | |
| 4467 @samp{configure-package-path}. This corresponds to what was compiled | |
| 4468 into XEmacs using the @samp{--package-prefix} or @samp{--package-path} | |
| 4469 parameter (@pxref{Q2.1.1}). If this has the value of @samp{nil}, | |
| 4470 this means that no value was compiled into XEmacs using these parameters. | |
| 4471 | |
| 4472 @node Q2.5.3, Q2.5.4, Q2.5.2, Installation | |
| 4473 @unnumberedsubsec Q2.5.3: XEmacs won't start without network. | |
| 434 | 4474 |
| 4475 If XEmacs starts when you're on the network, but fails when you're not | |
| 4476 on the network, you may be missing a "localhost" entry in your | |
| 4477 @file{/etc/hosts} file. The file should contain an entry like: | |
| 4478 | |
| 4479 @example | |
| 4480 127.0.0.1 localhost | |
| 4481 @end example | |
| 4482 | |
| 4483 Add that line, and XEmacs will be happy. | |
| 4484 | |
| 2559 | 4485 @node Q2.5.4, Q2.5.5, Q2.5.3, Installation |
| 4486 @unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts? | |
| 2417 | 4487 |
| 4488 How can I avoid the startup warnings about deducing proper fonts? | |
| 4489 | |
| 4490 This is highly dependent on your installation, but try with the | |
| 4491 following font as your base font for XEmacs and see what it does: | |
| 4492 | |
| 4493 @format | |
| 4494 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
| 4495 @end format | |
| 4496 | |
| 4497 More precisely, do the following in your resource file: | |
| 4498 | |
| 4499 @format | |
| 4500 Emacs.default.attributeFont: \ | |
| 4501 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
| 4502 @end format | |
| 4503 | |
| 4504 If you just don't want to see the @samp{*Warnings*} buffer at startup | |
| 4505 time, you can set this: | |
| 428 | 4506 |
| 4507 @lisp | |
| 2417 | 4508 (setq display-warning-minimum-level 'error) |
| 428 | 4509 @end lisp |
| 4510 | |
| 2417 | 4511 The buffer still exists; it just isn't in your face. |
| 4512 | |
| 2559 | 4513 @node Q2.5.5, Q2.5.6, Q2.5.4, Installation |
| 4514 @unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers. | |
| 2417 | 4515 |
| 4516 The following information comes from the @file{PROBLEMS} file that comes | |
| 4517 with XEmacs. | |
| 4518 | |
| 4519 If you're having troubles with HP/UX it is because HP/UX defines the | |
| 4520 modifiers wrong in X. Here is a shell script to fix the problem; be | |
| 4521 sure that it is run after VUE configures the X server. | |
| 428 | 4522 |
| 4523 @example | |
| 2417 | 4524 #! /bin/sh |
| 4525 xmodmap 2> /dev/null - << EOF | |
| 4526 keysym Alt_L = Meta_L | |
| 4527 keysym Alt_R = Meta_R | |
| 4528 EOF | |
| 4529 | |
| 4530 xmodmap - << EOF | |
| 4531 clear mod1 | |
| 4532 keysym Mode_switch = NoSymbol | |
| 4533 add mod1 = Meta_L | |
| 4534 keysym Meta_R = Mode_switch | |
| 4535 add mod2 = Mode_switch | |
| 4536 EOF | |
| 428 | 4537 @end example |
| 4538 | |
| 2559 | 4539 @node Q2.5.6, , Q2.5.5, Installation |
| 4540 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? | |
| 2417 | 4541 |
| 4542 Yes. | |
| 4543 | |
| 4544 The console was there because @file{temacs} (and in turn, @file{xemacs}) | |
| 4545 was a console application, and Windows typically creates a new | |
| 4546 console for a console process unless the creating process requests that | |
| 4547 one isn't created. This used to be fixed with @file{runemacs}, a small | |
| 4548 Windows application that existed merely to start @file{xemacs}, stating | |
| 4549 that it didn't want a console. | |
| 4550 | |
| 4551 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI" | |
| 4552 application. The explanation of what that means is included for | |
| 4553 educational value. | |
| 4554 | |
| 4555 When building an application to be run in a Win32 environment, you must | |
| 4556 state which sub-system it is to run in. Valid subsystems include | |
| 4557 "console" and "gui". The subsystem you use affects the run time | |
| 4558 libraries linked into your application, the start up function that is | |
| 4559 run before control is handed over to your application, the entry point | |
| 4560 to your program, and how Windows normally invokes your program. (Console | |
| 4561 programs automatically get a console created for them at startup if | |
| 4562 their stdin/stdout don't point anywhere useful, which is the case when | |
| 4563 run from the GUI. This is a stupid design, of course -- instead, the | |
| 4564 console should get created only when the first I/O actually occurs! | |
| 4565 GUI programs have an equally stupid design: When called from | |
| 4566 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to | |
| 4567 point nowhere useful, even though the command shell has its own | |
| 4568 stdin/stdout. It's as if someone who had learned a bit about stdio but | |
| 4569 had no actual knowledge of interprocess communication designed the | |
| 4570 scheme; unfortunately, the whole process-communication aspect of the | |
| 4571 Win32 API is equally badly designed.) For example, the entry point for a | |
| 4572 console app is "main" (which is what you'd expect for a C/C++ program), | |
| 4573 but the entry point for a "gui" app is "WinMain". This confuses and | |
| 4574 annoys a lot of programmers who've grown up on Unix systems, where the | |
| 4575 kernel doesn't really care whether your application is a gui program or | |
| 4576 not. | |
| 4577 | |
| 4578 For reasons not altogether clear, and are lost in the mists of time and | |
| 4579 tradition, XEmacs on Win32 started out as a console application, and | |
| 4580 therefore a console was automatically created for it. (It may have been | |
| 4581 made a console application partly because a console is needed in some | |
| 4582 circumstances, especially under Win95, to interrupt, terminate, or send | |
| 4583 signals to a child process, and because of the bogosity mentioned above | |
| 4584 with GUI programs and the standard command shell. Currently, XEmacs | |
| 4585 just creates and immediately hides a console when necessary, and | |
| 4586 works around the "no useful stdio" problem by creating its own console | |
| 4587 window as necessary to display messages in.) | |
| 4588 | |
| 2459 | 4589 @node Editing, Display, Installation, Top |
| 4590 @unnumbered 3 Editing Functions | |
| 2417 | 4591 |
| 4592 This is part 3 of the XEmacs Frequently Asked Questions list. This | |
| 2459 | 4593 section is devoted to the editing-related capabilities of XEmacs (the |
| 4594 keyboard, mouse, buffers, text selections, etc.) and how to customize | |
| 4595 them. | |
| 2417 | 4596 |
| 4597 @menu | |
| 4598 3.0: The Keyboard | |
| 2459 | 4599 * Q3.0.1:: How can I customize the keyboard? |
| 4600 * Q3.0.2:: How can I bind complex functions (or macros) to keys? | |
| 4601 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down? | |
| 4602 * Q3.0.4:: Globally binding @kbd{Delete}? | |
| 4603 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 4604 * Q3.0.6:: How can you type in special characters in XEmacs? | |
| 4605 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys? | |
| 4606 * Q3.0.8:: How do I map the arrow keys? | |
| 4607 * Q3.0.9:: HP Alt key as Meta. | |
| 4608 * Q3.0.10:: Why does edt emulation not work? | |
| 4609 * Q3.0.11:: How can I emulate VI and use it as my default mode? | |
| 2417 | 4610 |
| 4611 3.1: The Mouse | |
| 4612 * Q3.1.1:: How can I turn off Mouse pasting? | |
| 4613 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons? | |
| 4614 * Q3.1.3:: Clicking the left button does not do anything in buffer list. | |
| 4615 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3? | |
| 2459 | 4616 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is? |
| 4617 | |
| 4618 3.2: Buffers, Text Editing | |
| 4619 * Q3.2.1:: Can I have the end of the buffer delimited in some way? | |
| 4620 * Q3.2.2:: How do I insert today's date into a buffer? | |
| 4621 * Q3.2.3:: How do I get a single minibuffer frame? | |
| 4622 * Q3.2.4:: How can I enable auto-indent and/or Filladapt? | |
| 4623 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 4624 | |
| 4625 3.3: Text Selections | |
| 4626 * Q3.3.1:: How do I select a rectangular region? | |
| 4627 * Q3.3.2:: How can I turn off or change highlighted selections? | |
| 4628 * Q3.3.3:: How do I cause typing on an active region to remove it? | |
| 4629 * Q3.3.4:: Can I turn off the highlight during isearch? | |
| 4630 * Q3.3.5:: Why is killing so slow? | |
| 4631 * Q3.3.6:: Why does @kbd{M-w} take so long? | |
| 4632 | |
| 4633 3.4: Editing Source Code | |
| 4634 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode? | |
| 4635 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly? | |
| 2417 | 4636 @end menu |
| 4637 | |
| 4638 @unnumberedsec 3.0: The Keyboard | |
| 4639 | |
| 2459 | 4640 @node Q3.0.1, Q3.0.2, Editing, Editing |
| 4641 @unnumberedsubsec Q3.0.1: How can I customize the keyboard? | |
| 4642 | |
| 4643 #### Write me. | |
| 4644 | |
| 4645 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing | |
| 4646 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys? | |
| 428 | 4647 |
| 4648 As an example, say you want the @kbd{paste} key on a Sun keyboard to | |
| 4649 insert the current Primary X selection at point. You can accomplish this | |
| 4650 with: | |
| 4651 | |
| 4652 @lisp | |
| 4653 (define-key global-map [f18] 'x-insert-selection) | |
| 4654 @end lisp | |
| 4655 | |
| 4656 However, this only works if there is a current X selection (the | |
| 4657 selection will be highlighted). The functionality I like is for the | |
| 4658 @kbd{paste} key to insert the current X selection if there is one, | |
| 4659 otherwise insert the contents of the clipboard. To do this you need to | |
| 4660 pass arguments to @code{x-insert-selection}. This is done by wrapping | |
| 4661 the call in a 'lambda form: | |
| 4662 | |
| 4663 @lisp | |
| 4664 (global-set-key [f18] | |
| 4665 (lambda () (interactive) (x-insert-selection t nil))) | |
| 4666 @end lisp | |
| 4667 | |
| 4668 This binds the f18 key to a @dfn{generic} functional object. The | |
| 4669 interactive spec is required because only interactive functions can be | |
| 4670 bound to keys. | |
| 4671 | |
| 4672 For the FAQ example you could use: | |
| 4673 | |
| 4674 @lisp | |
| 4675 (global-set-key [(control ?.)] | |
| 4676 (lambda () (interactive) (scroll-up 1))) | |
| 440 | 4677 (global-set-key [(control ?;)] |
| 4678 (lambda () (interactive) (scroll-up -1))) | |
| 428 | 4679 @end lisp |
| 4680 | |
| 4681 This is fine if you only need a few functions within the lambda body. | |
| 2417 | 4682 If you're doing more it's cleaner to define a separate function. |
| 2459 | 4683 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and |
| 2417 | 4684 down?}. |
| 4685 | |
| 2459 | 4686 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing |
| 4687 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down? | |
| 428 | 4688 |
| 4689 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and | |
| 4690 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}: | |
| 4691 | |
| 4692 @lisp | |
| 4693 (defun scroll-up-one-line () | |
| 4694 (interactive) | |
| 4695 (scroll-up 1)) | |
| 4696 | |
| 4697 (defun scroll-down-one-line () | |
| 4698 (interactive) | |
| 4699 (scroll-down 1)) | |
| 4700 | |
| 4701 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-. | |
| 440 | 4702 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-; |
| 428 | 4703 @end lisp |
| 4704 | |
| 4705 The key point is that you can only bind simple functions to keys; you | |
| 2417 | 4706 can not bind a key to a function that you're also passing arguments |
| 2459 | 4707 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to |
| 2417 | 4708 keys?} for a better answer). |
| 4709 | |
| 2459 | 4710 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing |
| 4711 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}? | |
| 428 | 4712 |
| 4713 I cannot manage to globally bind my @kbd{Delete} key to something other | |
| 4714 than the default. How does one do this? | |
| 4715 | |
| 462 | 4716 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To |
| 4717 get around this, try the following: | |
| 4718 | |
| 428 | 4719 @lisp |
| 4720 (defun foo () | |
| 4721 (interactive) | |
| 4722 (message "You hit DELETE")) | |
| 4723 | |
| 462 | 4724 (define-key key-translation-map 'delete 'redirected-delete) |
| 4725 (global-set-key 'redirected-delete 'foo) | |
| 428 | 4726 @end lisp |
| 4727 | |
| 2459 | 4728 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing |
| 4729 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 428 | 4730 |
| 4731 The following works in GNU Emacs 19: | |
| 4732 | |
| 4733 @lisp | |
| 4734 (global-set-key [help] 'help-command);; Help | |
| 4735 @end lisp | |
| 4736 | |
| 462 | 4737 The following works in XEmacs with the addition of shift: |
| 428 | 4738 |
| 4739 @lisp | |
| 4740 (global-set-key [(shift help)] 'help-command);; Help | |
| 4741 @end lisp | |
| 4742 | |
| 4743 But it doesn't work alone. This is in the file @file{PROBLEMS} which | |
| 4744 should have come with your XEmacs installation: @emph{Emacs ignores the | |
| 4745 @kbd{help} key when running OLWM}. | |
| 4746 | |
| 4747 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate | |
| 4748 client using | |
| 4749 @iftex | |
| 4750 @* | |
| 4751 @end iftex | |
| 4752 @code{XSendEvent}. Allowing Emacs to react to synthetic | |
| 4753 events is a security hole, so this is turned off by default. You can | |
| 4754 enable it by setting the variable @code{x-allow-sendevents} to t. You | |
| 4755 can also cause fix this by telling OLWM to not grab the help key, with | |
| 4756 the null binding @code{OpenWindows.KeyboardCommand.Help:}. | |
| 4757 | |
| 2459 | 4758 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing |
| 4759 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs? | |
| 428 | 4760 One way is to use the package @code{x-compose}. Then you can use |
| 4761 sequences like @kbd{Compose " a} to get ä, etc. | |
| 4762 | |
| 462 | 4763 Another way is to use the @code{iso-insert} package. Then you can use |
| 4764 sequences like @kbd{C-x 8 " a} to get ä, etc. | |
| 428 | 4765 |
| 4766 @email{glynn@@sensei.co.uk, Glynn Clements} writes: | |
| 4767 | |
| 4768 @quotation | |
| 4769 It depends upon your X server. | |
| 4770 | |
| 4771 Generally, the simplest way is to define a key as Multi_key with | |
| 4772 xmodmap, e.g. | |
| 4773 @c hey, show some respect, willya -- there's xkeycaps, isn't there? -- | |
| 4774 @c chr ;) | |
| 4775 @example | |
| 440 | 4776 xmodmap -e 'keycode 0xff20 = Multi_key' |
| 428 | 4777 @end example |
| 4778 | |
| 4779 You will need to pick an appropriate keycode. Use xev to find out the | |
| 4780 keycodes for each key. | |
| 4781 | |
| 4782 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically | |
| 4783 define the right `Windows' key as Multi_key'.] | |
| 4784 | |
| 4785 Once you have Multi_key defined, you can use e.g. | |
| 4786 @example | |
| 440 | 4787 Multi a ' => á |
| 4788 Multi e " => ë | |
| 4789 Multi c , => ç | |
| 428 | 4790 @end example |
| 4791 | |
| 4792 etc. | |
| 4793 | |
| 4794 Also, recent versions of XFree86 define various AltGr-<key> | |
| 4795 combinations as dead keys, i.e. | |
| 4796 @example | |
| 440 | 4797 AltGr [ => dead_diaeresis |
| 4798 AltGr ] => dead_tilde | |
| 4799 AltGr ; => dead_acute | |
| 428 | 4800 @end example |
| 4801 etc. | |
| 4802 | |
| 4803 Running @samp{xmodmap -pk} will list all of the defined keysyms. | |
| 4804 @end quotation | |
| 4805 | |
| 1135 | 4806 For the related problem of @emph{displaying} non-ASCII characters in a |
| 2459 | 4807 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}. |
| 4808 | |
| 4809 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing | |
| 4810 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys? | |
| 428 | 4811 |
| 4812 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the | |
| 4813 effect of being able to press and release Shift and have the next | |
| 4814 character typed come out in upper case. This will affect all the other | |
| 4815 modifier keys like Control and Meta as well. | |
| 4816 | |
| 4817 @email{ben@@xemacs.org, Ben Wing} writes: | |
| 4818 | |
| 4819 @quotation | |
| 4820 One thing about the sticky modifiers is that if you move the mouse out | |
| 4821 of the frame and back in, it cancels all currently ``stuck'' modifiers. | |
| 4822 @end quotation | |
| 4823 | |
| 2459 | 4824 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing |
| 4825 @unnumberedsubsec Q3.0.8: How do I map the arrow keys? | |
| 428 | 4826 @c New |
| 4827 Say you want to map @kbd{C-@key{right}} to forward-word: | |
| 4828 | |
| 4829 @email{sds@@usa.net, Sam Steingold} writes: | |
| 4830 | |
| 4831 @quotation | |
| 4832 @lisp | |
| 4833 ; both XEmacs and Emacs | |
| 4834 (define-key global-map [(control right)] 'forward-word) | |
| 4835 @end lisp | |
| 4836 or | |
| 4837 @lisp | |
| 4838 ; Emacs only | |
| 4839 (define-key global-map [C-right] 'forward-word) | |
| 4840 @end lisp | |
| 4841 or | |
| 4842 @lisp | |
| 4843 ; ver > 20, both | |
| 4844 (define-key global-map (kbd "C-<right>") 'forward-word) | |
| 4845 @end lisp | |
| 4846 @end quotation | |
| 4847 | |
| 2459 | 4848 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing |
| 4849 @unnumberedsubsec Q3.0.9: HP Alt key as Meta. | |
| 2417 | 4850 |
| 4851 How can I make XEmacs recognize the Alt key of my HP workstation as a | |
| 4852 Meta key? | |
| 4853 | |
| 4854 Put the following line into a file and load it with xmodmap(1) before | |
| 4855 starting XEmacs: | |
| 428 | 4856 |
| 4857 @example | |
| 2417 | 4858 remove Mod1 = Mode_switch |
| 428 | 4859 @end example |
| 4860 | |
| 2459 | 4861 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing |
| 4862 @unnumberedsubsec Q3.0.10: Why does edt emulation not work? | |
| 2417 | 4863 |
| 4864 We don't know, but you can use tpu-edt emulation instead, which works | |
| 4865 fine and is a little fancier than the standard edt emulation. To do | |
| 4866 this, add the following line to your @file{init.el}: | |
| 4867 | |
| 4868 @lisp | |
| 4869 (tpu-edt) | |
| 4870 @end lisp | |
| 4871 | |
| 4872 If you don't want it to replace @kbd{C-h} with an edt-style help menu | |
| 4873 add this as well: | |
| 428 | 4874 |
| 4875 @lisp | |
| 2417 | 4876 (global-set-key [(control h)] 'help-for-help) |
| 428 | 4877 @end lisp |
| 4878 | |
| 2459 | 4879 @node Q3.0.11, Q3.1.1, Q3.0.10, Editing |
| 4880 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode? | |
| 2417 | 4881 |
| 4882 Our recommended VI emulator is viper. To make viper-mode the default, | |
| 4883 add this to your @file{init.el}: | |
| 428 | 4884 |
| 4885 @lisp | |
| 2417 | 4886 (viper-mode) |
| 428 | 4887 @end lisp |
| 4888 | |
| 2417 | 4889 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes: |
| 4890 | |
| 4891 @quotation | |
| 4892 This should be added as close to the top of @file{init.el} as you can get | |
| 4893 it, otherwise some minor modes may not get viper-ized. | |
| 4894 @end quotation | |
| 4895 | |
| 4896 @unnumberedsec 3.1: The Mouse | |
| 4897 | |
| 2459 | 4898 @node Q3.1.1, Q3.1.2, Q3.0.11, Editing |
| 2417 | 4899 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting? |
| 428 | 4900 |
| 4901 I keep hitting the middle mouse button by accident and getting stuff | |
| 4902 pasted into my buffer so how can I turn this off? | |
| 4903 | |
| 4904 Here is an alternative binding, whereby the middle mouse button selects | |
| 4905 (but does not cut) the expression under the mouse. Clicking middle on a | |
| 4906 left or right paren will select to the matching one. Note that you can | |
| 4907 use @code{define-key} or @code{global-set-key}. | |
| 4908 | |
| 4909 @lisp | |
| 4910 (defun mouse-set-point-and-select (event) | |
| 4911 "Sets the point at the mouse location, then marks following form" | |
| 4912 (interactive "@@e") | |
| 4913 (mouse-set-point event) | |
| 4914 (mark-sexp 1)) | |
| 4915 (define-key global-map [button2] 'mouse-set-point-and-select) | |
| 4916 @end lisp | |
| 4917 | |
| 2459 | 4918 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing |
| 2417 | 4919 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons? |
| 428 | 4920 |
| 4921 Use, for instance, @code{[(meta button1)]}. For example, here is a common | |
| 4922 setting for Common Lisp programmers who use the bundled @code{ilisp} | |
| 4923 package, whereby meta-button1 on a function name will find the file where | |
| 4924 the function name was defined, and put you at that location in the source | |
| 4925 file. | |
| 4926 | |
| 4927 [Inside a function that gets called by the lisp-mode-hook and | |
| 4928 ilisp-mode-hook] | |
| 4929 | |
| 4930 @lisp | |
| 4931 (local-set-key [(meta button1)] 'edit-definitions-lisp) | |
| 4932 @end lisp | |
| 4933 | |
| 2459 | 4934 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing |
| 2417 | 4935 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list. |
| 428 | 4936 |
| 4937 I do @kbd{C-x C-b} to get a list of buffers and the entries get | |
| 4938 highlighted when I move the mouse over them but clicking the left mouse | |
| 4939 does not do anything. | |
| 4940 | |
| 4941 Use the middle mouse button. | |
| 4942 | |
| 2459 | 4943 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing |
| 2417 | 4944 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3? |
| 428 | 4945 |
| 4946 The following code will replace the default popup on button3: | |
| 4947 | |
| 4948 @lisp | |
| 4949 (global-set-key [button3] 'popup-buffer-menu) | |
| 4950 @end lisp | |
| 4951 | |
| 2459 | 4952 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing |
| 4953 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is? | |
| 428 | 4954 |
| 4955 By default XEmacs pastes X selections where the mouse pointer is. How | |
| 4956 do I disable this? | |
| 4957 | |
| 4958 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank | |
| 4959 @key{RET}}. | |
| 4960 | |
| 2417 | 4961 To get XEmacs to paste at the text cursor, add this your @file{init.el}: |
| 428 | 4962 |
| 4963 @lisp | |
| 4964 (setq mouse-yank-at-point t) | |
| 4965 @end lisp | |
| 4966 | |
| 2459 | 4967 You can also change this with Customize. Select from the |
| 4968 @code{Options} menu @code{Advanced | |
| 4969 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x | |
| 4970 customize @key{RET} mouse @key{RET}}. | |
| 4971 | |
| 4972 @unnumberedsec 3.2: Buffers, Text Editing | |
| 4973 | |
| 4974 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing | |
| 4975 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way? | |
| 4976 | |
| 4977 Say, with: @samp{[END]}? | |
| 4978 | |
| 4979 Try this: | |
| 4980 | |
| 4981 @lisp | |
| 4982 (let ((ext (make-extent (point-min) (point-max)))) | |
| 4983 (set-extent-property ext 'start-closed t) | |
| 4984 (set-extent-property ext 'end-closed t) | |
| 4985 (set-extent-property ext 'detachable nil) | |
| 4986 (set-extent-end-glyph ext (make-glyph [string :data "[END]"]))) | |
| 4987 @end lisp | |
| 4988 | |
| 4989 Since this is XEmacs, you can specify an icon to be shown on | |
| 4990 window-system devices. To do so, change the @code{make-glyph} call to | |
| 4991 something like this: | |
| 4992 | |
| 4993 @lisp | |
| 4994 (make-glyph '([xpm :file "~/something.xpm"] | |
| 4995 [string :data "[END]"])) | |
| 4996 @end lisp | |
| 4997 | |
| 4998 You can inline the @sc{xpm} definition yourself by specifying | |
| 4999 @code{:data} instead of @code{:file}. Here is such a full-featured | |
| 5000 version that works on both X and TTY devices: | |
| 5001 | |
| 5002 @lisp | |
| 5003 (let ((ext (make-extent (point-min) (point-max)))) | |
| 5004 (set-extent-property ext 'start-closed t) | |
| 5005 (set-extent-property ext 'end-closed t) | |
| 5006 (set-extent-property ext 'detachable nil) | |
| 5007 (set-extent-end-glyph ext (make-glyph '([xpm :data "\ | |
| 5008 /* XPM */ | |
| 5009 static char* eye = @{ | |
| 5010 \"20 11 7 2\", | |
| 5011 \"__ c None\" | |
| 5012 \"_` c #7f7f7f\", | |
| 5013 \"_a c #fefefe\", | |
| 5014 \"_b c #7f0000\", | |
| 5015 \"_c c #fefe00\", | |
| 5016 \"_d c #fe0000\", | |
| 5017 \"_e c #bfbfbf\", | |
| 5018 \"___________`_`_`___b_b_b_b_________`____\", | |
| 5019 \"_________`_`_`___b_c_c_c_b_b____________\", | |
| 5020 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\", | |
| 5021 \"___`_`_e_a___b_b_d___b___b___b___b______\", | |
| 5022 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\", | |
| 5023 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\", | |
| 5024 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\", | |
| 5025 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\", | |
| 5026 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\", | |
| 5027 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\", | |
| 5028 \"___`_____`_`_`_`___b_b_b_b_b_b__________\", | |
| 5029 @} ;"] | |
| 5030 [string :data "[END]"])))) | |
| 5031 @end lisp | |
| 5032 | |
| 5033 Note that you might want to make this a function, and put it to a hook. | |
| 5034 We leave that as an exercise for the reader. | |
| 5035 | |
| 5036 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing | |
| 5037 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer? | |
| 2417 | 5038 |
| 5039 Like this: | |
| 428 | 5040 |
| 5041 @lisp | |
| 2459 | 5042 (insert (current-time-string)) |
| 2417 | 5043 @end lisp |
| 5044 | |
| 2459 | 5045 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing |
| 5046 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame? | |
| 5047 | |
| 5048 @email{acs@@acm.org, Vin Shelton} writes: | |
| 2417 | 5049 |
| 5050 @lisp | |
| 2459 | 5051 (setq initial-frame-plist '(minibuffer nil)) |
| 5052 (setq default-frame-plist '(minibuffer nil)) | |
| 5053 (setq default-minibuffer-frame | |
| 5054 (make-frame | |
| 5055 '(minibuffer only | |
| 5056 width 86 | |
| 5057 height 1 | |
| 5058 menubar-visible-p nil | |
| 5059 default-toolbar-visible-p nil | |
| 5060 name "minibuffer" | |
| 5061 top -2 | |
| 5062 left -2 | |
| 5063 has-modeline-p nil))) | |
| 5064 (frame-notice-user-settings) | |
| 2417 | 5065 @end lisp |
| 5066 | |
| 2459 | 5067 @strong{Please note:} The single minibuffer frame may not be to everyone's |
| 5068 taste, and there any number of other XEmacs options settings that may | |
| 5069 make it difficult or inconvenient to use. | |
| 5070 | |
| 5071 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing | |
| 5072 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt? | |
| 5073 | |
| 5074 Put the following line in your @file{init.el}: | |
| 428 | 5075 |
| 5076 @lisp | |
| 2459 | 5077 (setq indent-line-function 'indent-relative-maybe) |
| 428 | 5078 @end lisp |
| 5079 | |
| 2459 | 5080 If you want to get fancy, try the @code{filladapt} package available |
| 5081 standard with XEmacs. Put this into your @file{init.el}: | |
| 428 | 5082 |
| 5083 @lisp | |
| 2459 | 5084 (require 'filladapt) |
| 5085 (setq-default filladapt-mode t) | |
| 5086 (add-hook 'c-mode-hook 'turn-off-filladapt-mode) | |
| 428 | 5087 @end lisp |
| 5088 | |
| 2459 | 5089 This will enable Filladapt for all modes except C mode, where it doesn't |
| 5090 work well. To turn Filladapt on only in particular major modes, remove | |
| 5091 the @code{(setq-default ...)} line and use | |
| 5092 @code{turn-on-filladapt-mode}, like this: | |
| 428 | 5093 |
| 5094 @lisp | |
| 2459 | 5095 (add-hook 'text-mode-hook 'turn-on-filladapt-mode) |
| 428 | 5096 @end lisp |
| 2417 | 5097 |
| 2459 | 5098 You can customize filling and adaptive filling with Customize. |
| 5099 Select from the @code{Options} menu | |
| 5100 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...} | |
| 5101 or type @kbd{M-x customize @key{RET} fill @key{RET}}. | |
| 5102 | |
| 5103 Note that well-behaving text-lookalike modes will run | |
| 5104 @code{text-mode-hook} by default (e.g. that's what Message does). For | |
| 5105 the nasty ones, you'll have to provide the @code{add-hook}s yourself. | |
| 5106 | |
| 5107 Please note that the @code{fa-extras} package is no longer useful. | |
| 5108 | |
| 5109 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing | |
| 5110 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 5111 | |
| 5112 Try the following lisp in your @file{init.el}: | |
| 2417 | 5113 |
| 5114 @lisp | |
| 2459 | 5115 (setq default-major-mode 'text-mode) |
| 2769 | 5116 (add-hook 'text-mode-hook 'turn-on-auto-fill) |
| 2417 | 5117 @end lisp |
| 5118 | |
| 2459 | 5119 @strong{WARNING}: note that changing the value of |
| 5120 @code{default-major-mode} from @code{fundamental-mode} can break a large | |
| 5121 amount of built-in code that expects newly created buffers to be in | |
| 5122 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to | |
| 5123 @code{text-mode} might not wreak too much havoc, but changing to | |
| 5124 something more exotic like a lisp-mode would break many Emacs packages). | |
| 5125 | |
| 5126 Note that Emacs by default starts up in buffer @code{*scratch*} in | |
| 5127 @code{initial-major-mode}, which defaults to | |
| 5128 @code{lisp-interaction-mode}. Thus adding the following form to your | |
| 5129 Emacs init file will cause the initial @code{*scratch*} buffer to be put | |
| 5130 into auto-fill'ed @code{text-mode}: | |
| 2417 | 5131 |
| 5132 @lisp | |
| 2459 | 5133 (setq initial-major-mode |
| 5134 (lambda () | |
| 5135 (text-mode) | |
| 5136 (turn-on-auto-fill))) | |
| 2417 | 5137 @end lisp |
| 5138 | |
| 2459 | 5139 Note that after your init file is loaded, if |
| 5140 @code{inhibit-startup-message} is @code{nil} (the default) and the | |
| 5141 startup buffer is @code{*scratch*} then the startup message will be | |
| 5142 inserted into @code{*scratch*}; it will be removed after a timeout by | |
| 5143 erasing the entire @code{*scratch*} buffer. Keep in mind this default | |
| 5144 usage of @code{*scratch*} if you desire any prior manipulation of | |
| 5145 @code{*scratch*} from within your Emacs init file. In particular, | |
| 5146 anything you insert into @code{*scratch*} from your init file will be | |
| 5147 later erased. Also, if you change the mode of the @code{*scratch*} | |
| 5148 buffer, be sure that this will not interfere with possible later | |
| 5149 insertion of the startup message (e.g. if you put @code{*scratch*} into | |
| 5150 a nonstandard mode that has automatic font lock rules, then the startup | |
| 5151 message might get fontified in a strange foreign manner, e.g. as code in | |
| 5152 some programming language). | |
| 5153 | |
| 5154 @unnumberedsec 3.3: Text Selections | |
| 5155 | |
| 5156 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing | |
| 5157 @unnumberedsubsec Q3.3.1: How do I select a rectangular region? | |
| 2417 | 5158 |
| 5159 Just select the region normally, then use the rectangle commands (e.g. | |
| 5160 @code{kill-rectangle} on it. The region does not highlight as a | |
| 5161 rectangle, but the commands work just fine. | |
| 5162 | |
| 5163 To actually sweep out rectangular regions with the mouse you can use | |
| 5164 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}. | |
| 5165 Then use rectangle commands. | |
| 5166 | |
| 5167 You can also do the following to change default behavior to sweep out | |
| 5168 rectangular regions: | |
| 5169 | |
| 5170 @lisp | |
| 5171 (setq mouse-track-rectangle-p t) | |
| 5172 @end lisp | |
| 5173 | |
| 2459 | 5174 You can also change this with Customize. |
| 2417 | 5175 Select from the @code{Options} menu |
| 5176 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type | |
| 5177 @kbd{M-x customize @key{RET} mouse @key{RET}}. | |
| 5178 | |
| 5179 | |
| 5180 @example | |
| 5181 mouse-track-do-rectangle: (event) | |
| 5182 -- an interactive compiled Lisp function. | |
| 5183 Like `mouse-track' but selects rectangles instead of regions. | |
| 5184 @end example | |
| 5185 | |
| 2459 | 5186 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing |
| 5187 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections? | |
| 428 | 5188 |
| 5189 The @code{zmacs} mode allows for what some might call gratuitous | |
| 5190 highlighting for selected regions (either by setting mark or by using | |
| 5191 the mouse). This is the default behavior. To turn off, add the | |
| 2417 | 5192 following line to your @file{init.el} file: |
| 428 | 5193 |
| 5194 @lisp | |
| 5195 (setq zmacs-regions nil) | |
| 5196 @end lisp | |
| 5197 | |
| 2417 | 5198 You can also change this with Customize. Select from the |
| 5199 @code{Options} menu | |
| 5200 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions} | |
| 5201 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}. | |
| 5202 | |
| 5203 To change the face for selection, look at @code{Options->Advanced (Customize)} | |
| 5204 on the menubar. | |
| 5205 | |
| 2459 | 5206 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing |
| 5207 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it? | |
| 428 | 5208 |
| 5209 I want to change things so that if I select some text and start typing, | |
| 5210 the typed text replaces the selected text, similar to Motif. | |
| 5211 | |
| 5212 You want to use something called @dfn{pending delete}. Pending delete | |
| 5213 is what happens when you select a region (with the mouse or keyboard) | |
| 5214 and you press a key to replace the selected region by the key you typed. | |
| 5215 Usually backspace kills the selected region. | |
| 5216 | |
| 2164 | 5217 To get this behavior, ensure that you have the @file{pc} package |
| 5218 installed, and add the following lines to your | |
| 2417 | 5219 @file{init.el}: |
| 428 | 5220 |
| 5221 @lisp | |
| 438 | 5222 (cond |
| 5223 ((fboundp 'turn-on-pending-delete) | |
| 5224 (turn-on-pending-delete)) | |
| 5225 ((fboundp 'pending-delete-on) | |
| 5226 (pending-delete-on t))) | |
| 428 | 5227 @end lisp |
| 5228 | |
| 1138 | 5229 Note that this will work with both Backspace and Delete. This code is a |
| 438 | 5230 tad more complicated than it has to be for XEmacs in order to make it |
| 5231 more portable. | |
| 428 | 5232 |
| 2459 | 5233 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing |
| 5234 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch? | |
| 428 | 5235 |
| 5236 I do not like my text highlighted while I am doing isearch as I am not | |
| 5237 able to see what's underneath. How do I turn it off? | |
| 5238 | |
| 2417 | 5239 Put the following in your @file{init.el}: |
| 428 | 5240 |
| 5241 @lisp | |
| 5242 (setq isearch-highlight nil) | |
| 5243 @end lisp | |
| 5244 | |
| 2459 | 5245 You can also change this with Customize. Type |
| 428 | 5246 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}. |
| 5247 | |
| 5248 Note also that isearch-highlight affects query-replace and ispell. | |
| 5249 Instead of disabling isearch-highlight you may find that a better | |
| 5250 solution consists of customizing the @code{isearch} face. | |
| 5251 | |
| 2459 | 5252 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing |
| 5253 @unnumberedsubsec Q3.3.5: Why is killing so slow? | |
| 892 | 5254 |
| 5255 This actually is an X Windows question, although you'll notice it with | |
| 5256 keyboard operations as well as while using the GUI. Basically, there | |
| 5257 are four ways to communicate interprogram via the X server: | |
| 5258 | |
| 5259 @table @strong | |
| 5260 @item Primary selection | |
| 5261 a transient selection that gets replaced every time a new selection is made | |
| 5262 | |
| 5263 @item Secondary selection | |
| 5264 for "exchanging" with the primary selection | |
| 5265 | |
| 5266 @item Cut buffers | |
| 5267 a clipboard internal to the X server (deprecated) | |
| 5268 | |
| 5269 @item Clipboard selection | |
| 5270 a selection with a notification protocol that allows a separate app to | |
| 5271 manage the clipboard | |
| 5272 @end table | |
| 5273 | |
| 5274 The cut buffers are deprecated because managing them is even more | |
| 5275 inefficient than the clipboard notification protocol. The primary | |
| 5276 selection works fine for many users and applications, but is not very | |
| 5277 robust under intensive or sophisticated use. | |
| 5278 | |
| 5279 In Motif and MS Windows, a clipboard has become the primary means for | |
| 5280 managing cut and paste. These means that "modern" applications tend to | |
| 5281 be oriented toward a true clipboard, rather than the primary selection. | |
| 5282 (On Windows, there is nothing equivalent to the primary selection.) | |
| 5283 It's not that XEmacs doesn't support the simple primary selection | |
| 5284 method, it's that more and more other applications don't. | |
| 5285 | |
| 5286 So the slowdown occurs because XEmacs now engages in the clipboard | |
| 5287 notification protocol on @emph{every} kill. This is especially slow on | |
| 5288 Motif. | |
| 5289 | |
| 5290 With most people running most clients and server on the same host, and | |
| 5291 many of the rest working over very fast communication, you may expect | |
| 5292 that the situation is not going to improve. | |
| 5293 | |
| 5294 There are a number of workarounds. The most effective is to use a | |
| 5295 special command to do selection ownership only when you intend to paste | |
| 5296 to another application. Useful commands are @code{kill-primary-selection} | |
| 5297 and @code{copy-primary-selection}. These work only on text selected | |
| 5298 with the mouse (probably; experiment), and are bound by default to the | |
| 5299 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar. | |
| 5300 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can | |
| 5301 yank the clipboard contents with @code{yank-primary-selection}, bound to | |
| 5302 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}. | |
| 5303 | |
| 5304 If you are communicating by cut and paste with applications that use the | |
| 5305 primary selection, then you can customize | |
| 5306 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs | |
| 5307 version 20 behavior. How can you tell if a program will support this? | |
| 5308 Motifly-correct programs require the clipboard; you lose. For others, | |
| 5309 only by trying it. You also need to customize the complementary | |
| 5310 @code{interprogram-paste-function} to @code{nil}. (Otherwise | |
| 5311 XEmacs-to-XEmacs pastes will not work correctly.) | |
| 5312 | |
| 5313 You may get some relief on Motif by setting | |
| 5314 @code{x-selection-strict-motif-ownership} to nil, but this means you will | |
| 5315 only intermittently be able to paste XEmacs kills to Motif applications. | |
| 5316 | |
| 5317 Thanks to Jeff Mincy and Glynn Clements for corrections. | |
| 5318 | |
| 2459 | 5319 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing |
| 5320 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long? | |
| 2417 | 5321 |
| 5322 It actually doesn't. It leaves the region visible for a second so that | |
| 5323 you can see what area is being yanked. If you start working, though, it | |
| 5324 will immediately complete its operation. In other words, it will only | |
| 5325 delay for a second if you let it. | |
| 5326 | |
| 2459 | 5327 @unnumberedsec 3.4: Editing Source Code |
| 5328 | |
| 5329 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing | |
| 5330 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode? | |
| 2417 | 5331 |
| 5332 Well, first off, consider if you really want to do this. cc-mode is | |
| 5333 much more powerful than the old c-mode. If you're having trouble | |
| 5334 getting your old offsets to work, try using @code{c-set-offset} instead. | |
| 5335 You might also consider using the package @code{cc-compat}. | |
| 5336 | |
| 5337 But, if you still insist, add the following lines to your @file{init.el}: | |
| 5338 | |
| 5339 @lisp | |
| 5340 (fmakunbound 'c-mode) | |
| 5341 (makunbound 'c-mode-map) | |
| 5342 (fmakunbound 'c++-mode) | |
| 5343 (makunbound 'c++-mode-map) | |
| 5344 (makunbound 'c-style-alist) | |
| 5345 (load-library "old-c-mode") | |
| 5346 (load-library "old-c++-mode") | |
| 5347 @end lisp | |
| 5348 | |
| 5349 This must be done before any other reference is made to either c-mode or | |
| 5350 c++-mode. | |
| 5351 | |
| 2459 | 5352 @node Q3.4.2, , Q3.4.1, Editing |
| 5353 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly? | |
| 2417 | 5354 |
| 5355 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the | |
| 5356 same amount instead of indenting the 3rd clause differently from the | |
| 5357 first two. | |
| 5358 | |
| 2459 | 5359 The package @code{cl-indent} that comes with XEmacs sets up this kind |
| 5360 of indentation by default. @code{cl-indent} also knows about many | |
| 5361 other CL-specific forms. To use @code{cl-indent}, one can do this: | |
| 2417 | 5362 |
| 5363 @lisp | |
| 2459 | 5364 (setq lisp-indent-function 'common-lisp-indent-function) |
| 2417 | 5365 @end lisp |
| 5366 | |
| 5367 One can also customize @file{cl-indent.el} so it mimics the default | |
| 5368 @code{if} indentation @code{then} indented more than the @code{else}. | |
| 5369 Here's how: | |
| 5370 | |
| 5371 @lisp | |
| 5372 (put 'if 'common-lisp-indent-function '(nil nil &body)) | |
| 5373 @end lisp | |
| 5374 | |
| 2459 | 5375 @node Display, External Subsystems, Editing, Top |
| 5376 @unnumbered 4 Display Functions | |
| 428 | 5377 |
| 5378 This is part 4 of the XEmacs Frequently Asked Questions list. This | |
| 2459 | 5379 section is devoted to the display-related capabilities of XEmacs |
| 5380 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how | |
| 5381 to customize them. | |
| 5382 | |
| 5383 @menu | |
| 5384 4.0: Textual Fonts and Colors | |
| 5385 * Q4.0.1:: How do I specify a font? | |
| 5386 * Q4.0.2:: How do I set the text, menu and modeline fonts? | |
| 5387 * Q4.0.3:: How can I set color options from @file{init.el}? | |
| 5388 * Q4.0.4:: How can I set the colors when highlighting a region? | |
| 5389 * Q4.0.5:: How can I limit color map usage? | |
| 5390 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them. | |
| 5391 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs? | |
| 5392 * Q4.0.8:: How do I display non-ASCII characters? | |
| 5393 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}. | |
| 5394 | |
| 5395 4.1: Syntax Highlighting (Font Lock) | |
| 5396 * Q4.1.1:: How can I do source code highlighting using font-lock? | |
| 5397 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default? | |
| 5398 | |
| 5399 4.2: The Modeline | |
| 5400 * Q4.2.1:: How can I make the modeline go away? | |
| 5401 * Q4.2.2:: How do you have XEmacs display the line number in the modeline? | |
| 5402 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline? | |
| 5403 * Q4.2.4:: How can I change the modeline color based on the mode used? | |
| 5404 | |
| 5405 4.3: The Cursor | |
| 5406 * Q4.3.1:: Is there a way to make the bar cursor thicker? | |
| 5407 * Q4.3.2:: Is there a way to get back the block cursor? | |
| 5408 * Q4.3.3:: Can I make the cursor blink? | |
| 5409 | |
| 5410 4.4: The Menubar | |
| 5411 * Q4.4.1:: How do I get rid of the menubar? | |
| 5412 * Q4.4.2:: How can I customize the menubar? | |
| 5413 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 5414 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 5415 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working? | |
| 5416 | |
| 5417 4.5: The Toolbar | |
| 5418 * Q4.5.1:: How do I get rid of the toolbar? | |
| 5419 * Q4.5.2:: How can I customize the toolbar? | |
| 5420 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar? | |
| 5421 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar | |
| 5422 | |
| 5423 4.6: Scrollbars and Scrolling | |
| 5424 * Q4.6.1:: How can I disable the scrollbar? | |
| 5425 * Q4.6.2:: How can I change the scrollbar width? | |
| 5426 * Q4.6.3:: How can I use resources to change scrollbar colors? | |
| 5427 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this? | |
| 5428 * Q4.6.5:: Scrolling one line at a time. | |
| 5429 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes? | |
| 5430 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off? | |
| 5431 | |
| 5432 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 5433 * Q4.7.1:: How can I disable the gutter tabs? | |
| 5434 * Q4.7.2:: How can I disable the progress bar? | |
| 5435 * Q4.7.3:: There are bugs in the gutter or widgets. | |
| 5436 * Q4.7.4:: How can I customize the gutter or gutter tabs? | |
| 5437 @end menu | |
| 5438 | |
| 5439 @unnumberedsec 4.0: Textual Fonts and Colors | |
| 5440 | |
| 5441 @node Q4.0.1, Q4.0.2, Display, Display | |
| 5442 @unnumberedsubsec Q4.0.1: How do I specify a font? | |
| 5443 | |
| 5444 #### Update me. | |
| 5445 | |
| 5446 In 21.4 and above, you can use the @samp{Options} menu to change the font. | |
| 5447 You can also do it in your init file, e.g. like this (for MS Windows): | |
| 5448 | |
| 5449 @display | |
| 5450 (set-face-font 'default "Lucida Console:Regular:10") | |
| 5451 (set-face-font 'modeline "MS Sans Serif:Regular:10") | |
| 5452 @end display | |
| 5453 | |
| 5454 @node Q4.0.2, Q4.0.3, Q4.0.1, Display | |
| 5455 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts? | |
| 5456 | |
| 5457 #### Update me. | |
| 5458 | |
| 5459 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when | |
| 5460 setting face values. | |
| 5461 | |
| 5462 In @file{.Xresources}: | |
| 5463 | |
| 5464 @example | |
| 5465 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-* | |
| 5466 Emacs*menubar*font: fixed | |
| 5467 Emacs.modeline.attributeFont: fixed | |
| 5468 @end example | |
| 5469 | |
| 5470 This is confusing because @samp{default} and @samp{modeline} are face | |
| 5471 names, and can be found listed with all faces in the current mode by | |
| 5472 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific | |
| 5473 resource @samp{attributeFont}. | |
| 5474 | |
| 5475 On the other hand, @samp{menubar} is a normal X thing that uses the | |
| 5476 resource @samp{font}. With Motif it @emph{may be} necessary to use | |
| 5477 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif} | |
| 5478 configurations with Mule it @emph{is} necessary to use @samp{fontSet} | |
| 5479 instead of @samp{font}. (Sorry, there just is no simple recipe here.) | |
| 5480 | |
| 5481 @node Q4.0.3, Q4.0.4, Q4.0.2, Display | |
| 5482 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}? | |
| 5483 | |
| 5484 How can I set the most commonly used color options from my | |
| 5485 @file{init.el} instead of from my @file{.Xresources}? | |
| 5486 | |
| 5487 Like this: | |
| 5488 | |
| 5489 @lisp | |
| 5490 (set-face-background 'default "bisque") ; frame background | |
| 5491 (set-face-foreground 'default "black") ; normal text | |
| 5492 (set-face-background 'zmacs-region "red") ; When selecting w/ | |
| 5493 ; mouse | |
| 5494 (set-face-foreground 'zmacs-region "yellow") | |
| 5495 (set-face-font 'default "*courier-bold-r*120-100-100*") | |
| 5496 (set-face-background 'highlight "blue") ; Ie when selecting | |
| 5497 ; buffers | |
| 5498 (set-face-foreground 'highlight "yellow") | |
| 5499 (set-face-background 'modeline "blue") ; Line at bottom | |
| 5500 ; of buffer | |
| 5501 (set-face-foreground 'modeline "white") | |
| 5502 (set-face-font 'modeline "*bold-r-normal*140-100-100*") | |
| 5503 (set-face-background 'isearch "yellow") ; When highlighting | |
| 5504 ; while searching | |
| 5505 (set-face-foreground 'isearch "red") | |
| 5506 (setq x-pointer-foreground-color "black") ; Adds to bg color, | |
| 5507 ; so keep black | |
| 5508 (setq x-pointer-background-color "blue") ; This is color | |
| 5509 ; you really | |
| 5510 ; want ptr/crsr | |
| 5511 @end lisp | |
| 5512 | |
| 5513 @node Q4.0.4, Q4.0.5, Q4.0.3, Display | |
| 5514 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region? | |
| 5515 | |
| 5516 How can I set the background/foreground colors when highlighting a | |
| 5517 region? | |
| 5518 | |
| 5519 You can change the face @code{zmacs-region} either in your | |
| 5520 @file{.Xresources}: | |
| 5521 | |
| 5522 @example | |
| 5523 Emacs.zmacs-region.attributeForeground: firebrick | |
| 5524 Emacs.zmacs-region.attributeBackground: lightseagreen | |
| 5525 @end example | |
| 5526 | |
| 5527 or in your @file{init.el}: | |
| 5528 | |
| 5529 @lisp | |
| 5530 (set-face-background 'zmacs-region "red") | |
| 5531 (set-face-foreground 'zmacs-region "yellow") | |
| 5532 @end lisp | |
| 5533 | |
| 5534 @node Q4.0.5, Q4.0.6, Q4.0.4, Display | |
| 5535 @unnumberedsubsec Q4.0.5: How can I limit color map usage? | |
| 5536 | |
| 5537 I'm using Netscape (or another color grabber like XEmacs); | |
| 5538 is there any way to limit the number of available colors in the color map? | |
| 5539 | |
| 5540 Answer: No, but you can start Netscape before XEmacs, and it will use | |
| 5541 the closest available color if the colormap is full. You can also limit | |
| 5542 the number of colors Netscape uses, using the flags -mono, -ncols <#> or | |
| 5543 -install (for mono, limiting to <#> colors, or for using a private color | |
| 5544 map). | |
| 5545 | |
| 5546 If you have the money, another solution would be to use a truecolor or | |
| 5547 direct color video. | |
| 5548 | |
| 5549 @node Q4.0.6, Q4.0.7, Q4.0.5, Display | |
| 5550 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them. | |
| 5551 | |
| 5552 XEmacs tries to automatically determine whether your tty supports color, | |
| 5553 but sometimes guesses wrong. In that case, you can make XEmacs Do The | |
| 5554 Right Thing using this Lisp code: | |
| 5555 | |
| 5556 @lisp | |
| 5557 (if (eq 'tty (device-type)) | |
| 5558 (set-device-class nil 'color)) | |
| 5559 @end lisp | |
| 5560 | |
| 5561 @node Q4.0.7, Q4.0.8, Q4.0.6, Display | |
| 5562 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs? | |
| 5563 @c New | |
| 5564 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes: | |
| 5565 | |
| 5566 @quotation | |
| 5567 There are several ways to do it. For example, you could specify a | |
| 5568 default pixmap image to use in your @file{~/.Xresources}, e.g., | |
| 5569 | |
| 5570 | |
| 5571 @example | |
| 5572 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm | |
| 5573 @end example | |
| 5574 | |
| 5575 | |
| 5576 and then reload ~/.Xresources and restart XEmacs. Alternatively, | |
| 5577 since each face can have its own pixmap background, a better way | |
| 5578 would be to set a face's pixmap within your XEmacs init file, e.g., | |
| 5579 | |
| 5580 @lisp | |
| 5581 (set-face-background-pixmap 'default "/path/to/image.xpm") | |
| 5582 (set-face-background-pixmap 'bold "/path/to/another_image.xpm") | |
| 5583 @end lisp | |
| 5584 | |
| 5585 and so on. You can also do this interactively via @kbd{M-x edit-faces}. | |
| 5586 | |
| 5587 @end quotation | |
| 5588 | |
| 5589 @node Q4.0.8, Q4.0.9, Q4.0.7, Display | |
| 5590 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters? | |
| 5591 @c New | |
| 5592 | |
| 5593 If you're using a Mule-enabled XEmacs, then display is automatic. If | |
| 5594 you're not seeing the characters you expect, either (1) you don't have | |
| 5595 appropriate fonts available or (2) XEmacs did not correctly detect the | |
| 5596 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1), | |
| 5597 install fonts as is customary for your platform. In case (2), you | |
| 5598 need to tell XEmacs explicitly what coding systems you're using. | |
| 5599 @ref{Specify Coding, , , xemacs}. | |
| 5600 | |
| 5601 If your XEmacs is not Mule-enabled, and for some reason getting a | |
| 5602 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost. | |
| 5603 You can arrange it by brute force. In @file{event-Xt.c} (suppress the | |
| 5604 urge to look in this file---play Doom instead, because you'll survive | |
| 5605 longer), it is written: | |
| 5606 | |
| 5607 @quotation | |
| 5608 In a non-Mule world, a user can still have a multi-lingual editor, by | |
| 5609 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all | |
| 5610 their Latin-2 buffers, etc. | |
| 5611 @end quotation | |
| 5612 | |
| 5613 For the related problem of @emph{inputting} non-ASCII characters in a | |
| 5614 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters | |
| 5615 in XEmacs?}. | |
| 5616 | |
| 5617 @node Q4.0.9, Q4.1.1, Q4.0.8, Display | |
| 5618 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}. | |
| 5619 | |
| 5620 @email{mannj@@ll.mit.edu, John Mann} writes: | |
| 5621 | |
| 5622 @quotation | |
| 5623 You have to go to @samp{Options->Menubars} and unselect | |
| 5624 @samp{Frame-Local Font Menu}. If this option is selected, font changes | |
| 5625 are only applied to the @emph{current} frame and do @emph{not} get saved | |
| 5626 when you save options. | |
| 5627 @end quotation | |
| 5628 | |
| 5629 Also, set the following in your @file{init.el}: | |
| 5630 | |
| 5631 @lisp | |
| 5632 (setq options-save-faces t) | |
| 5633 @end lisp | |
| 5634 | |
| 5635 @unnumberedsec 4.1: Syntax Highlighting (Font Lock) | |
| 5636 | |
| 5637 @node Q4.1.1, Q4.1.2, Q4.0.9, Display | |
| 5638 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock? | |
| 5639 | |
| 5640 For most modes, font-lock is already set up and just needs to be turned | |
| 5641 on. This can be done by adding the line: | |
| 5642 | |
| 5643 @lisp | |
| 5644 (require 'font-lock) | |
| 5645 @end lisp | |
| 5646 | |
| 5647 to your @file{init.el}. (You can turn it on for the | |
| 5648 current buffer and session only by @kbd{M-x font-lock-mode}.) See the | |
| 5649 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs | |
| 5650 versions prior to 21.4) for more information. | |
| 5651 | |
| 5652 @c the old way: | |
| 5653 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock) | |
| 5654 @c (add-hook 'dired-mode-hook 'turn-on-font-lock) | |
| 5655 | |
| 5656 See also @code{Syntax Highlighting} from the @code{Options} menu. | |
| 5657 Remember to save options. | |
| 5658 | |
| 5659 @node Q4.1.2, Q4.2.1, Q4.1.1, Display | |
| 5660 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default? | |
| 5661 | |
| 5662 Use the following code in your @file{init.el}: | |
| 5663 | |
| 5664 @lisp | |
| 5665 (setq-default font-lock-maximum-decoration t) | |
| 5666 @end lisp | |
| 5667 | |
| 5668 See also @code{Syntax Highlighting} from the @code{Options} menu. | |
| 5669 Remember to save options. | |
| 5670 | |
| 5671 @unnumberedsec 4.2: The Modeline | |
| 5672 | |
| 5673 @node Q4.2.1, Q4.2.2, Q4.1.2, Display | |
| 5674 @unnumberedsubsec Q4.2.1: How can I make the modeline go away? | |
| 5675 | |
| 5676 @lisp | |
| 5677 (set-specifier has-modeline-p nil) | |
| 5678 @end lisp | |
| 5679 | |
| 5680 @node Q4.2.2, Q4.2.3, Q4.2.1, Display | |
| 5681 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline? | |
| 5682 | |
| 5683 Add the following line to your @file{init.el} file to | |
| 5684 display the line number: | |
| 5685 | |
| 5686 @lisp | |
| 5687 (line-number-mode 1) | |
| 5688 @end lisp | |
| 5689 | |
| 5690 Use the following to display the column number: | |
| 5691 | |
| 5692 @lisp | |
| 5693 (column-number-mode 1) | |
| 5694 @end lisp | |
| 5695 | |
| 5696 Or select from the @code{Options} menu | |
| 5697 @iftex | |
| 5698 @* | |
| 5699 @end iftex | |
| 5700 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode} | |
| 5701 and/or | |
| 5702 @iftex | |
| 5703 @* | |
| 5704 @end iftex | |
| 5705 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode} | |
| 5706 | |
| 5707 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}. | |
| 5708 | |
| 5709 @node Q4.2.3, Q4.2.4, Q4.2.2, Display | |
| 5710 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline? | |
| 5711 | |
| 5712 Add the following line to your @file{init.el} file to | |
| 5713 display the time: | |
| 5714 | |
| 5715 @lisp | |
| 5716 (display-time) | |
| 5717 @end lisp | |
| 5718 | |
| 5719 See @code{Customize} from the @code{Options} menu for customization. | |
| 5720 | |
| 5721 @node Q4.2.4, Q4.3.1, Q4.2.3, Display | |
| 5722 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used? | |
| 5723 | |
| 5724 You can use something like the following: | |
| 5725 | |
| 5726 @lisp | |
| 5727 (add-hook 'lisp-mode-hook | |
| 5728 (lambda () | |
| 5729 (set-face-background 'modeline "red" (current-buffer)))) | |
| 5730 @end lisp | |
| 5731 | |
| 5732 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline | |
| 5733 colors change from the default set in your @file{init.el}. | |
| 5734 The change will only be made in the buffer you just entered (which | |
| 5735 contains the Lisp file you are editing) and will not affect the modeline | |
| 5736 colors anywhere else. | |
| 5737 | |
| 5738 Notes: | |
| 5739 | |
| 5740 @itemize @bullet | |
| 5741 | |
| 5742 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook, | |
| 5743 c++-mode-hook, emacs-lisp-mode-hook (used for your | |
| 5744 @file{init.el} or a @file{xx.el} file), | |
| 5745 lisp-interaction-mode-hook (the @samp{*scratch*} buffer), | |
| 5746 text-mode-hook, etc. | |
| 5747 | |
| 5748 @item | |
| 5749 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)}, | |
| 5750 otherwise you will erase anything that anybody has already put on the | |
| 5751 hook. | |
| 5752 | |
| 5753 @item | |
| 5754 You can also do @code{(set-face-font 'modeline @var{font})}, | |
| 5755 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*" | |
| 5756 (current-buffer))} if you wish the modeline font to vary based on the | |
| 5757 current mode. | |
| 5758 @end itemize | |
| 5759 | |
| 5760 There are additional modeline faces, @code{modeline-buffer-id}, | |
| 5761 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which | |
| 5762 you may want to customize. | |
| 5763 | |
| 5764 @unnumberedsec 4.3: The Cursor | |
| 5765 | |
| 5766 @node Q4.3.1, Q4.3.2, Q4.2.4, Display | |
| 5767 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker? | |
| 5768 | |
| 5769 I'd like to have the bar cursor a little thicker, as I tend to "lose" it | |
| 5770 often. | |
| 5771 | |
| 5772 For a 1 pixel bar cursor, use: | |
| 5773 | |
| 5774 @lisp | |
| 5775 (setq bar-cursor t) | |
| 5776 @end lisp | |
| 5777 | |
| 5778 For a 2 pixel bar cursor, use: | |
| 5779 | |
| 5780 @lisp | |
| 5781 (setq bar-cursor 'anything-else) | |
| 5782 @end lisp | |
| 5783 | |
| 5784 You can also change these with Customize. | |
| 5785 Select from the @code{Options} menu | |
| 5786 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type | |
| 5787 @kbd{M-x customize @key{RET} display @key{RET}}. | |
| 5788 | |
| 5789 You can use a color to make it stand out better: | |
| 5790 | |
| 5791 @example | |
| 5792 Emacs*cursorColor: Red | |
| 5793 @end example | |
| 5794 | |
| 5795 @node Q4.3.2, Q4.3.3, Q4.3.1, Display | |
| 5796 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor? | |
| 5797 | |
| 5798 @lisp | |
| 5799 (setq bar-cursor nil) | |
| 5800 @end lisp | |
| 5801 | |
| 5802 You can also change this with Customize. | |
| 5803 Select from the @code{Options} menu | |
| 5804 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type | |
| 5805 @kbd{M-x customize @key{RET} display @key{RET}}. | |
| 5806 | |
| 5807 @node Q4.3.3, Q4.4.1, Q4.3.2, Display | |
| 5808 @unnumberedsubsec Q4.3.3: Can I make the cursor blink? | |
| 5809 | |
| 5810 Yes, like this: | |
| 5811 | |
| 5812 @lisp | |
| 5813 (blink-cursor-mode) | |
| 5814 @end lisp | |
| 5815 | |
| 5816 This function toggles between a steady cursor and a blinking cursor. | |
| 5817 You may also set this mode from the menu bar by selecting | |
| 5818 @samp{Options->Display->Blinking Cursor}. Remember to save options. | |
| 5819 | |
| 5820 @unnumberedsec 4.4: The Menubar | |
| 5821 | |
| 5822 @node Q4.4.1, Q4.4.2, Q4.3.3, Display | |
| 5823 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar? | |
| 5824 | |
| 5825 @lisp | |
| 5826 (set-specifier menubar-visible-p nil) | |
| 5827 @end lisp | |
| 5828 | |
| 5829 @node Q4.4.2, Q4.4.3, Q4.4.1, Display | |
| 5830 @unnumberedsubsec Q4.4.2: How can I customize the menubar? | |
| 5831 | |
| 5832 For an extensive menubar, add this line to your @file{init.el}: | |
| 5833 | |
| 5834 @lisp | |
| 5835 (load "big-menubar") | |
| 5836 @end lisp | |
| 5837 | |
| 5838 If you'd like to write your own, this file provides as good a set of | |
| 5839 examples as any to start from. The file is located in edit-utils | |
| 5840 package. | |
| 5841 | |
| 5842 @node Q4.4.3, Q4.4.4, Q4.4.2, Display | |
| 5843 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 5844 | |
| 5845 #### Write me. | |
| 5846 | |
| 5847 @node Q4.4.4, Q4.4.5, Q4.4.3, Display | |
| 5848 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 5849 | |
| 5850 Add the following to your @file{init.el} (suit to fit): | |
| 5851 | |
| 5852 @lisp | |
| 5853 (setq buffers-menu-max-size 20) | |
| 5854 @end lisp | |
| 5855 | |
| 5856 For no limit, use an argument of @samp{nil}. | |
| 5857 | |
| 5858 You can also change this with Customize. Select from the | |
| 5859 @code{Options} menu | |
| 5860 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...} | |
| 5861 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}. | |
| 5862 | |
| 5863 @node Q4.4.5, Q4.5.1, Q4.4.4, Display | |
| 5864 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working? | |
| 5865 | |
| 5866 I am trying to use a resource like @code{Emacs*menubar*font} to set the | |
| 5867 font of the menubar but it's not working. | |
| 5868 | |
| 5869 In Motif, the use of @samp{font} resources is obsoleted in order to | |
| 5870 support internationalization. If you are using the real Motif menubar, | |
| 5871 this resource is not recognized at all; you have to say: | |
| 5872 | |
| 5873 @example | |
| 5874 Emacs*menubar*fontList: FONT | |
| 5875 @end example | |
| 5876 | |
| 5877 If you are using the Lucid menubar, for backward compatibility with | |
| 5878 existing user configurations, the @samp{font} resource is recognized. | |
| 5879 Since this is not supported by Motif itself, the code is a kludge and | |
| 5880 the @samp{font} resource will be recognized only if the @samp{fontList} | |
| 5881 resource resource is unset. This means that the resource | |
| 5882 | |
| 5883 @example | |
| 5884 *fontList: FONT | |
| 5885 @end example | |
| 5886 | |
| 5887 will override | |
| 5888 | |
| 5889 @example | |
| 5890 Emacs*menubar*font: FONT | |
| 5891 @end example | |
| 5892 | |
| 5893 even though the latter is more specific. | |
| 5894 | |
| 5895 In non-Motif configurations using @samp{--with-mule} and | |
| 5896 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet} | |
| 5897 resource @emph{instead of} the @code{font} resource. The backward | |
| 5898 compatibility kludge was never implemented for non-Motif builds. | |
| 5899 Example: | |
| 5900 | |
| 5901 @example | |
| 5902 *fontSet: FONT | |
| 5903 @end example | |
| 5904 | |
| 5905 @unnumberedsec 4.5: The Toolbar | |
| 5906 | |
| 5907 @node Q4.5.1, Q4.5.2, Q4.4.5, Display | |
| 5908 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar? | |
| 5909 | |
| 5910 #### Write me. | |
| 5911 | |
| 5912 @node Q4.5.2, Q4.5.3, Q4.5.1, Display | |
| 5913 @unnumberedsubsec Q4.5.2: How can I customize the toolbar? | |
| 5914 | |
| 5915 #### Write me. | |
| 5916 | |
| 5917 @node Q4.5.3, Q4.5.4, Q4.5.2, Display | |
| 5918 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar? | |
| 5919 | |
| 5920 Try something like: | |
| 5921 | |
| 5922 @lisp | |
| 5923 (defun my-toggle-toolbar () | |
| 5924 (interactive) | |
| 5925 (set-specifier default-toolbar-visible-p | |
| 5926 (not (specifier-instance default-toolbar-visible-p)))) | |
| 5927 (global-set-key "\C-xT" 'my-toggle-toolbar) | |
| 5928 @end lisp | |
| 5929 | |
| 5930 @ignore | |
| 5931 @c Probably not relevant any more | |
| 5932 There are redisplay bugs in 19.14 that may make the preceding result in | |
| 5933 a messed-up display, especially for frames with multiple windows. You | |
| 5934 may need to resize the frame before XEmacs completely realizes the | |
| 5935 toolbar is really gone. | |
| 5936 @end ignore | |
| 5937 | |
| 5938 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct | |
| 5939 code. | |
| 5940 | |
| 5941 @node Q4.5.4, Q4.6.1, Q4.5.3, Display | |
| 5942 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar | |
| 5943 | |
| 5944 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes: | |
| 5945 | |
| 5946 I just installed the XEmacs (20.4-2) RPMS that I downloaded from | |
| 5947 @uref{http://www.xemacs.org/}. Everything works fine, except that when | |
| 5948 I place my mouse over the toolbar, it beeps and gives me this message: | |
| 5949 | |
| 5950 @example | |
| 5951 Can't instantiate image (probably cached): | |
| 5952 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data | |
| 5953 (16 16 <strange control characters> ... | |
| 5954 @end example | |
| 5955 | |
| 5956 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes: | |
| 5957 @quotation | |
| 5958 This is problem specific to some Chips and Technologies video | |
| 5959 chips, when running XFree86. Putting | |
| 5960 | |
| 5961 @code{Option "sw_cursor"} | |
| 5962 | |
| 5963 in @file{XF86Config} gets rid of the problem. | |
| 5964 @end quotation | |
| 5965 | |
| 5966 @unnumberedsec 4.6: Scrollbars and Scrolling | |
| 5967 | |
| 5968 @node Q4.6.1, Q4.6.2, Q4.5.4, Display | |
| 5969 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar? | |
| 5970 | |
| 5971 To disable them for all frames, add the following line to | |
| 5972 your @file{.Xresources}: | |
| 5973 | |
| 5974 @example | |
| 5975 Emacs.scrollBarWidth: 0 | |
| 5976 @end example | |
| 5977 | |
| 5978 Or select @samp{Options->Display->Scrollbars}. | |
| 5979 Remember to save options. | |
| 5980 | |
| 5981 To turn the scrollbar off on a per-frame basis, use the following | |
| 5982 function: | |
| 5983 | |
| 5984 @lisp | |
| 5985 (set-specifier scrollbar-width 0 (selected-frame)) | |
| 5986 @end lisp | |
| 5987 | |
| 5988 You can actually turn the scrollbars on at any level you want by | |
| 5989 substituting for (selected-frame) in the above command. For example, to | |
| 5990 turn the scrollbars off only in a single buffer: | |
| 5991 | |
| 5992 @lisp | |
| 5993 (set-specifier scrollbar-width 0 (current-buffer)) | |
| 5994 @end lisp | |
| 5995 | |
| 5996 @node Q4.6.2, Q4.6.3, Q4.6.1, Display | |
| 5997 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width? | |
| 5998 | |
| 5999 #### Write me. | |
| 6000 | |
| 6001 @node Q4.6.3, Q4.6.4, Q4.6.2, Display | |
| 6002 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors? | |
| 6003 | |
| 6004 Here's a recap of how to use resources to change your scrollbar colors: | |
| 6005 | |
| 6006 @example | |
| 6007 ! Motif scrollbars | |
| 6008 | |
| 6009 Emacs*XmScrollBar.Background: skyblue | |
| 6010 Emacs*XmScrollBar.troughColor: lightgray | |
| 6011 | |
| 6012 ! Athena scrollbars | |
| 6013 | |
| 6014 Emacs*Scrollbar.Foreground: skyblue | |
| 6015 Emacs*Scrollbar.Background: lightgray | |
| 6016 @end example | |
| 6017 | |
| 6018 Note the capitalization of @code{Scrollbar} for the Athena widget. | |
| 6019 | |
| 6020 @node Q4.6.4, Q4.6.5, Q4.6.3, Display | |
| 6021 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this? | |
| 6022 | |
| 6023 When I move the scrollbar in an XEmacs window, it moves the point as | |
| 6024 well, which should not be the default behavior. Is this a bug or a | |
| 6025 feature? Can I disable it? | |
| 6026 | |
| 6027 The current behavior is a feature, not a bug. Point remains at the same | |
| 6028 buffer position as long as that position does not scroll off the screen. | |
| 6029 In that event, point will end up in either the upper-left or lower-left | |
| 6030 hand corner. | |
| 6031 | |
| 6032 This cannot be changed. | |
| 6033 | |
| 6034 @node Q4.6.5, Q4.6.6, Q4.6.4, Display | |
| 6035 @unnumberedsubsec Q4.6.5: Scrolling one line at a time. | |
| 6036 | |
| 6037 Can the cursor keys scroll the screen a line at a time, rather than the | |
| 6038 default half page jump? I tend it to find it disorienting. | |
| 6039 | |
| 6040 Use the following: | |
| 6041 | |
| 6042 @lisp | |
| 6043 (setq scroll-step 1) | |
| 6044 @end lisp | |
| 6045 | |
| 6046 You can also change this with Customize. Select from the | |
| 6047 @code{Options} menu | |
| 6048 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...} | |
| 6049 or type @kbd{M-x customize @key{RET} windows @key{RET}}. | |
| 6050 | |
| 6051 @node Q4.6.6, Q4.6.7, Q4.6.5, Display | |
| 6052 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes? | |
| 6053 | |
| 6054 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes | |
| 6055 in which you want lines truncated. | |
| 6056 | |
| 6057 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars | |
| 6058 will never appear. Otherwise, they will appear only if the value of | |
| 6059 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you | |
| 6060 do | |
| 6061 | |
| 6062 @lisp | |
| 6063 (set-specifier scrollbar-height 0) | |
| 6064 @end lisp | |
| 6065 | |
| 6066 then horizontal scrollbars will not appear in truncated buffers unless | |
| 6067 the package specifically asked for them. | |
| 6068 | |
| 6069 @node Q4.6.7, Q4.7.1, Q4.6.6, Display | |
| 6070 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off? | |
| 6071 | |
| 6072 @code{auto-show-mode} controls whether or not a horizontal scrollbar | |
| 6073 magically appears when a line is too long to be displayed. This is | |
| 6074 enabled by default. To turn it off, put the following in your | |
| 6075 @file{init.el}: | |
| 6076 | |
| 6077 @lisp | |
| 6078 (setq auto-show-mode nil) | |
| 6079 (setq-default auto-show-mode nil) | |
| 6080 @end lisp | |
| 6081 | |
| 6082 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 6083 | |
| 6084 @node Q4.7.1, Q4.7.2, Q4.6.7, Display | |
| 6085 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs? | |
| 6086 | |
| 6087 #### Write me. | |
| 6088 | |
| 6089 @node Q4.7.2, Q4.7.3, Q4.7.1, Display | |
| 6090 @unnumberedsubsec Q4.7.2: How can I disable the progress bar? | |
| 6091 | |
| 6092 #### Write me. | |
| 6093 | |
| 6094 @node Q4.7.3, Q4.7.4, Q4.7.2, Display | |
| 6095 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets. | |
| 6096 | |
| 6097 #### Write me. | |
| 6098 | |
| 6099 @node Q4.7.4, , Q4.7.3, Display | |
| 6100 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs? | |
| 6101 | |
| 6102 #### Write me. | |
| 6103 | |
| 6104 @node External Subsystems, Internet, Display, Top | |
| 6105 @unnumbered 5 Interfacing with the Operating System and External Devices | |
| 6106 | |
| 6107 This is part 5 of the XEmacs Frequently Asked Questions list. This | |
| 2417 | 6108 section is devoted to the various ways that XEmacs interfaces with the |
| 6109 operating system, with other processes and with external devices such | |
| 6110 as speakers and the printer. | |
| 428 | 6111 |
| 6112 @menu | |
| 2459 | 6113 5.0: X Window System and Resources |
| 6114 * Q5.0.1:: Where is a list of X resources? | |
| 6115 * Q5.0.2:: How can I detect a color display? | |
| 6116 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}? | |
| 6117 * Q5.0.4:: How can I have the window title area display the full path? | |
| 6118 * Q5.0.5:: @samp{xemacs -name junk} doesn't work? | |
| 6119 * Q5.0.6:: @samp{-iconic} doesn't work. | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6120 * Q5.0.7:: How can I use antialiased fonts under X11? |
| 2459 | 6121 |
| 6122 5.1: Microsoft Windows | |
| 6123 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? | |
| 6124 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 6125 | |
| 6126 5.2: Printing | |
| 6127 * Q5.2.1:: What do I need to change to make printing work? | |
| 6128 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer? | |
| 6129 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 6130 * Q5.2.4:: Can you print under MS Windows? | |
| 6131 | |
| 6132 5.3: Sound | |
| 6133 * Q5.3.1:: How do I turn off the sound? | |
| 6134 * Q5.3.2:: How do I get funky sounds instead of a boring beep? | |
| 6135 * Q5.3.3:: What are NAS and ESD (EsounD)? | |
| 6136 * Q5.3.4:: Sunsite sounds don't play. | |
| 6137 | |
| 6138 5.4: Running an Interior Shell, Invoking Subprocesses | |
| 6139 * Q5.4.1:: What is an interior shell? | |
| 6140 * Q5.4.2:: How do I start up a second shell buffer? | |
| 6141 * Q5.4.3:: Telnet from shell filters too much | |
| 6142 * Q5.4.4:: Strange things are happening in Shell Mode. | |
| 6143 * Q5.4.5:: XEmacs complains "No such file or directory, diff" | |
| 2995 | 6144 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed" |
| 2459 | 6145 |
| 6146 5.5: Multiple Device Support | |
| 6147 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display? | |
| 6148 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 6149 * Q5.5.3:: How do I disable gnuserv from opening a new frame? | |
| 6150 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 6151 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 428 | 6152 @end menu |
| 6153 | |
| 2459 | 6154 @unnumberedsec 5.0: X Window System and Resources |
| 6155 | |
| 6156 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems | |
| 6157 @unnumberedsubsec Q5.0.1: Where is a list of X resources? | |
| 2417 | 6158 |
| 6159 Search through the @file{NEWS} file for @samp{X Resources}. A fairly | |
| 6160 comprehensive list is given after it. | |
| 6161 | |
| 6162 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is | |
| 6163 supplied, listing the defaults. The file @file{etc/sample.Xresources} | |
| 6164 gives a different set of defaults that you might consider for | |
| 6165 installation in your @file{~/.Xresources} file. It is nearly the same | |
| 6166 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about | |
| 6167 installing the contents of this file into your @file{.Xresources} (or | |
| 6168 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well. | |
| 6169 | |
| 2459 | 6170 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems |
| 6171 @unnumberedsubsec Q5.0.2: How can I detect a color display? | |
| 2417 | 6172 |
| 6173 You can test the return value of the function @code{(device-class)}, as | |
| 6174 in: | |
| 6175 | |
| 6176 @lisp | |
| 6177 (when (eq (device-class) 'color) | |
| 6178 (set-face-foreground 'font-lock-comment-face "Grey") | |
| 6179 (set-face-foreground 'font-lock-string-face "Red") | |
| 6180 .... | |
| 6181 ) | |
| 6182 @end lisp | |
| 6183 | |
| 2459 | 6184 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems |
| 6185 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}? | |
| 2417 | 6186 |
| 6187 I'd like the icon to just say @samp{XEmacs}, and not include the name of | |
| 6188 the current file in it. | |
| 6189 | |
| 6190 Add the following line to your @file{init.el}: | |
| 6191 | |
| 6192 @lisp | |
| 6193 (setq frame-icon-title-format "XEmacs") | |
| 6194 @end lisp | |
| 6195 | |
| 2459 | 6196 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems |
| 6197 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path? | |
| 2417 | 6198 |
| 6199 I'd like to have the window title area display the full directory/name | |
| 6200 of the current buffer file and not just the name. | |
| 6201 | |
| 6202 Add the following line to your @file{init.el}: | |
| 6203 | |
| 6204 @lisp | |
| 6205 (setq frame-title-format "%S: %f") | |
| 6206 @end lisp | |
| 6207 | |
| 6208 A more sophisticated title might be: | |
| 6209 | |
| 6210 @lisp | |
| 6211 (setq frame-title-format | |
| 6212 '("%S: " (buffer-file-name "%f" | |
| 6213 (dired-directory dired-directory "%b")))) | |
| 6214 @end lisp | |
| 6215 | |
| 6216 That is, use the file name, or the dired-directory, or the buffer name. | |
| 6217 | |
| 2459 | 6218 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems |
| 6219 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work? | |
| 2417 | 6220 |
| 6221 When I run @samp{xterm -name junk}, I get an xterm whose class name | |
| 6222 according to xprop, is @samp{junk}. This is the way it's supposed to | |
| 6223 work, I think. When I run @samp{xemacs -name junk} the class name is | |
| 6224 not set to @samp{junk}. It's still @samp{emacs}. What does | |
| 6225 @samp{xemacs -name} really do? The reason I ask is that my window | |
| 6226 manager (fvwm) will make a window sticky and I use XEmacs to read my | |
| 6227 mail. I want that XEmacs window to be sticky, without having to use the | |
| 6228 window manager's function to set the window sticky. What gives? | |
| 6229 | |
| 6230 @samp{xemacs -name} sets the application name for the program (that is, | |
| 6231 the thing which normally comes from @samp{argv[0]}). Using @samp{-name} | |
| 6232 is the same as making a copy of the executable with that new name. The | |
| 6233 @code{WM_CLASS} property on each frame is set to the frame-name, and the | |
| 6234 application-class. So, if you did @samp{xemacs -name FOO} and then | |
| 6235 created a frame named @var{BAR}, you'd get an X window with WM_CLASS = | |
| 6236 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this | |
| 6237 widget would be: | |
| 6238 | |
| 6239 @example | |
| 6240 Name: FOO .shell .container .BAR | |
| 6241 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame | |
| 6242 @end example | |
| 6243 | |
| 6244 instead of the default | |
| 6245 | |
| 6246 @example | |
| 6247 Name: xemacs.shell .container .emacs | |
| 6248 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame | |
| 6249 @end example | |
| 6250 | |
| 6251 | |
| 6252 It is arguable that the first element of WM_CLASS should be set to the | |
| 6253 application-name instead of the frame-name, but I think that's less | |
| 6254 flexible, since it does not give you the ability to have multiple frames | |
| 6255 with different WM_CLASS properties. Another possibility would be for | |
| 6256 the default frame name to come from the application name instead of | |
| 6257 simply being @samp{emacs}. However, at this point, making that change | |
| 6258 would be troublesome: it would mean that many users would have to make | |
| 6259 yet another change to their resource files (since the default frame name | |
| 6260 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever | |
| 6261 the executable happened to be named), so we'd rather avoid it. | |
| 6262 | |
| 6263 To make a frame with a particular name use: | |
| 6264 | |
| 6265 @lisp | |
| 6266 (make-frame '((name . "the-name"))) | |
| 6267 @end lisp | |
| 6268 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6269 @node Q5.0.6, Q5.0.7, Q5.0.5, External Subsystems |
| 2459 | 6270 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work. |
| 2417 | 6271 |
| 6272 When I start up XEmacs using @samp{-iconic} it doesn't work right. | |
| 6273 Using @samp{-unmapped} on the command line, and setting the | |
| 6274 @code{initiallyUnmapped} X Resource don't seem to help much either... | |
| 6275 | |
| 6276 @email{ben@@xemacs.org, Ben Wing} writes: | |
| 6277 | |
| 6278 @quotation | |
| 6279 Ugh, this stuff is such an incredible mess that I've about given up | |
| 6280 getting it to work. The principal problem is numerous window-manager | |
| 6281 bugs... | |
| 6282 @end quotation | |
| 6283 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6284 @node Q5.0.7, Q5.1.1, Q5.0.6, External Subsystems |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6285 @unnumberedsubsec Q5.0.7: How can I use antialiased fonts under X11? |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6286 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6287 For this you need a recent beta version, and please consider the caveats |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6288 that apply when using beta software from any source. Rebuild xemacs |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6289 using at least the following options to configure: |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6290 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6291 @samp{./configure --enable-mule --with-xft=emacs,menubars} |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6292 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6293 For further details on the XEmacs widgets that support XFT, see the |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6294 output of @code{./configure --help}. You may find that you have to |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6295 install some lib[something]-dev packages to provide header files; see |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6296 your packaging system's documentation. Depending on your platform, your |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6297 packaging system will normally be something like RPM, @code{apt} or |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6298 DarwinPorts. |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6299 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6300 To specify a particular antialiased font, put something like the |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6301 following lines in your @file{~/.Xdefaults} or @file{~.Xresources} |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6302 (using @code{#define} in @file{.Xresources} avoids boring hand |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6303 substitution): |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6304 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6305 @example |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6306 #define MONO Mono |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6307 #define SANS Sans |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6308 #define PTSIZEM 12 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6309 #define PTSIZES 11 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6310 XEmacs.default.attributeFont: MONO:size=PTSIZEM |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6311 XEmacs.bold.attributeFont: MONO:size=PTSIZEM:style=Bold |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6312 XEmacs.italic.attributeFont: MONO:size=PTSIZEM:style=Oblique |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6313 XEmacs.bold-italic.attributeFont: MONO:size=PTSIZEM:style=Bold Oblique |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6314 XEmacs.modeline.attributeFont: SANS:size=PTSIZES |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6315 XEmacs.menubar.font: SANS:size=PTSIZES |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6316 XEmacs*xftFont: SANS:size=PTSIZES |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6317 @end example |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6318 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6319 And run @code{xrdb -merge} before starting the new, XFT-enabled xemacs. |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6320 You can choose the available fonts from the list given by |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6321 @code{fc-list}; try @code{xfd -fa FONTNAME-SIZE} to preview a given font. |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6322 |
| 2459 | 6323 @unnumberedsec 5.1: Microsoft Windows |
| 6324 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6325 @node Q5.1.1, Q5.1.2, Q5.0.7, External Subsystems |
| 2459 | 6326 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? |
| 2417 | 6327 |
| 6328 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*} | |
| 6329 symbols to @samp{w32-*}. Does XEmacs do the same? | |
| 6330 | |
| 6331 We consider such a move counter-productive, thus we do not use the | |
| 6332 @samp{w32} prefix. (His rather questionable justification was that he | |
| 6333 did not consider Windows to be a "winning" platform.) However, the name | |
| 6334 @samp{Win32} is not particularly descriptive outside the Windows world, | |
| 6335 and using just @samp{windows-} would be too generic. So we chose a | |
| 6336 compromise, the prefix @samp{mswindows-} for Windows-related variables | |
| 6337 and functions. | |
| 6338 | |
| 6339 Thus all the XEmacs variables and functions directly related to either | |
| 6340 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a | |
| 6341 couple of debugging variables, prefixed @samp{debug-mswindows-}). From | |
| 6342 an architectural perspective, however, we believe that this is mostly a | |
| 6343 non-issue because there should be a very small number of | |
| 6344 window-systems-specific variables anyway. Whenever possible, we try to | |
| 6345 provide generic interfaces that apply to all window systems. | |
| 6346 | |
| 6347 @c not true: | |
| 6348 @c The user variables | |
| 6349 @c that share functionality with existing NT Emacs variables are be named | |
| 6350 @c with our convention, but we provide the GNU Emacs names as | |
| 6351 @c compatibility aliases. | |
| 6352 | |
| 2459 | 6353 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems |
| 6354 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 2417 | 6355 |
| 6356 @unnumberedsubsubsec Associating a new file type with XEmacs. | |
| 6357 | |
| 6358 In Explorer select @samp{View->Options->File Types}, press @samp{[New | |
| 6359 Type...]} and fill in the dialog box, e.g.: | |
| 6360 | |
| 6361 @example | |
| 6362 Description of type: Emacs Lisp source | |
| 6363 Associated extension: el | |
| 6364 Content Type (MIME): text/plain | |
| 6365 @end example | |
| 6366 | |
| 6367 then press @samp{[New...]} and fill in the @samp{Action} dialog box as | |
| 6368 follows: | |
| 6369 | |
| 6370 @example | |
| 6371 Action: | |
| 6372 Open | |
| 6373 | |
| 6374 Application used to perform action: | |
| 6375 D:\Full\path\for\xemacs.exe "%1" | |
| 6376 | |
| 6377 [x] Use DDE | |
| 6378 | |
| 6379 DDE Message: | |
| 6380 open("%1") | |
| 6381 | |
| 6382 Application: | |
| 6383 <leave blank> | |
| 6384 | |
| 6385 DDE Application Not Running: | |
| 6386 <leave blank> | |
| 6387 | |
| 6388 Topic: | |
| 6389 <leave blank> | |
| 6390 @end example | |
| 6391 | |
| 6392 @unnumberedsubsubsec Associating an existing file type with XEmacs. | |
| 6393 | |
| 6394 In Explorer select @samp{View->Options->File Types}. Click on the file | |
| 6395 type in the list and press @samp{[Edit...]}. If the file type already | |
| 6396 has an @samp{Open} action, double click on it and fill in the | |
| 6397 @samp{Action} dialog box as described above; otherwise create a new | |
| 6398 action. | |
| 6399 | |
| 6400 If the file type has more than one action listed, you probably want to | |
| 6401 make the @samp{Open} action that you just edited the default by clicking on | |
| 6402 it and pressing @samp{Set Default}. | |
| 6403 | |
| 6404 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types} | |
| 6405 using @samp{Control Panel->Folder Options->File Types}. | |
| 6406 | |
| 2459 | 6407 @unnumberedsec 5.2: Printing |
| 6408 | |
| 6409 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems | |
| 6410 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work? | |
| 2417 | 6411 |
| 6412 For regular printing there are two variables that can be customized. | |
| 6413 | |
| 6414 @table @code | |
| 6415 @item lpr-command | |
| 6416 This should be set to a command that takes standard input and sends | |
| 6417 it to a printer. Something like: | |
| 6418 | |
| 6419 @lisp | |
| 6420 (setq lpr-command "lp") | |
| 6421 @end lisp | |
| 6422 | |
| 6423 @item lpr-switches | |
| 6424 This should be set to a list that contains whatever the print command | |
| 6425 requires to do its job. Something like: | |
| 6426 | |
| 6427 @lisp | |
| 6428 (setq lpr-switches '("-depson")) | |
| 6429 @end lisp | |
| 6430 @end table | |
| 6431 | |
| 6432 For postscript printing there are three analogous variables to | |
| 6433 customize. | |
| 6434 | |
| 6435 @table @code | |
| 6436 @item ps-lpr-command | |
| 6437 This should be set to a command that takes postscript on standard input | |
| 6438 and directs it to a postscript printer. | |
| 6439 | |
| 6440 @item ps-lpr-switches | |
| 6441 This should be set to a list of switches required for | |
| 6442 @code{ps-lpr-command} to do its job. | |
| 6443 | |
| 6444 @item ps-print-color-p | |
| 6445 This boolean variable should be set @code{t} if printing will be done in | |
| 6446 color, otherwise it should be set to @code{nil}. | |
| 6447 @end table | |
| 6448 | |
| 6449 NOTE: It is an undocumented limitation in XEmacs that postscript | |
| 6450 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a | |
| 6451 window system environment. It cannot be used outside of X11. | |
| 6452 | |
| 2459 | 6453 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems |
| 6454 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer? | |
| 2417 | 6455 |
| 6456 Font-lock looks nice. How can I print (WYSIWYG) the highlighted | |
| 6457 document? | |
| 6458 | |
| 6459 The package @code{ps-print}, which is now included with XEmacs, provides | |
| 6460 the ability to do this. The source code contains complete instructions | |
| 6461 on its use, in | |
| 6462 @file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el}, | |
| 6463 being the default location of an installed ps-print package. | |
| 6464 | |
| 2459 | 6465 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems |
| 6466 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 2417 | 6467 |
| 6468 My printer is a Postscript printer and @code{lpr} only works for | |
| 6469 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x | |
| 6470 lpr-buffer} to work? | |
| 6471 | |
| 6472 Put something like this in your @file{init.el}: | |
| 428 | 6473 |
| 6474 @lisp | |
| 2417 | 6475 (setq lpr-command "a2ps") |
| 6476 (setq lpr-switches '("-p" "-1")) | |
| 6477 @end lisp | |
| 6478 | |
| 6479 If you don't use a2ps to convert ASCII to postscript (why not, it's | |
| 6480 free?), replace with the command you do use. Note also that some | |
| 6481 versions of a2ps require a @samp{-Pprinter} to ensure spooling. | |
| 6482 | |
| 2459 | 6483 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems |
| 6484 @unnumberedsubsec Q5.2.4: Can you print under MS Windows? | |
| 2417 | 6485 |
| 6486 As of 21.4, printing works on Windows, using simply | |
| 6487 @samp{File->Print BUFFER...}, and can be configured with | |
| 6488 @samp{File->Page Setup...}. | |
| 6489 | |
| 6490 Prior to 21.4, there is no built-in support, but there are some clever | |
| 6491 hacks out there. If you know how, please let us know and we'll put it | |
| 6492 here. | |
| 6493 | |
| 2459 | 6494 @unnumberedsec 5.3: Sound |
| 6495 | |
| 6496 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems | |
| 6497 @unnumberedsubsec Q5.3.1: How do I turn off the sound? | |
| 2417 | 6498 |
| 6499 Add the following line to your @file{init.el}: | |
| 6500 | |
| 6501 @lisp | |
| 6502 (setq bell-volume 0) | |
| 6503 (setq sound-alist nil) | |
| 6504 @end lisp | |
| 6505 | |
| 6506 That will make your XEmacs totally silent---even the default ding sound | |
| 6507 (TTY beep on TTY-s) will be gone. | |
| 6508 | |
| 6509 You can also change these with Customize. Select from the | |
| 6510 @code{Options} menu @code{Advanced | |
| 6511 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x | |
| 6512 customize @key{RET} sound @key{RET}}. | |
| 6513 | |
| 6514 | |
| 2459 | 6515 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems |
| 6516 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep? | |
| 2417 | 6517 |
| 6518 Make sure your XEmacs was compiled with sound support, and then put this | |
| 6519 in your @file{init.el}: | |
| 6520 | |
| 6521 @lisp | |
| 6522 (load-default-sounds) | |
| 6523 @end lisp | |
| 6524 | |
| 2459 | 6525 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems |
| 6526 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)? | |
| 6527 | |
| 6528 @dfn{Network Audio System} (NAS) is a client-server sound library for X. | |
| 6529 | |
| 6530 @uref{http://radscan.com/nas.html}. | |
| 6531 | |
| 3018 | 6532 To build XEmacs with it, use the @file{configure} flag |
| 6533 @samp{--with-sound=nas} (@samp{--enable-sound=nas} in 21.5 or later). | |
| 2459 | 6534 |
| 6535 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system. | |
| 6536 | |
| 6537 @uref{http://www.tux.org/~ricdude/EsounD.html}. | |
| 6538 | |
| 3018 | 6539 To build XEmacs with it, use the @file{configure} flag |
| 6540 @samp{--with-sound=esd} (@samp{--enable-sound=esd} in 21.5 or later). | |
| 6541 | |
| 6542 You can specify support for both with a flag like | |
| 6543 @samp{--with-sound=nas,esd} (@samp{--enable-sound=nas,esd} in 21.5 or | |
| 6544 later). | |
| 2459 | 6545 |
| 6546 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems | |
| 6547 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play. | |
| 2417 | 6548 |
| 6549 I'm having some trouble with sounds I've downloaded from sunsite. They | |
| 6550 play when I run them through @code{showaudio} or cat them directly to | |
| 6551 @file{/dev/audio}, but XEmacs refuses to play them. | |
| 6552 | |
| 6553 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes: | |
| 6554 | |
| 6555 @quotation | |
| 6556 [Many of] These files have an (erroneous) 24byte header that tells about | |
| 6557 the format that they have been recorded in. If you cat them to | |
| 6558 @file{/dev/audio}, the header will be ignored and the default behavior | |
| 6559 for /dev/audio will be used. This happens to be 8kHz uLaw. It is | |
| 6560 probably possible to fix the header by piping through @code{sox} and | |
| 6561 passing explicit parameters for specifying the sampling format; you then | |
| 6562 need to perform a 'null' conversion from SunAudio to SunAudio. | |
| 6563 @end quotation | |
| 6564 | |
| 2459 | 6565 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses |
| 6566 | |
| 6567 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems | |
| 6568 @unnumberedsubsec Q5.4.1: What is an interior shell? | |
| 2417 | 6569 |
| 6570 #### Write me. | |
| 6571 | |
| 2459 | 6572 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems |
| 6573 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer? | |
| 2417 | 6574 |
| 6575 In the @code{*shell*} buffer: | |
| 6576 | |
| 6577 @lisp | |
| 6578 M-x rename-buffer @key{RET} *shell-1* @key{RET} | |
| 6579 M-x shell RET | |
| 6580 @end lisp | |
| 6581 | |
| 6582 This will then start a second shell. The key is that no buffer named | |
| 6583 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x | |
| 6584 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x | |
| 6585 rename-buffer}. | |
| 6586 | |
| 6587 Alternately, you can set the variable @code{shell-multiple-shells}. | |
| 6588 If the value of this variable is non-nil, each time shell mode is invoked, | |
| 6589 a new shell is made | |
| 6590 | |
| 2459 | 6591 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems |
| 6592 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much | |
| 2417 | 6593 |
| 6594 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke | |
| 6595 and use a telnet session within it. Everything works fine except that | |
| 6596 now all @samp{^M}'s are filtered out by Emacs. Fixes? | |
| 6597 | |
| 6598 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather | |
| 6599 than doing rsh or telnet within the local shell buffer. You can also | |
| 6600 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh} | |
| 6601 installed. | |
| 6602 | |
| 2459 | 6603 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems |
| 6604 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode. | |
| 2417 | 6605 |
| 6606 Sometimes (i.e. it's not repeatable, and I can't work out why it | |
| 6607 happens) when I'm typing into shell mode, I hit return and only a | |
| 6608 portion of the command is given to the shell, and a blank prompt is | |
| 6609 returned. If I hit return again, the rest of the previous command is | |
| 6610 given to the shell. | |
| 6611 | |
| 6612 @email{martin@@xemacs.org, Martin Buchholz} writes: | |
| 6613 | |
| 6614 @quotation | |
| 6615 There is a known problem with interaction between @code{csh} and the | |
| 6616 @code{filec} option and XEmacs. You should add the following to your | |
| 6617 @file{.cshrc}: | |
| 6618 | |
| 6619 @example | |
| 6620 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec | |
| 6621 @end example | |
| 6622 @end quotation | |
| 6623 | |
| 2995 | 6624 @node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems |
| 2459 | 6625 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff" |
| 2417 | 6626 |
| 6627 or "ispell" or other commands that seem related to whatever you just | |
| 6628 tried to do (M-x ediff or M-$, for example). | |
| 6629 | |
| 6630 There are a large number of common (in the sense that "everyone has | |
| 6631 these, they really do") Unix utilities that are not provided with | |
| 6632 XEmacs. The GNU Project's implementations are available for Windows in | |
| 6633 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also | |
| 6634 provides a complete Unix emulation environment (and thus makes ports of | |
| 6635 Unix utilities nearly trivial). Another implementation is that from | |
| 6636 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others, | |
| 6637 please let us know! | |
| 6638 | |
| 2995 | 6639 @node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems |
| 6640 @unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed" | |
| 6641 | |
| 6642 If you are getting an error like | |
| 6643 | |
| 6644 @example | |
| 6645 17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed, | |
| 6646 0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487 | |
| 6647 bash: fork: resource temporarily unavailable | |
| 6648 @end example | |
| 6649 | |
| 6650 when trying to run bash using @kbd{M-x shell}, then you need to rebase | |
| 6651 your Cygwin DLL's. This is a known problem with Cygwin. To fix: | |
| 6652 | |
| 6653 @enumerate | |
| 6654 @item | |
| 6655 Download the @file{rebase} utility from Cygwin setup (it's under | |
| 6656 @samp{System}). | |
| 6657 @item | |
| 6658 Kill @strong{all} of your Cygwin processes, including all of your | |
| 6659 shells and all background processes. Use @code{ps -a} to list all the | |
| 6660 processes you need to kill. | |
| 6661 @item | |
| 6662 From a DOS prompt, run @file{ash} (@strong{not} @file{bash}, | |
| 6663 @file{tcsh} or @file{zsh}). Do not try to be clever and @code{exec | |
| 6664 /bin/ash} from your last shell; it won't work. | |
| 6665 @item | |
| 6666 Type @code{/bin/rebaseall -v}. | |
| 6667 @end enumerate | |
| 6668 | |
| 6669 The problem should now be fixed -- at least, until you install another | |
| 6670 Cygwin package with DLL's, in which case you may have to repeat the | |
| 6671 procedure. | |
| 6672 | |
| 2459 | 6673 @unnumberedsec 5.5: Multiple Device Support |
| 6674 | |
| 2995 | 6675 @node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems |
| 2459 | 6676 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display? |
| 2417 | 6677 |
| 6678 Use the command @kbd{M-x make-frame-on-display}. This command is also | |
| 6679 on the File menu in the menubar. | |
| 6680 | |
| 6681 The command @code{make-frame-on-tty} also exists, which will establish a | |
| 6682 connection to any tty-like device. Opening the TTY devices should be | |
| 6683 left to @code{gnuclient}, though. | |
| 6684 | |
| 2459 | 6685 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems |
| 6686 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 6687 | |
| 6688 Yes. Use @code{gnuclient -nw}. | |
| 6689 | |
| 6690 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}. | |
| 6691 | |
| 6692 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems | |
| 6693 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame? | |
| 2417 | 6694 |
| 6695 If you set the @code{gnuserv-frame} variable to the frame that should be | |
| 6696 used to display buffers that are pulled up, a new frame will not be | |
| 6697 created. For example, you could put | |
| 6698 | |
| 6699 @lisp | |
| 6700 (setq gnuserv-frame (selected-frame)) | |
| 428 | 6701 @end lisp |
| 6702 | |
| 2417 | 6703 early on in your @file{init.el}, to ensure that the first frame created |
| 6704 is the one used for your gnuserv buffers. | |
| 6705 | |
| 6706 There is an option to set the gnuserv target to the current frame. See | |
| 6707 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target} | |
| 6708 | |
| 6709 You can also change this with Customize. Select from the | |
| 6710 @code{Options} menu @code{Advanced | |
| 6711 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type | |
| 6712 @kbd{M-x customize @key{RET} gnuserv @key{RET}}. | |
| 6713 | |
| 6714 | |
| 2459 | 6715 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems |
| 6716 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 2417 | 6717 |
| 6718 Put the following in your @file{init.el} file to start the server: | |
| 6719 | |
| 6720 @lisp | |
| 6721 (gnuserv-start) | |
| 6722 @end lisp | |
| 6723 | |
| 6724 Start your first XEmacs as usual. After that, you can do: | |
| 6725 | |
| 6726 @example | |
| 6727 gnuclient randomfilename | |
| 6728 @end example | |
| 6729 | |
| 6730 from the command line to get your existing XEmacs process to open a new | |
| 6731 frame and visit randomfilename in that window. When you're done editing | |
| 6732 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the | |
| 6733 frame. | |
| 6734 | |
| 6735 See also man page of gnuclient. | |
| 6736 | |
| 2459 | 6737 @node Q5.5.5, , Q5.5.4, External Subsystems |
| 6738 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 2417 | 6739 |
| 6740 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes: | |
| 6741 @quotation | |
| 6742 Here is one of the solutions, we have this in a script called | |
| 6743 @file{etc/editclient.sh}. | |
| 6744 @example | |
| 6745 #!/bin/sh | |
| 6746 if gnuclient -batch -eval t >/dev/null 2>&1 | |
| 6747 then | |
| 6748 exec gnuclient $@{1+"$@@"@} | |
| 6749 else | |
| 6750 xemacs -unmapped -f gnuserv-start & | |
| 6751 until gnuclient -batch -eval t >/dev/null 2>&1 | |
| 6752 do | |
| 6753 sleep 1 | |
| 6754 done | |
| 6755 exec gnuclient $@{1+"$@@"@} | |
| 6756 fi | |
| 6757 @end example | |
| 6758 | |
| 6759 Note that there is a known problem when running XEmacs and 'gnuclient | |
| 6760 -nw' on the same TTY. | |
| 6761 @end quotation | |
| 6762 | |
| 2459 | 6763 @node Internet, Advanced, External Subsystems, Top |
| 6764 @unnumbered 6 Connecting to the Internet | |
| 6765 | |
| 6766 This is part 6 of the XEmacs Frequently Asked Questions list. This | |
| 6767 section is devoted connecting to the Internet. | |
| 6768 | |
| 6769 @menu | |
| 6770 6.0: General Mail and News | |
| 6771 * Q6.0.1:: What are the various packages for reading mail? | |
| 6772 * Q6.0.2:: How can I send mail? | |
| 6773 * Q6.0.3:: How do I get my outgoing mail archived? | |
| 6774 * Q6.0.4:: How can I read and/or compose MIME messages? | |
| 6775 * Q6.0.5:: How do I customize the From line? | |
| 6776 * Q6.0.6:: How do I get my MUA to filter mail for me? | |
| 6777 * Q6.0.7:: Remote mail reading with an MUA. | |
| 6778 * Q6.0.8:: An MUA gets an error incorporating new mail. | |
| 6779 * Q6.0.9:: Why isn't @file{movemail} working? | |
| 6780 * Q6.0.10:: How do I make my MUA display graphical smilies? | |
| 6781 * Q6.0.11:: How can I get those oh-so-neat X-Face lines? | |
| 6782 | |
| 6783 6.1: Reading Mail with VM | |
| 6784 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP? | |
| 6785 * Q6.1.2:: How can I get VM to automatically check for new mail? | |
| 6786 * Q6.1.3:: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"? | |
| 6787 * Q6.1.4:: Is there a mailing list or FAQ for VM? | |
| 6788 * Q6.1.5:: How do I make VM stay in a single frame? | |
| 6789 * Q6.1.6:: Customization of VM not covered in the manual, or here. | |
| 6790 | |
| 6791 6.2: Reading Netnews and Mail with Gnus | |
| 6792 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 6793 * Q6.2.2:: How do I make Gnus stay within a single frame? | |
| 6794 | |
| 6795 6.3: FTP Access | |
| 6796 * Q6.3.1:: Can I edit files on other hosts? | |
| 6797 * Q6.3.2:: What is EFS? | |
| 6798 | |
| 6799 6.4: Web Browsing with W3 | |
| 6800 * Q6.4.1:: What is W3? | |
| 6801 * Q6.4.2:: How do I run W3 from behind a firewall? | |
| 6802 * Q6.4.3:: Is it true that W3 supports style sheets and tables? | |
| 6803 @end menu | |
| 6804 | |
| 6805 @unnumberedsec 6.0: General Mail and News | |
| 6806 | |
| 6807 @node Q6.0.1, Q6.0.2, Internet, Internet | |
| 6808 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail? | |
| 6809 | |
| 6810 #### Write me. | |
| 6811 | |
| 6812 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet | |
| 6813 @unnumberedsubsec Q6.0.2: How can I send mail? | |
| 6814 | |
| 6815 Under Unix and Mac OS X, the @samp{sendmail} package is normally used | |
| 6816 for this. | |
| 6817 #### Write me. | |
| 6818 | |
| 6819 Under Windows, you need to use @samp{smtpmail}, which communicates | |
| 6820 directly with the mail server, as there is no @file{sendmail} program | |
| 6821 running. To get it working, use code like the following in your | |
| 6822 @file{init.el} file: | |
| 6823 | |
| 6824 @lisp | |
| 6825 ;; Get mail working under Windows. | |
| 6826 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus | |
| 6827 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc. | |
| 6828 ;; the following ensures that mail problems can be debugged: it logs a trace | |
| 6829 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*. | |
| 6830 (setq smtpmail-debug-info t) | |
| 6831 ;; Substitute your info here. | |
| 6832 ;(setq user-mail-address "ben@@xemacs.org") | |
| 6833 ;(setq user-full-name "Ben Wing") | |
| 6834 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com") | |
| 6835 ;; The following two aren't completely necessary but may help. | |
| 6836 ;(setq smtpmail-local-domain "666.com") | |
| 6837 ;(setq smtpmail-sendto-domain "666.com") | |
| 6838 ;; If your SMTP server requires a username/password to authenticate, as | |
| 6839 ;; many do nowadays, set them like this: | |
| 6840 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo | |
| 6841 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD"))) | |
| 6842 | |
| 6843 ;; Other possibilities for getting smtpmail to work: | |
| 6844 ;; | |
| 6845 ;; If for some reason you need to authenticate using the STARTTLS protocol | |
| 6846 ;; (don't look into this unless you know what it is), use | |
| 6847 ;; (setq smtpmail-starttls-credentials | |
| 6848 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert"))) | |
| 6849 ;; Requires external program | |
| 6850 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz. | |
| 6851 ;; See http://www.ietf.org/rfc/rfc2246.txt, | |
| 6852 ;; http://www.ietf.org/rfc/rfc2487.txt | |
| 6853 @end lisp | |
| 6854 | |
| 6855 The lines you need to care about are those that set | |
| 6856 @code{user-mail-address}, @code{user-full-name}, | |
| 6857 @code{smtpmail-default-smtp-server}, and | |
| 6858 @code{smtpmail-auth-credentials}. You need to set these with, | |
| 6859 respectively, your email address, your full name, the SMTP server you | |
| 6860 use for outgoing mail, and the username and password you need to log | |
| 6861 in to your SMTP server. (If for some reason your SMTP server doesn't | |
| 6862 require logging in to send mail, don't uncomment this last line.) | |
| 6863 | |
| 6864 The other settings may be useful in specific cases, but you should know what | |
| 6865 you're doing before enabling them. | |
| 6866 | |
| 6867 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet | |
| 6868 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived? | |
| 6869 | |
| 6870 @lisp | |
| 6871 (setq mail-archive-file-name "~/outbox") | |
| 6872 @end lisp | |
| 6873 | |
| 6874 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet | |
| 6875 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages? | |
| 6876 | |
| 6877 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not | |
| 6878 have MIME support; refer to their documentation and other resources, | |
| 6879 such as web pages and mailing lists. Packages like SEMI/WEMI may be | |
| 6880 useful in connection with MUAs like mew and Wanderlust. | |
| 6881 | |
| 6882 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet | |
| 6883 @unnumberedsubsec Q6.0.5: How do I customize the From line? | |
| 6884 | |
| 6885 How do I change the @samp{From:} line? I have set gnus-user-from-line | |
| 6886 to | |
| 6887 @example | |
| 6888 Gail Gurman <gail.gurman@@sybase.com> | |
| 6889 @end example | |
| 6890 @noindent , but XEmacs Gnus doesn't use | |
| 6891 it. [This should apply to all MUA's. --ed] Instead it uses | |
| 6892 @example | |
| 6893 Gail Mara Gurman @email{gailg@@deall} | |
| 6894 @end example | |
| 6895 @noindent and then complains | |
| 6896 that it's incorrect. Also, as you perhaps can see, my Message-ID is | |
| 6897 screwy. How can I change that? | |
| 6898 | |
| 6899 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes: | |
| 6900 | |
| 6901 @quotation | |
| 6902 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or | |
| 6903 @code{mail-host-address} to @samp{sybase.com}. | |
| 6904 @end quotation | |
| 6905 | |
| 6906 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet | |
| 6907 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me? | |
| 6908 | |
| 6909 One possibility is to use procmail to split your mail before it gets to | |
| 6910 the MUA. I prefer this personally, since there are many strange and | |
| 6911 wonderful things one can do with procmail. Procmail may be found at | |
| 6912 @uref{http://www.procmail.org/}. | |
| 6913 | |
| 6914 Also see the Mail Filtering FAQ at: | |
| 6915 @iftex | |
| 6916 @* | |
| 6917 @end iftex | |
| 6918 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}. | |
| 6919 | |
| 6920 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet | |
| 6921 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA. | |
| 6922 | |
| 6923 My mailbox lives at the office on a big honkin server. My regular INBOX | |
| 6924 lives on my honkin desktop machine. I now can PPP to the office from | |
| 6925 home which is far from honking... I'd like to be able to read mail at | |
| 6926 home without storing it here and I'd like to use xemacs and the MUA at | |
| 6927 home... Is there a recommended setup? | |
| 6928 | |
| 6929 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes: | |
| 6930 | |
| 6931 @quotation | |
| 6932 There are several ways to do this. | |
| 6933 | |
| 6934 @enumerate | |
| 6935 @item | |
| 6936 Set your display to your home machine and run dxpc or one of the other X | |
| 6937 compressors. | |
| 6938 | |
| 6939 @item | |
| 6940 NFS mount your desktop machine on your home machine and modify your pop | |
| 6941 command on your home machine to rsh to your desktop machine and actually | |
| 6942 do the pop get's. | |
| 6943 | |
| 6944 @item | |
| 6945 Run a POP server on your desktop machine as well and do a sort of two | |
| 6946 tiered POP get. | |
| 6947 @end enumerate | |
| 6948 @end quotation | |
| 6949 | |
| 6950 @email{wmperry@@monolith.spry.com, William Perry} adds: | |
| 6951 | |
| 6952 @quotation | |
| 6953 Or you could run a pop script periodically on your desktop machine, and | |
| 6954 just use ange-ftp or NFS to get to your mailbox. I used to do this all | |
| 6955 the time back at IU. | |
| 6956 @end quotation | |
| 6957 | |
| 6958 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet | |
| 6959 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail. | |
| 6960 | |
| 6961 rmail and VM, and probably other MUA's as well, get new mail from | |
| 6962 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER} | |
| 6963 or something similar) using a program called @code{movemail}. | |
| 6964 This program interlocks with @code{/bin/mail} using the protocol | |
| 6965 defined by @code{/bin/mail}. | |
| 6966 | |
| 6967 There are various different protocols in general use, which you need to | |
| 3018 | 6968 specify using the @samp{--mail-locking} option |
| 6969 (@samp{--with-mail-locking} in 21.5 or later) to @file{configure}: | |
| 2459 | 6970 |
| 6971 @table @samp | |
| 6972 @item lockf | |
| 6973 POSIX file locking with @code{lockf()} | |
| 6974 @item flock | |
| 6975 BSD file locking with @code{flock()} | |
| 6976 @item dot | |
| 6977 To manipulate mail file @file{foo}, first create file @file{foo.lock} | |
| 6978 @item locking | |
| 6979 Use @code{locking()}, Microsoft's renamed @code{flock()} | |
| 6980 @item mmdf | |
| 6981 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel | |
| 6982 Memo Distribution Facility | |
| 6983 @item pop | |
| 6984 Retrieve mail using POP (the Post Office Protocol). This is the | |
| 6985 default for Cygwin/MinGW. | |
| 6986 @end table | |
| 6987 | |
| 6988 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR | |
| 6989 SYSTEM, YOU CAN LOSE MAIL!} | |
| 6990 | |
| 6991 Usually the value is correctly determined automatically: | |
| 6992 @file{configure} tries to detect the method in use, and defaults exist | |
| 6993 on systems for which this doesn't work. | |
| 6994 | |
| 6995 However, if you run into problems incorporating new mail, it may be | |
| 6996 because an incorrect method is being used. | |
| 6997 | |
| 6998 If your system uses the lock file protocol, and permissions are set | |
| 6999 so that ordinary users cannot write lock files in the mail spool | |
| 7000 directory, you may need to make @file{movemail} setgid to a | |
| 7001 suitable group such as @samp{mail}. You can use these commands (as | |
| 7002 root): | |
| 7003 | |
| 7004 @example | |
| 7005 chgrp mail movemail | |
| 7006 chmod 2755 movemail | |
| 7007 @end example | |
| 7008 | |
| 7009 If you are using the @samp{pop} locking method, @file{movemail} must | |
| 7010 be setuid root. | |
| 7011 | |
| 7012 Installation normally copies movemail from the build directory to an | |
| 7013 installation directory which is usually under @file{/usr/local/lib}. | |
| 7014 The installed copy of @file{movemail} is usually in the directory | |
| 7015 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example, | |
| 7016 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change | |
| 7017 the group and mode of the installed copy; changing the group and mode | |
| 7018 of the build directory copy is ineffective. | |
| 7019 | |
| 7020 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet | |
| 7021 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working? | |
| 7022 | |
| 7023 @xref{Q6.0.8}. | |
| 7024 | |
| 7025 Note also that older versions of Mozilla came with a @file{movemail} | |
| 7026 program that is @strong{not} compatible with XEmacs. Do not use it. | |
| 7027 Always use the @file{movemail} installed with your XEmacs. Failure to | |
| 7028 do so can result in lost mail. | |
| 7029 | |
| 7030 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet | |
| 7031 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies? | |
| 7032 For mh-e use the following: | |
| 7033 | |
| 7034 @lisp | |
| 7035 (add-hook 'mh-show-mode-hook '(lambda () | |
| 7036 (smiley-region (point-min) | |
| 7037 (point-max)))) | |
| 7038 @end lisp | |
| 7039 | |
| 7040 @email{bill@@carpenter.ORG, WJCarpenter} writes: | |
| 7041 For VM use the following: | |
| 7042 @lisp | |
| 7043 (autoload 'smiley-region "smiley" nil t) | |
| 7044 (add-hook 'vm-select-message-hook | |
| 7045 '(lambda () | |
| 7046 (smiley-region (point-min) | |
| 7047 (point-max)))) | |
| 7048 @end lisp | |
| 7049 | |
| 7050 For tm use the following: | |
| 7051 @lisp | |
| 7052 (autoload 'smiley-buffer "smiley" nil t) | |
| 7053 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer) | |
| 7054 @end lisp | |
| 7055 | |
| 7056 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet | |
| 7057 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines? | |
| 7058 | |
| 7059 Firstly there is an ftp site which describes X-faces and has the | |
| 7060 associated tools mentioned below, at | |
| 7061 @uref{http://ftp.cs.indiana.edu/pub/faces/}. | |
| 7062 | |
| 7063 Then the steps are | |
| 7064 | |
| 7065 @enumerate | |
| 7066 @item | |
| 7067 Create 48x48x1 bitmap with your favorite tool | |
| 7068 | |
| 7069 @item | |
| 7070 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc., | |
| 7071 and then compile the face. | |
| 7072 | |
| 7073 @item | |
| 7074 @example | |
| 7075 cat file.xbm | xbm2ikon |compface > file.face | |
| 7076 @end example | |
| 7077 | |
| 7078 @item | |
| 7079 Then be sure to quote things that are necessary for emacs strings: | |
| 7080 | |
| 7081 @example | |
| 7082 cat ./file.face | sed 's/\\/\\\\/g' | |
| 7083 @iftex | |
| 7084 \ @* | |
| 7085 @end iftex | |
| 7086 | sed 's/\"/\\\"/g' > ./file.face.quoted | |
| 7087 @end example | |
| 7088 | |
| 7089 @item | |
| 7090 Then set up emacs to include the file as a mail header - there were a | |
| 7091 couple of suggestions here---either something like: | |
| 7092 | |
| 7093 @lisp | |
| 7094 (setq mail-default-headers | |
| 7095 "X-Face: @email{Ugly looking text string here}") | |
| 7096 @end lisp | |
| 7097 | |
| 7098 Or, alternatively, as: | |
| 7099 | |
| 7100 @lisp | |
| 7101 (defun mail-insert-x-face () | |
| 7102 (save-excursion | |
| 7103 (goto-char (point-min)) | |
| 7104 (search-forward mail-header-separator) | |
| 7105 (beginning-of-line) | |
| 7106 (insert "X-Face:") | |
| 7107 (insert-file-contents "~/.face"))) | |
| 7108 | |
| 7109 (add-hook 'mail-setup-hook 'mail-insert-x-face) | |
| 7110 @end lisp | |
| 7111 @end enumerate | |
| 7112 | |
| 7113 However, 2 things might be wrong: | |
| 7114 | |
| 7115 Some versions of pbmtoicon produces some header lines that is not | |
| 7116 expected by the version of compface that I grabbed. So I found I had to | |
| 7117 include a @code{tail +3} in the pipeline like this: | |
| 7118 | |
| 7119 @example | |
| 7120 cat file.xbm | xbm2ikon | tail +3 |compface > file.face | |
| 7121 @end example | |
| 7122 | |
| 7123 Some people have also found that if one uses the @code{(insert-file)} | |
| 7124 method, one should NOT quote the face string using the sed script . | |
| 7125 | |
| 7126 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script | |
| 7127 xbm2face (included in the compface distribution at XEmacs.org) to do the | |
| 7128 conversion. | |
| 7129 | |
| 7130 Contributors for this item: | |
| 7131 | |
| 7132 Paul Emsley, | |
| 7133 Ricardo Marek, | |
| 7134 Amir J. Katz, | |
| 7135 Glen McCort, | |
| 7136 Heinz Uphoff, | |
| 7137 Peter Arius, | |
| 7138 Paul Harrison, and | |
| 7139 Vegard Vesterheim | |
| 7140 | |
| 7141 @unnumberedsec 6.1: Reading Mail with VM | |
| 7142 | |
| 7143 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet | |
| 7144 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP? | |
| 7145 | |
| 7146 Use @code{vm-spool-files}, like this for example: | |
| 7147 | |
| 7148 @lisp | |
| 7149 (setq vm-spool-files '("/var/spool/mail/wing" | |
| 7150 "netcom23.netcom.com:110:pass:wing:MYPASS")) | |
| 7151 @end lisp | |
| 7152 | |
| 7153 Of course substitute your actual password for MYPASS. | |
| 7154 | |
| 7155 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet | |
| 7156 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail? | |
| 7157 | |
| 7158 @email{turner@@lanl.gov, John Turner} writes: | |
| 7159 | |
| 7160 @quotation | |
| 7161 Use the following: | |
| 7162 | |
| 7163 @lisp | |
| 7164 (setq vm-auto-get-new-mail 60) | |
| 7165 @end lisp | |
| 7166 @end quotation | |
| 7167 | |
| 7168 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet | |
| 7169 @unnumberedsubsec Q6.1.3: I have various addresses at which I receive mail. How can I tell VM to ignore them when doing a "reply-all"? | |
| 7170 | |
| 7171 Set @code{vm-reply-ignored-addresses} to a list, like | |
| 7172 | |
| 7173 @lisp | |
| 7174 (setq vm-reply-ignored-addresses | |
| 7175 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com" | |
| 7176 "wing@@netcom.com" "wing@@xemacs.org")) | |
| 7177 @end lisp | |
| 7178 | |
| 7179 Note that each string is a regular expression. | |
| 7180 | |
| 7181 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet | |
| 7182 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM? | |
| 7183 | |
| 7184 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}. | |
| 7185 | |
| 7186 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug. | |
| 7187 | |
| 7188 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet | |
| 7189 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame? | |
| 7190 | |
| 7191 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes: | |
| 7192 | |
| 7193 @quotation | |
| 7194 @lisp | |
| 7195 ; Don't use multiple frames | |
| 7196 (setq vm-frame-per-composition nil) | |
| 7197 (setq vm-frame-per-folder nil) | |
| 7198 (setq vm-frame-per-edit nil) | |
| 7199 (setq vm-frame-per-summary nil) | |
| 7200 @end lisp | |
| 7201 @end quotation | |
| 7202 | |
| 7203 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet | |
| 7204 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here. | |
| 7205 | |
| 4311 | 7206 @email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} writes: |
| 2459 | 7207 |
| 7208 @quotation | |
| 7209 The meta-answer is to look into the file @file{vm-vars.el}, in the vm | |
| 7210 directory of the lisp library. | |
| 7211 | |
| 7212 @file{vm-vars.el} contains, initializes and carefully describes, with | |
| 7213 examples of usage, the plethora of user options that @emph{fully} | |
| 7214 control VM's behavior. | |
| 7215 | |
| 7216 Enter vm-vars, @code{forward-search} for toolbar, find the variables | |
| 7217 that control the toolbar placement, appearance, existence, copy to your | |
| 7218 @file{init.el} or @file{.vm} and modify according to the | |
| 7219 detailed instructions. | |
| 7220 | |
| 7221 The above also applies to all the various features of VM: search for | |
| 7222 some keywords, maybe the first you conjure isn't appropriate, find the | |
| 7223 appropriate variables, copy and experiment. | |
| 7224 @end quotation | |
| 7225 | |
| 7226 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus | |
| 7227 | |
| 7228 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet | |
| 7229 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 7230 | |
| 7231 The Gnus numbering issues are not meant for mere mortals to know them. | |
| 7232 If you feel you @emph{must} enter the muddy waters of Gnus, visit the | |
| 7233 excellent FAQ, maintained by Justin Sheehy, at: | |
| 7234 | |
| 7235 @example | |
| 7236 @uref{http://my.gnus.org/FAQ/} | |
| 7237 @end example | |
| 7238 | |
| 7239 See also Gnus home page | |
| 7240 @example | |
| 7241 @uref{http://www.gnus.org/} | |
| 7242 @end example | |
| 7243 | |
| 7244 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet | |
| 7245 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame? | |
| 7246 | |
| 7247 The toolbar code to start Gnus opens the new frame---and it's a feature | |
| 7248 rather than a bug. If you don't like it, but would still like to click | |
| 7249 on the seemly icon, use the following code: | |
| 7250 | |
| 7251 @lisp | |
| 7252 (defun toolbar-news () | |
| 7253 (gnus)) | |
| 7254 @end lisp | |
| 7255 | |
| 7256 It will redefine the callback function of the icon to just call | |
| 7257 @code{gnus}, without all the fancy frame stuff. | |
| 7258 | |
| 7259 @unnumberedsec 6.3: FTP Access | |
| 7260 | |
| 7261 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet | |
| 7262 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts? | |
| 7263 | |
| 7264 Yes. Of course XEmacs can use any network file system (such as NFS or | |
| 7265 Windows file sharing) you have available, and includes some | |
| 7266 optimizations and safety features appropriate to those environments. | |
| 7267 | |
| 7268 It is also possible to transparently edit files via FTP, ssh, or rsh. That | |
| 7269 is, XEmacs makes a local copy using the transport in the background, and | |
| 7270 automatically refreshes the remote original from that copy when you save | |
| 7271 it. XEmacs also is capable of doing file system manipulations like | |
| 7272 creating and removing directories and files. The FTP interface is | |
| 7273 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The | |
| 7274 ssh/rsh interface is provided by the optional @samp{tramp} package | |
| 7275 @ref{Top, TRAMP, , tramp}. | |
| 7276 | |
| 7277 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet | |
| 7278 @unnumberedsubsec Q6.3.2: What is EFS? | |
| 7279 | |
| 7280 #### Write me. | |
| 7281 | |
| 7282 @unnumberedsec 6.4: Web Browsing with W3 | |
| 7283 | |
| 7284 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet | |
| 7285 @unnumberedsubsec Q6.4.1: What is W3? | |
| 7286 | |
| 7287 W3 is an advanced graphical browser written in Emacs lisp that runs on | |
| 7288 XEmacs. It has full support for cascaded style sheets, and more... | |
| 7289 | |
| 7290 It has a home web page at | |
| 7291 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}. | |
| 7292 | |
| 7293 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet | |
| 7294 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall? | |
| 7295 | |
| 7296 There is a long, well-written, detailed section in the W3 manual that | |
| 7297 describes how to do this. Look in the section entitled "Firewalls". | |
| 7298 | |
| 7299 @node Q6.4.3, , Q6.4.2, Internet | |
| 7300 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables? | |
| 7301 | |
| 7302 Yes, and much more. W3, as distributed with the latest XEmacs is a | |
| 7303 full-featured web browser. | |
| 7304 | |
| 7305 @node Advanced, Other Packages, Internet, Top | |
| 7306 @unnumbered 7 Advanced Customization Using XEmacs Lisp | |
| 7307 | |
| 7308 This is part 7 of the XEmacs Frequently Asked Questions list. This | |
| 7309 section is devoted to advanced customization using XEmacs Lisp. | |
| 7310 | |
| 7311 @menu | |
| 2537 | 7312 7.0: Emacs Lisp and @file{init.el} |
| 7313 * Q7.0.1:: What version of Emacs am I running? | |
| 7314 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions? | |
| 7315 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. | |
| 7316 * Q7.0.4:: How can I add directories to the @code{load-path}? | |
| 7317 * Q7.0.5:: How to check if a lisp function is defined? | |
| 7318 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? | |
| 7319 | |
| 7320 7.1: Emacs Lisp Programming Techniques | |
| 7321 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 7322 * Q7.1.2:: Can I generate "fake" keyboard events? | |
| 7323 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? | |
| 7324 * Q7.1.4:: What is the performance hit of @code{let}? | |
| 7325 * Q7.1.5:: What is the recommended use of @code{setq}? | |
| 7326 * Q7.1.6:: What is the typical misuse of @code{setq}? | |
| 7327 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down? | |
| 7328 * Q7.1.8:: I like recursion, does it slow things down? | |
| 7329 * Q7.1.9:: How do I put a glyph as annotation in a buffer? | |
| 7330 * Q7.1.10:: @code{map-extents} won't traverse all of my extents! | |
| 7331 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 7332 | |
| 7333 7.2: Mathematics | |
| 7334 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp? | |
| 7335 * Q7.2.2:: XEmacs segfaults when I use very big numbers! | |
| 7336 * Q7.2.3:: Bignums are really slow! | |
| 7337 * Q7.2.4:: Equal bignums don't compare as equal! What gives? | |
| 2459 | 7338 @end menu |
| 7339 | |
| 2537 | 7340 @unnumberedsec 7.0: Emacs Lisp and @file{init.el} |
| 2459 | 7341 |
| 7342 @node Q7.0.1, Q7.0.2, Advanced, Advanced | |
| 2537 | 7343 @unnumberedsubsec Q7.0.1: What version of Emacs am I running? |
| 2459 | 7344 |
| 7345 How can @file{init.el} determine which of the family of | |
| 7346 Emacsen I am using? | |
| 7347 | |
| 7348 To determine if you are currently running GNU Emacs 18, GNU Emacs 19, | |
| 7349 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the | |
| 7350 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in | |
| 7351 XEmacs versions prior to 21.4). There are other nifty things in there | |
| 7352 as well! | |
| 7353 | |
| 7354 For all new code, all you really need to do is: | |
| 7355 | |
| 7356 @lisp | |
| 7357 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version)) | |
| 7358 @end lisp | |
| 7359 | |
| 2537 | 7360 @node Q7.0.2, Q7.0.3, Q7.0.1, Advanced |
| 7361 @unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions? | |
| 2459 | 7362 |
| 7363 I know I can evaluate Elisp expressions from @code{*scratch*} buffer | |
| 7364 with @kbd{C-j} after the expression. How do I do it from another | |
| 7365 buffer? | |
| 7366 | |
| 7367 Press @kbd{M-:} (the default binding of @code{eval-expression}), and | |
| 7368 enter the expression to the minibuffer. | |
| 7369 | |
| 2537 | 7370 @node Q7.0.3, Q7.0.4, Q7.0.2, Advanced |
| 7371 @unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly. | |
| 2459 | 7372 |
| 7373 If you put @code{(setq tab-width 6)} in your | |
| 7374 @file{init.el} file it does not work! Is there a reason | |
| 7375 for this? If you do it at the EVAL prompt it works fine!! How strange. | |
| 7376 | |
| 7377 Use @code{setq-default} instead, since @code{tab-width} is | |
| 7378 all-buffer-local. | |
| 7379 | |
| 2537 | 7380 @node Q7.0.4, Q7.0.5, Q7.0.3, Advanced |
| 7381 @unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}? | |
| 2459 | 7382 |
| 7383 Here are two ways to do that, one that puts your directories at the | |
| 7384 front of the load-path, the other at the end: | |
| 7385 | |
| 7386 @lisp | |
| 7387 ;;; Add things at the beginning of the load-path, do not add | |
| 7388 ;;; duplicate directories: | |
| 7389 (pushnew "bar" load-path :test 'equal) | |
| 7390 | |
| 7391 (pushnew "foo" load-path :test 'equal) | |
| 7392 | |
| 7393 ;;; Add things at the end, unconditionally | |
| 7394 (setq load-path (nconc load-path '("foo" "bar"))) | |
| 7395 @end lisp | |
| 7396 | |
| 4311 | 7397 @email{keithh@@nortel.ca, Keith (k.p.) Hanlan} writes: |
| 2459 | 7398 |
| 7399 @quotation | |
| 7400 To add directories using Unix shell metacharacters use | |
| 7401 @file{expand-file-name} like this: | |
| 7402 | |
| 7403 @lisp | |
| 7404 (push (expand-file-name "~keithh/.emacsdir") load-path) | |
| 7405 @end lisp | |
| 7406 @end quotation | |
| 7407 | |
| 2537 | 7408 @node Q7.0.5, Q7.0.6, Q7.0.4, Advanced |
| 7409 @unnumberedsubsec Q7.0.5: How to check if a lisp function is defined? | |
| 2459 | 7410 |
| 7411 Use the following elisp: | |
| 7412 | |
| 7413 @lisp | |
| 7414 (fboundp 'foo) | |
| 7415 @end lisp | |
| 7416 | |
| 7417 It's almost always a mistake to test @code{emacs-version} or any similar | |
| 7418 variables. | |
| 7419 | |
| 7420 Instead, use feature-tests, such as @code{featurep}, @code{boundp}, | |
| 7421 @code{fboundp}, or even simple behavioral tests, eg.: | |
| 7422 | |
| 7423 @lisp | |
| 7424 (defvar foo-old-losing-code-p | |
| 7425 (condition-case nil (progn (losing-code t) nil) | |
| 7426 (wrong-number-of-arguments t))) | |
| 7427 @end lisp | |
| 7428 | |
| 7429 There is an incredible amount of broken code out there which could work | |
| 7430 much better more often in more places if it did the above instead of | |
| 7431 trying to divine its environment from the value of one variable. | |
| 7432 | |
| 2537 | 7433 @node Q7.0.6, Q7.1.1, Q7.0.5, Advanced |
| 7434 @unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer? | |
| 2459 | 7435 |
| 7436 It would be good having it in a buffer, as the output of | |
| 7437 @code{(face-list)} is too wide to fit to a minibuffer. | |
| 7438 | |
| 7439 Evaluate the expression in the @samp{*scratch*} buffer with point after | |
| 7440 the rightmost paren and typing @kbd{C-j}. | |
| 7441 | |
| 7442 If the minibuffer smallness is the only problem you encounter, you can | |
| 7443 simply press @kbd{C-h l} to get the former minibuffer contents in a | |
| 7444 buffer. | |
| 7445 | |
| 2537 | 7446 @unnumberedsec 7.1: Emacs Lisp Programming Techniques |
| 7447 | |
| 7448 @node Q7.1.1, Q7.1.2, Q7.0.6, Advanced | |
| 7449 @unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 2459 | 7450 |
| 7451 @email{clerik@@naggum.no, Erik Naggum} writes; | |
| 7452 | |
| 7453 @quotation | |
| 7454 Emacs has a legacy of keyboards that produced characters with modifier | |
| 7455 bits, and therefore map a variety of input systems into this scheme even | |
| 7456 today. XEmacs is instead optimized for X events. This causes an | |
| 7457 incompatibility in the way key sequences are specified, but both Emacs | |
| 7458 and XEmacs will accept a key sequence as a vector of lists of modifiers | |
| 7459 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say | |
| 7460 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated | |
| 7461 form for a single key, just (meta control a). Emacs has an abbreviated | |
| 7462 form for the Control and the Meta modifiers to string-characters (the | |
| 7463 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware | |
| 7464 that the abbreviated form works only for one-character key sequences, | |
| 7465 while Emacs users need to be aware that the string-character is rather | |
| 7466 limited. Specifically, the string-character can accommodate only 256 | |
| 7467 different values, 128 of which have the Meta modifier and 128 of which | |
| 7468 have not. In each of these blocks, only 32 characters have the Control | |
| 7469 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta | |
| 7470 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A} | |
| 7471 do not. Programmers are advised to use the full common form, both | |
| 7472 because it is more readable and less error-prone, and because it is | |
| 7473 supported by both Emacsen. | |
| 7474 @end quotation | |
| 7475 | |
| 7476 Another (even safer) way to be sure of the key-sequences is to use the | |
| 7477 @code{read-kbd-macro} function, which takes a string like @samp{C-c | |
| 7478 <up>}, and converts it to the internal key representation of the Emacs | |
| 7479 you use. The function is available both on XEmacs and GNU Emacs. | |
| 7480 | |
| 2537 | 7481 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced |
| 7482 @unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events? | |
| 2459 | 7483 |
| 7484 I wonder if there is an interactive function that can generate | |
| 7485 @dfn{fake} keyboard events. This way, I could simply map them inside | |
| 7486 XEmacs. | |
| 7487 | |
| 7488 This seems to work: | |
| 7489 | |
| 7490 @lisp | |
| 7491 (defun cg--generate-char-event (ch) | |
| 7492 "Generate an event, as if ch has been typed" | |
| 7493 (dispatch-event (character-to-event ch))) | |
| 7494 | |
| 7495 ;; Backspace and Delete stuff | |
| 7496 (global-set-key [backspace] | |
| 7497 (lambda () (interactive) (cg--generate-char-event 127))) | |
| 7498 (global-set-key [unknown_keysym_0x4] | |
| 7499 (lambda () (interactive) (cg--generate-char-event 4))) | |
| 7500 @end lisp | |
| 7501 | |
| 2537 | 7502 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced |
| 7503 @unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail? | |
| 2459 | 7504 |
| 7505 The @code{read-kbd-macro} function returns the internal Emacs | |
| 7506 representation of a human-readable string (which is its argument). | |
| 7507 Thus: | |
| 7508 | |
| 7509 @lisp | |
| 7510 (read-kbd-macro "C-c C-a") | |
| 7511 @result{} [(control ?c) (control ?a)] | |
| 7512 | |
| 7513 (read-kbd-macro "C-c C-. <up>") | |
| 7514 @result{} [(control ?c) (control ?.) up] | |
| 7515 @end lisp | |
| 7516 | |
| 7517 In GNU Emacs the same forms will be evaluated to what GNU Emacs | |
| 7518 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3 | |
| 7519 67108910 up]}, respectively. | |
| 7520 | |
| 7521 The exact @dfn{human-readable} syntax is defined in the docstring of | |
| 7522 @code{edmacro-mode}. I'll repeat it here, for completeness. | |
| 7523 | |
| 7524 @quotation | |
| 7525 Format of keyboard macros during editing: | |
| 7526 | |
| 7527 Text is divided into @dfn{words} separated by whitespace. Except for | |
| 7528 the words described below, the characters of each word go directly as | |
| 7529 characters of the macro. The whitespace that separates words is | |
| 7530 ignored. Whitespace in the macro must be written explicitly, as in | |
| 7531 @kbd{foo @key{SPC} bar @key{RET}}. | |
| 7532 | |
| 7533 @itemize @bullet | |
| 7534 @item | |
| 7535 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD}, | |
| 7536 @kbd{ESC}, and @kbd{NUL} represent special control characters. The | |
| 7537 words must be written in uppercase. | |
| 7538 | |
| 7539 @item | |
| 7540 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or | |
| 7541 @code{<f1>}, represents a function key. (Note that in the standard | |
| 7542 configuration, the function key @code{<return>} and the control key | |
| 7543 @key{RET} are synonymous.) You can use angle brackets on the words | |
| 7544 @key{RET}, @key{SPC}, etc., but they are not required there. | |
| 7545 | |
| 7546 @item | |
| 7547 Keys can be written by their @sc{ascii} code, using a backslash followed | |
| 7548 by up to six octal digits. This is the only way to represent keys with | |
| 7549 codes above \377. | |
| 7550 | |
| 7551 @item | |
| 7552 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-} | |
| 7553 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may | |
| 7554 precede a character or key notation. For function keys, the prefixes | |
| 7555 may go inside or outside of the brackets: @code{C-<down>} @equiv{} | |
| 7556 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x} | |
| 7557 @equiv{} @kbd{C-M-x}. | |
| 7558 | |
| 7559 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except | |
| 7560 that the Meta prefix is allowed on a sequence of digits and optional | |
| 7561 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}. | |
| 7562 | |
| 7563 @item | |
| 7564 The @code{^} notation for control characters also works: @kbd{^M} | |
| 7565 @equiv{} @kbd{C-m}. | |
| 7566 | |
| 7567 @item | |
| 7568 Double angle brackets enclose command names: @code{<<next-line>>} is | |
| 7569 shorthand for @kbd{M-x next-line @key{RET}}. | |
| 7570 | |
| 7571 @item | |
| 7572 Finally, @code{REM} or @code{;;} causes the rest of the line to be | |
| 7573 ignored as a comment. | |
| 7574 @end itemize | |
| 7575 | |
| 7576 Any word may be prefixed by a multiplier in the form of a decimal number | |
| 7577 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>}, | |
| 7578 and @code{10*foo} @equiv{} | |
| 7579 @iftex | |
| 7580 @* | |
| 7581 @end iftex | |
| 7582 @code{foofoofoofoofoofoofoofoofoofoo}. | |
| 7583 | |
| 7584 Multiple text keys can normally be strung together to form a word, but | |
| 7585 you may need to add whitespace if the word would look like one of the | |
| 7586 above notations: @code{; ; ;} is a keyboard macro with three semicolons, | |
| 7587 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but | |
| 7588 @code{\123} is a single key written in octal, and @code{< right >} is | |
| 7589 seven keys but @code{<right>} is a single function key. When in doubt, | |
| 7590 use whitespace. | |
| 7591 @end quotation | |
| 7592 | |
| 2537 | 7593 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced |
| 7594 @unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}? | |
| 2459 | 7595 |
| 7596 In most cases, not noticeable. Besides, there's no avoiding | |
| 7597 @code{let}---you have to bind your local variables, after all. Some | |
| 7598 pose a question whether to nest @code{let}s, or use one @code{let} per | |
| 7599 function. I think because of clarity and maintenance (and possible | |
| 7600 future implementation), @code{let}-s should be used (nested) in a way to | |
| 7601 provide the clearest code. | |
| 7602 | |
| 2537 | 7603 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced |
| 7604 @unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}? | |
| 2459 | 7605 |
| 7606 @itemize @bullet | |
| 7607 @item Global variables | |
| 7608 | |
| 7609 You will typically @code{defvar} your global variable to a default | |
| 7610 value, and use @code{setq} to set it later. | |
| 7611 | |
| 7612 It is never a good practice to @code{setq} user variables (like | |
| 7613 @code{case-fold-search}, etc.), as it ignores the user's choice | |
| 7614 unconditionally. Note that @code{defvar} doesn't change the value of a | |
| 7615 variable if it was bound previously. If you wish to change a | |
| 7616 user-variable temporarily, use @code{let}: | |
| 7617 | |
| 7618 @lisp | |
| 7619 (let ((case-fold-search nil)) | |
| 7620 ... ; code with searches that must be case-sensitive | |
| 7621 ...) | |
| 7622 @end lisp | |
| 7623 | |
| 7624 You will notice the user-variables by their docstrings beginning with an | |
| 7625 asterisk (a convention). | |
| 7626 | |
| 7627 @item Local variables | |
| 7628 | |
| 7629 Bind them with @code{let}, which will unbind them (or restore their | |
| 7630 previous value, if they were bound) after exiting from the @code{let} | |
| 7631 form. Change the value of local variables with @code{setq} or whatever | |
| 7632 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form | |
| 7633 can even return one of its local variables. | |
| 7634 | |
| 7635 Typical usage: | |
| 7636 | |
| 7637 @lisp | |
| 7638 ;; iterate through the elements of the list returned by | |
| 7639 ;; `hairy-function-that-returns-list' | |
| 7640 (let ((l (hairy-function-that-returns-list))) | |
| 7641 (while l | |
| 7642 ... do something with (car l) ... | |
| 7643 (setq l (cdr l)))) | |
| 7644 @end lisp | |
| 7645 | |
| 7646 Another typical usage includes building a value simply to work with it. | |
| 7647 | |
| 7648 @lisp | |
| 7649 ;; Build the mode keymap out of the key-translation-alist | |
| 7650 (let ((inbox (file-truename (expand-file-name box))) | |
| 7651 (i 0)) | |
| 7652 ... code dealing with inbox ... | |
| 7653 inbox) | |
| 7654 @end lisp | |
| 7655 | |
| 7656 This piece of code uses the local variable @code{inbox}, which becomes | |
| 7657 unbound (or regains old value) after exiting the form. The form also | |
| 7658 returns the value of @code{inbox}, which can be reused, for instance: | |
| 7659 | |
| 7660 @lisp | |
| 7661 (setq foo-processed-inbox | |
| 7662 (let .....)) | |
| 7663 @end lisp | |
| 7664 @end itemize | |
| 7665 | |
| 2537 | 7666 @node Q7.1.6, Q7.1.7, Q7.1.5, Advanced |
| 7667 @unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}? | |
| 2459 | 7668 |
| 7669 A typical misuse is probably @code{setq}ing a variable that was meant to | |
| 7670 be local. Such a variable will remain bound forever, never to be | |
| 7671 garbage-collected. For example, the code doing: | |
| 7672 | |
| 7673 @lisp | |
| 7674 (defun my-function (whatever) | |
| 7675 (setq a nil) | |
| 7676 ... build a large list ... | |
| 7677 ... and exit ...) | |
| 7678 @end lisp | |
| 7679 | |
| 7680 does a bad thing, as @code{a} will keep consuming memory, never to be | |
| 7681 unbound. The correct thing is to do it like this: | |
| 7682 | |
| 7683 @lisp | |
| 7684 (defun my-function (whatever) | |
| 7685 (let (a) ; default initialization is to nil | |
| 7686 ... build a large list ... | |
| 7687 ... and exit, unbinding `a' in the process ...) | |
| 7688 @end lisp | |
| 7689 | |
| 7690 Not only is this prettier syntactically, but it makes it possible for | |
| 7691 Emacs to garbage-collect the objects which @code{a} used to reference. | |
| 7692 | |
| 7693 Note that even global variables should not be @code{setq}ed without | |
| 7694 @code{defvar}ing them first, because the byte-compiler issues warnings. | |
| 7695 The reason for the warning is the following: | |
| 7696 | |
| 7697 @lisp | |
| 7698 (defun flurgoze nil) ; ok, global internal variable | |
| 7699 ... | |
| 7700 | |
| 7701 (setq flurghoze t) ; ops! a typo, but semantically correct. | |
| 7702 ; however, the byte-compiler warns. | |
| 7703 | |
| 7704 While compiling toplevel forms: | |
| 7705 ** assignment to free variable flurghoze | |
| 7706 @end lisp | |
| 7707 | |
| 2537 | 7708 @node Q7.1.7, Q7.1.8, Q7.1.6, Advanced |
| 7709 @unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down? | |
| 2459 | 7710 |
| 7711 It shouldn't. Here is what Dave Gillespie has to say about cl.el | |
| 7712 performance: | |
| 7713 | |
| 7714 @quotation | |
| 7715 Many of the advanced features of this package, such as @code{defun*}, | |
| 7716 @code{loop}, and @code{setf}, are implemented as Lisp macros. In | |
| 7717 byte-compiled code, these complex notations will be expanded into | |
| 7718 equivalent Lisp code which is simple and efficient. For example, the | |
| 7719 forms | |
| 7720 | |
| 7721 @lisp | |
| 7722 (incf i n) | |
| 7723 (push x (car p)) | |
| 7724 @end lisp | |
| 7725 | |
| 7726 are expanded at compile-time to the Lisp forms | |
| 7727 | |
| 7728 @lisp | |
| 7729 (setq i (+ i n)) | |
| 7730 (setcar p (cons x (car p))) | |
| 7731 @end lisp | |
| 7732 | |
| 7733 which are the most efficient ways of doing these respective operations | |
| 7734 in Lisp. Thus, there is no performance penalty for using the more | |
| 7735 readable @code{incf} and @code{push} forms in your compiled code. | |
| 7736 | |
| 7737 @emph{Interpreted} code, on the other hand, must expand these macros | |
| 7738 every time they are executed. For this reason it is strongly | |
| 7739 recommended that code making heavy use of macros be compiled. (The | |
| 7740 features labelled @dfn{Special Form} instead of @dfn{Function} in this | |
| 7741 manual are macros.) A loop using @code{incf} a hundred times will | |
| 7742 execute considerably faster if compiled, and will also garbage-collect | |
| 7743 less because the macro expansion will not have to be generated, used, | |
| 7744 and thrown away a hundred times. | |
| 7745 | |
| 7746 You can find out how a macro expands by using the @code{cl-prettyexpand} | |
| 7747 function. | |
| 7748 @end quotation | |
| 7749 | |
| 2537 | 7750 @node Q7.1.8, Q7.1.9, Q7.1.7, Advanced |
| 7751 @unnumberedsubsec Q7.1.8: I like recursion, does it slow things down? | |
| 2459 | 7752 |
| 7753 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But | |
| 7754 think well whether this is a real concern in Emacs. Much of the Emacs | |
| 7755 slowness comes from internal mechanisms such as redisplay, or from the | |
| 7756 fact that it is an interpreter. | |
| 7757 | |
| 7758 Please try not to make your code much uglier to gain a very small speed | |
| 7759 gain. It's not usually worth it. | |
| 7760 | |
| 2537 | 7761 @node Q7.1.9, Q7.1.10, Q7.1.8, Advanced |
| 7762 @unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer? | |
| 2459 | 7763 |
| 7764 Here is a solution that will insert the glyph annotation at the | |
| 7765 beginning of buffer: | |
| 7766 | |
| 7767 @lisp | |
| 7768 (make-annotation (make-glyph '([FORMAT :file FILE] | |
| 7769 [string :data "fallback-text"])) | |
| 7770 (point-min) | |
| 7771 'text | |
| 7772 (current-buffer)) | |
| 7773 @end lisp | |
| 7774 | |
| 7775 Replace @samp{FORMAT} with an unquoted symbol representing the format of | |
| 7776 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.) | |
| 7777 Instead of @samp{FILE}, use the image file name | |
| 7778 (e.g. | |
| 7779 @iftex | |
| 7780 @* | |
| 7781 @end iftex | |
| 7782 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}). | |
| 7783 | |
| 7784 You can turn this to a function (that optionally prompts you for a file | |
| 7785 name), and inserts the glyph at @code{(point)} instead of | |
| 7786 @code{(point-min)}. | |
| 7787 | |
| 2537 | 7788 @node Q7.1.10, Q7.1.11, Q7.1.9, Advanced |
| 7789 @unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents! | |
| 2459 | 7790 |
| 7791 I tried to use @code{map-extents} to do an operation on all the extents | |
| 7792 in a region. However, it seems to quit after processing a random number | |
| 7793 of extents. Is it buggy? | |
| 7794 | |
| 7795 No. The documentation of @code{map-extents} states that it will iterate | |
| 7796 across the extents as long as @var{function} returns @code{nil}. | |
| 7797 Unexperienced programmers often forget to return @code{nil} explicitly, | |
| 7798 which results in buggy code. For instance, the following code is | |
| 7799 supposed to delete all the extents in a buffer, and issue as many | |
| 7800 @samp{fubar!} messages. | |
| 7801 | |
| 7802 @lisp | |
| 7803 (map-extents (lambda (ext ignore) | |
| 7804 (delete-extent ext) | |
| 7805 (message "fubar!"))) | |
| 7806 @end lisp | |
| 7807 | |
| 7808 Instead, it will delete only the first extent, and stop right there -- | |
| 7809 because @code{message} will return a non-nil value. The correct code | |
| 7810 is: | |
| 7811 | |
| 7812 @lisp | |
| 7813 (map-extents (lambda (ext ignore) | |
| 7814 (delete-extent ext) | |
| 7815 (message "fubar!") | |
| 7816 nil)) | |
| 7817 @end lisp | |
| 7818 | |
| 2537 | 7819 @node Q7.1.11, Q7.2.1, Q7.1.10, Advanced |
| 7820 @unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 2459 | 7821 @c New |
| 7822 | |
| 7823 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes: | |
| 7824 @quotation | |
| 7825 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence}, | |
| 7826 press a key (say @key{RET} in the Gnus Group buffer), and get the | |
| 7827 results using @kbd{M-x profile-results}. It should give you an idea of | |
| 7828 where the time is being spent. | |
| 7829 @end quotation | |
| 7830 | |
| 2537 | 7831 @unnumberedsec 7.2: Mathematics |
| 7832 | |
| 7833 @node Q7.2.1, Q7.2.2, Q7.1.11, Advanced | |
| 7834 @unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp? | |
| 2459 | 7835 |
| 7836 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and | |
| 7837 later can use the capabilities of multiple-precision libraries that may | |
| 7838 be available for your platform. The GNU Multiple Precision (GMP) and | |
| 7839 BSD Multiple Precision (MP) libraries are partially supported. GMP | |
| 7840 gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios} | |
| 7841 (arbitrary precision fractions), and @dfn{bigfloats} (arbitrary | |
| 7842 precision floating point numbers). GNU MP is better-supported by XEmacs | |
| 7843 at the time of writing (2004-04-06). BSD MP support does not include | |
| 7844 ratios or bigfloats, and it throws errors that aren't understood. | |
| 7845 | |
| 7846 In most cases, bignum support should be transparent to users and Lisp | |
| 7847 programmers. A bignum-enabled XEmacs will automatically convert from | |
| 7848 fixnums to bignums and back in pure integer arithmetic, and for GNU MP, | |
| 7849 from floats to bigfloats. (Bigfloats must be explicitly coerced to | |
| 7850 other types, even if they are exactly representable by less precise | |
| 7851 types.) The Lisp reader and printer have been enhanced to handle | |
| 7852 bignums, as have the mathematical functions. Rationals (fixnums, | |
| 7853 bignums, and ratios) are printed using the @samp{%d}, @samp{%o}, | |
| 7854 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios | |
| 7855 is @samp{3/5}. | |
| 7856 | |
| 7857 User-visible changes in behavior include (in probable order of annoyance) | |
| 7858 | |
| 7859 @itemize | |
| 7860 @item | |
| 7861 Arithmetic can cause a segfault, depending on your MP library | |
| 2537 | 7862 @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. |
| 2459 | 7863 |
| 7864 @item | |
| 7865 Terminology is not Common-Lisp-conforming. For example, ``integer'' for | |
| 7866 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being | |
| 7867 investigated, but the use of ``integer'' for fixnum is pervasive and may | |
| 7868 cause backward-compatibility and GNU-Emacs-compatibility problems. | |
| 7869 | |
| 7870 @item | |
| 7871 Many operations that used to cause a range error now succeed, with | |
| 7872 intermediate results and return values coerced to bignums as needed. | |
| 7873 | |
| 7874 @item | |
| 7875 An atom with ratio read syntax now returns a number, not a symbol. | |
| 7876 | |
| 7877 @item | |
| 7878 The @samp{%u} format conversion will now give an error if its argument | |
| 7879 is negative. (Without MP, it prints a number which Lisp can't read.) | |
| 7880 @end itemize | |
| 7881 | |
| 7882 @emph{Surgeon General's Warning}: The automatic conversions cannot be | |
| 7883 disabled at runtime. New functions have been added which produce | |
| 7884 ratios, so there should be few surprises with type conflicts, but they | |
| 7885 can't be ruled out. ``Arbitrary'' precision means precisely what it | |
| 7886 says. If you work with extremely large numbers, your machine may | |
| 7887 arbitrarily decide to hand you an unpleasant surprise rather than a | |
| 2537 | 7888 bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. |
| 2459 | 7889 |
| 3018 | 7890 To configure with GNU MP, add @samp{--use-number-lib=gmp} |
| 7891 (@samp{--enable-bignum=gmp} in 21.5 or later) to your invocation of | |
| 7892 @file{configure}. For BSD MP, use @samp{--use-number-lib=mp} | |
| 7893 (@samp{--enable-bignum=mp} for 21.5). | |
| 2459 | 7894 |
| 7895 If you would like to help with bignum support, especially on BSD MP, | |
| 7896 please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta, | |
| 7897 XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and | |
| 7898 @file{number-mp.h}. Jerry has promised to write internals documentation | |
| 7899 eventually, but if your skills run more to analysis and documentation | |
| 7900 than to writing new code, feel free to fill in the gap! | |
| 7901 | |
| 7902 | |
| 2537 | 7903 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced |
| 7904 @unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers! | |
| 2459 | 7905 |
| 7906 GMP by default allocates temporaries on the stack. If you run out of | |
| 7907 stack space, you're dead; there is no way that we know of to reliably | |
| 7908 detect this condition, because @samp{alloca} is typically implemented to | |
| 7909 be @emph{fast} rather than robust. If you just need a little more | |
| 7910 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in | |
| 7911 bash(1)). If you want robustness at the cost of speed, configure GMP | |
| 7912 with @samp{--disable-alloca} and rebuild the GMP library. | |
| 7913 | |
| 7914 We do not know whether BSD MP uses @samp{alloca} or not. Please send | |
| 7915 any information you have as a bug report (@kbd{M-x report-xemacs-bug | |
| 7916 @key{RET}}), which will give us platform information. (We do know that | |
| 7917 BSD MP implementations vary across vendors, but how much, we do not know | |
| 7918 yet.) | |
| 7919 | |
| 7920 | |
| 2537 | 7921 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced |
| 7922 @unnumberedsubsec Q7.2.3: Bignums are really slow! | |
| 2459 | 7923 |
| 7924 Many Linux distributions compile all their packages for the i386, and | |
| 7925 this is costly. An optimized version can give you two or three orders | |
| 7926 of magnitude better performance for a Pentium III or IV. (Yes, really. | |
| 7927 See @uref{http://www.swox.com/gmp/gmp-speed.html}.) | |
| 7928 | |
| 7929 | |
| 2537 | 7930 @node Q7.2.4, , Q7.2.3, Advanced |
| 7931 @unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives? | |
| 2459 | 7932 |
| 7933 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva | |
| 7934 CLTL2 warned of the illusion that equal numbers would be @samp{eq}! | |
| 7935 Meditate on the deeper truths of @samp{eql}, in which numbers of the same | |
| 7936 type which have equal values compare equal, and @samp{=}, which does any | |
| 7937 necessary type coercions before comparing for equality. | |
| 7938 | |
| 7939 Yeah, yeah, it has always worked for integer types, because fixnums and | |
| 7940 characters have an immediate representation. Sorry about that; | |
| 7941 arbitrary precision obviously requires consing new objects because the | |
| 7942 objects are ``large'' and of variable size, and the definition of | |
| 7943 @samp{eq} does not permit different objects to compare as equal. | |
| 7944 | |
| 7945 @node Other Packages, Current Events, Advanced, Top | |
| 7946 @unnumbered 8 Other External Packages | |
| 7947 | |
| 7948 This is part 8 of the XEmacs Frequently Asked Questions list. This | |
| 7949 section is devoted to miscellaneous external packages not covered | |
| 7950 elsewhere in XEmacs. | |
| 7951 | |
| 7952 @menu | |
| 2537 | 7953 8.0: TeX |
| 2459 | 7954 * Q8.0.1:: Is there something better than LaTeX mode? |
| 7955 * Q8.0.2:: What is AUCTeX? Where do you get it? | |
| 7956 * Q8.0.3:: Problems installing AUCTeX. | |
| 7957 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline? | |
| 7958 | |
| 7959 8.1: Other Unbundled Packages | |
| 7960 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 7961 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets? | |
| 7962 * Q8.1.3:: Is there a MatLab mode? | |
| 7963 | |
| 7964 8.2: Environments Built Around XEmacs | |
| 7965 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop? | |
| 7966 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21? | |
| 7967 * Q8.2.3:: What is/was Energize? | |
| 7968 * Q8.2.4:: What is Infodock? | |
| 7969 @end menu | |
| 7970 | |
| 7971 @unnumberedsec 8.0: TeX | |
| 7972 | |
| 7973 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages | |
| 7974 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode? | |
| 2417 | 7975 |
| 7976 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes: | |
| 7977 | |
| 7978 @quotation | |
| 7979 The standard TeX modes leave much to be desired, and are somewhat | |
| 2459 | 7980 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2, |
| 2417 | 7981 What is AUCTeX? Where do you get it?}). |
| 7982 @end quotation | |
| 7983 | |
| 2459 | 7984 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages |
| 7985 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it? | |
| 2417 | 7986 |
| 7987 AUCTeX is a complex and sophisticated editing package dedicated to TeX | |
| 7988 and related text formatting languages, including LaTeX and Texinfo. | |
| 7989 It provides support for running TeX on a file or part of a file, | |
| 7990 include files, and of course shortcuts for entering common TeX macros, | |
| 7991 LaTeX environments, etc, and for fontlock. | |
| 7992 | |
| 7993 AUCTeX is a standard package provided by XEmacs. You can get it as | |
| 7994 usual through the @kbd{M-x list-packages} interface. It is also | |
| 7995 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is | |
| 7996 maintained by Uwe Brauer <GET MAIL ADDRESS>. | |
| 7997 | |
| 7998 AUCTeX is extremely complicated, and its developers primarily | |
| 7999 use GNU Emacs. Not all features of the bleeding edge version | |
| 8000 of AUCTeX are immediately ported to XEmacs; if you need | |
| 8001 these, you may be better off getting the most recent versions | |
| 8002 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}. | |
| 8003 | |
| 2459 | 8004 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages |
| 8005 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX. | |
| 2417 | 8006 |
| 8007 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes: | |
| 8008 | |
| 8009 @quotation | |
| 8010 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for | |
| 8011 a very very long time. This is mostly due to the work of | |
| 8012 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu} | |
| 8013 package. Which leads to what is probably the problem... | |
| 8014 @end quotation | |
| 8015 | |
| 8016 Most problems with AUCTeX are one of two things: | |
| 8017 | |
| 8018 @itemize @bullet | |
| 8019 @item | |
| 8020 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't | |
| 8021 match. | |
| 8022 | |
| 8023 Fix: make sure you configure AUCTeX properly @strong{before} installing. | |
| 8024 | |
| 8025 @item | |
| 8026 You have an old version of easymenu.el in your path. | |
| 8027 | |
| 8028 Fix: use @code{locate-library} and remove old versions to make sure it | |
| 8029 @strong{only} finds the one that came with XEmacs. | |
| 8030 @end itemize | |
| 8031 | |
| 2459 | 8032 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages |
| 8033 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline? | |
| 2417 | 8034 |
| 8035 With AUCTeX, fast typing is hard because the current chapter, section | |
| 8036 etc. are given in the modeline. How can I turn this off? | |
| 8037 | |
| 8038 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}. | |
| 8039 | |
| 8040 @c Add this code to your @file{init.el} to turn it off: | |
| 8041 @c | |
| 8042 @c @lisp | |
| 8043 @c (setq fume-display-in-modeline-p nil) | |
| 8044 @c @end lisp | |
| 8045 @c | |
| 8046 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX | |
| 8047 @c mode: | |
| 8048 @c | |
| 8049 @c @lisp | |
| 8050 @c (add-hook 'TeX-mode-hook | |
| 8051 @c '(lambda () (setq fume-display-in-modeline-p nil))) | |
| 8052 @c @end lisp | |
| 8053 @c | |
| 8054 @email{dhughes@@origin-at.co.uk, David Hughes} writes: | |
| 8055 | |
| 8056 @quotation | |
| 8057 Try this; you'll still get the function name displayed in the modeline, | |
| 8058 but it won't attempt to keep track when you modify the file. To refresh | |
| 8059 when it gets out of synch, you simply need click on the @samp{Rescan | |
| 8060 Buffer} option in the function-menu. | |
| 8061 | |
| 8062 @lisp | |
| 8063 (setq-default fume-auto-rescan-buffer-p nil) | |
| 8064 @end lisp | |
| 8065 @end quotation | |
| 8066 | |
| 2459 | 8067 @unnumberedsec 8.1: Other Unbundled Packages |
| 8068 | |
| 8069 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages | |
| 8070 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 2417 | 8071 |
| 8072 The reason for an Emacs package not to be included in XEmacs is | |
| 8073 usually one or more of the following: | |
| 8074 | |
| 8075 @enumerate | |
| 8076 @item | |
| 8077 The package has not been ported to XEmacs. This will typically happen | |
| 8078 when it uses GNU-Emacs-specific features, which make it fail under | |
| 8079 XEmacs. | |
| 8080 | |
| 8081 Porting a package to XEmacs can range from a trivial amount of change to | |
| 8082 a partial or full rewrite. Fortunately, the authors of modern packages | |
| 8083 usually choose to support both Emacsen themselves. | |
| 8084 | |
| 8085 @item | |
| 8086 The package has been decided not to be appropriate for XEmacs. It may | |
| 8087 have an equivalent or better replacement within XEmacs, in which case | |
| 8088 the developers may choose not to burden themselves with supporting an | |
| 8089 additional package. | |
| 8090 | |
| 8091 Each package bundled with XEmacs means more work for the maintainers, | |
| 8092 whether they want it or not. If you are ready to take over the | |
| 8093 maintenance responsibilities for the package you port, be sure to say | |
| 8094 so---we will more likely include it. | |
| 8095 | |
| 8096 @item | |
| 8097 The package simply hasn't been noted by the XEmacs development. If | |
| 8098 that's the case, the messages like yours are very useful for attracting | |
| 8099 our attention. | |
| 8100 | |
| 8101 @item | |
| 8102 The package was noted by the developers, but they simply haven't yet | |
| 8103 gotten around to including/porting it. Wait for the next release or, | |
| 8104 even better, offer your help. It will be gladly accepted and | |
| 8105 appreciated. | |
| 8106 @end enumerate | |
| 8107 | |
| 2459 | 8108 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages |
| 8109 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets? | |
| 2417 | 8110 |
| 8111 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at | |
| 428 | 8112 @iftex |
| 8113 @* | |
| 8114 @end iftex | |
| 2459 | 8115 @uref{http://acs.ist.psu.edu/dismal/dismal.html}. |
| 8116 | |
| 8117 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages | |
| 8118 @unnumberedsubsec Q8.1.3: Is there a MatLab mode? | |
| 2417 | 8119 |
| 8120 Yes, a matlab mode and other items are available at the | |
| 2459 | 8121 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}. |
| 8122 | |
| 8123 @unnumberedsec 8.2: Environments Built Around XEmacs | |
| 8124 | |
| 8125 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages | |
| 8126 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop? | |
| 2417 | 8127 |
| 8128 SPARCworks was a development environment from Sun (circa 1993-1996) | |
| 8129 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and | |
| 8130 Pascal), a debugger, and other tools such as TeamWare (for | |
| 8131 configuration management), MakeTool, etc. | |
| 428 | 8132 |
| 8133 EOS is the integration of XEmacs with the SPARCworks debugger. It | |
| 8134 allows one to use an XEmacs frame to view code (complete with | |
| 8135 fontification, etc.), set breakpoints, print variables, etc., while | |
| 2417 | 8136 using the SPARCworks debugger. |
| 8137 | |
| 8138 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten | |
| 8139 Again" and was the name used by Sun for its modified version of Lucid | |
| 8140 Emacs (later XEmacs) in the early-mid 90's. This is documented in | |
| 8141 more detail in the history section of the XEmacs About page. | |
| 8142 | |
| 8143 EOS was replaced around 1996 with a newer graphical development | |
| 8144 environment called Sun WorkShop. The current status of this is | |
| 8145 unknown. | |
| 8146 | |
| 2459 | 8147 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages |
| 8148 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21? | |
| 428 | 8149 |
| 8150 Add the switch ---with-workshop to the configure command when building | |
| 8151 XEmacs and put the following in one of your startup files | |
| 8152 (e.g. site-start.el or .emacs): | |
| 8153 | |
| 8154 @lisp | |
| 8155 (when (featurep 'tooltalk) | |
| 8156 (load "tooltalk-macros") | |
| 8157 (load "tooltalk-util") | |
| 8158 (load "tooltalk-init")) | |
| 8159 (when (featurep 'sparcworks) | |
| 8160 (load "sunpro-init") | |
| 8161 (load "ring") | |
| 8162 (load "comint") | |
| 8163 (load "annotations") | |
| 8164 (sunpro-startup)) | |
| 8165 @end lisp | |
| 8166 | |
| 8167 If you are not using the latest Workshop (5.0) you have to apply the | |
| 8168 following patch: | |
| 8169 | |
| 8170 @format | |
| 8171 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999 | |
| 8172 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999 | |
| 8173 @@@@ -42,7 +42,7 @@@@ | |
| 8174 (defvar running-xemacs nil "t if we're running XEmacs") | |
| 8175 (defvar running-emacs nil "t if we're running GNU Emacs 19") | |
| 438 | 8176 |
| 428 | 8177 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version) |
| 8178 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version) | |
| 8179 (setq running-xemacs t) | |
| 8180 (setq running-emacs t)) | |
| 438 | 8181 @end format |
| 428 | 8182 |
| 2459 | 8183 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages |
| 8184 @unnumberedsubsec Q8.2.3: What is/was Energize? | |
| 2417 | 8185 |
| 8186 The "Energize Programming System" was a C and C++ development environment | |
| 8187 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was | |
| 8188 created in the first place. Unfortunately, Lucid went out of business in | |
| 8189 1994. The rights to sell it in Japan were purchased by INS | |
| 8190 Engineering (which briefly employed Stig Hackvan aka Jonathan | |
| 8191 Stigelman to work on Japanese support for XEmacs, in late 1994 and | |
| 8192 early 1995) and Tartan bought the rights to sell it in the rest of the | |
| 8193 world. However, INS is not selling Energize at this point and may or | |
| 8194 may not have ever done so; Tartan certainly never did. | |
| 8195 | |
| 2459 | 8196 @node Q8.2.4, , Q8.2.3, Other Packages |
| 8197 @unnumberedsubsec Q8.2.4: What is Infodock? | |
| 428 | 8198 |
| 660 | 8199 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an |
| 8200 integrated productivity toolset, mainly aimed at technical people, | |
| 8201 hosted at SourceForge. | |
| 428 | 8202 |
| 8203 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of | |
| 8204 the power of Emacs, but with an easier to use and more comprehensive | |
| 8205 menu-based user interface. The bottom portion of this text describes | |
| 8206 how it differs from XEmacs and GNU Emacs from the Free Software | |
| 8207 Foundation. | |
| 8208 | |
| 8209 InfoDock is aimed at people who want a free, turn-key productivity | |
| 8210 environment. Although InfoDock is customizable, it is not intended for | |
| 8211 people who like basic versions of Emacs which need to be customized | |
| 8212 extensively for local use; standard Emacs distributions are better for | |
| 8213 such uses. InfoDock is for those people who want a complete, | |
| 8214 pre-customized environment in one package, which they need not touch | |
| 8215 more than once or twice a year to update to new revisions. | |
| 8216 | |
| 8217 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX, | |
| 8218 and Intel Linux systems. It is intended for use on a color display, | |
| 8219 although most features will work on monochrome monitors. Simply unpack | |
| 8220 InfoDock according to the instructions in the ID-INSTALL file and you | |
| 8221 are ready to run. | |
| 8222 | |
| 8223 The InfoDock Manual is concise, yet sufficient as a user guide for users | |
| 8224 who have never used an Emacs-type editor before. For users who are | |
| 8225 already familiar with Emacs, it supplements the information in the GNU | |
| 8226 Emacs Manual. | |
| 8227 | |
| 8228 InfoDock menus are much more extensive and more mature than standard | |
| 8229 Emacs menus. Each menu offers a @samp{Manual} item which displays | |
| 8230 documentation associated with the menu's functions. | |
| 8231 | |
| 8232 @noindent | |
| 8233 Four types of menubars are provided: | |
| 8234 @enumerate | |
| 8235 @item | |
| 8236 An extensive menubar providing access to global InfoDock commands. | |
| 8237 @item | |
| 8238 Mode-specific menubars tailored to the current major mode. | |
| 8239 @item | |
| 8240 A simple menubar for basic editing to help novices get started with InfoDock. | |
| 8241 @item | |
| 8242 The standard XEmacs menubar. | |
| 8243 @end enumerate | |
| 8244 | |
| 8245 Most modes also include mode-specific popup menus. Additionally, region and | |
| 8246 rectangle popup menus are included. | |
| 8247 | |
| 8248 @samp{Hyperbole}, the everyday information manager, is a core part of | |
| 8249 InfoDock. This provides context-sensitive mouse keys, a rolodex-type | |
| 8250 contact manager, programmable hypertext buttons, and an autonumbered | |
| 8251 outliner with embedded hyperlink anchors. | |
| 8252 | |
| 8253 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a | |
| 8254 standard part of InfoDock. | |
| 8255 | |
| 8256 InfoDock saves a more extensive set of user options than other Emacs | |
| 8257 versions. | |
| 8258 | |
| 8259 InfoDock inserts a useful file header in many file types, showing the | |
| 8260 author, summary, and last modification time of each file. A summary | |
| 8261 program can then be used to summarize all of the files in a directory, | |
| 8262 for easy MANIFEST file creation. | |
| 8263 | |
| 8264 Your working set of buffers is automatically saved and restored (if you | |
| 8265 answer yes to a prompt) between InfoDock sessions. | |
| 8266 | |
| 8267 Refined color choices for code highlighting are provided for both dark and | |
| 8268 light background display frames. | |
| 8269 | |
| 8270 The @kbd{C-z} key prefix performs frame-based commands which parallel the | |
| 8271 @kbd{C-x} key prefix for window-based commands. | |
| 8272 | |
| 8273 The Smart Menu system is included for producing command menus on dumb | |
| 8274 terminals. | |
| 8275 | |
| 8276 Lisp libraries are better categorized according to function. | |
| 8277 | |
| 8278 Extensions and improvements to many areas of Emacs are included, such as: | |
| 8279 paragraph filling, mail reading with Rmail, shell handling, outlining, code | |
| 8280 highlighting and browsing, and man page browsing. | |
| 8281 | |
| 8282 InfoDock questions, answers and discussion should go to the mail list | |
| 8283 @iftex | |
| 8284 @* | |
| 8285 @end iftex | |
| 8286 @email{infodock@@infodock.com}. Use | |
| 8287 @email{infodock-request@@infodock.com} to be added or removed from the | |
| 8288 list. Always include your InfoDock version number when sending help | |
| 8289 requests. | |
| 8290 | |
| 2459 | 8291 @node Current Events, Legacy Versions, Other Packages, Top |
| 8292 @unnumbered 9 What the Future Holds | |
| 8293 | |
| 8294 This is part 9 of the XEmacs Frequently Asked Questions list. This | |
| 611 | 8295 section will change frequently, and (in theory) should contain any |
| 8296 interesting items that have transpired recently. (But in practice it's | |
| 8297 not getting updated like this.) | |
| 8298 | |
| 8299 This section also contains descriptions of the new features in all the | |
| 8300 recent releases of XEmacs. For the most part, the information below is | |
| 8301 a synopsis of the more complete information that can be found in the | |
| 8302 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution. | |
| 8303 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help} | |
| 8304 menu. | |
| 8305 | |
| 8306 Information on older versions of XEmacs can be find in @file{ONEWS} in | |
| 8307 the same directory, or @file{OONEWS} for really old versions. | |
| 8308 | |
| 428 | 8309 @menu |
| 2537 | 8310 9.0: Changes |
| 2459 | 8311 * Q9.0.1:: What new features will be in XEmacs soon? |
| 8312 * Q9.0.2:: What's new in XEmacs 21.4? | |
| 8313 * Q9.0.3:: What's new in XEmacs 21.1? | |
| 8314 * Q9.0.4:: What's new in XEmacs 20.4? | |
| 8315 * Q9.0.5:: What's new in XEmacs 20.3? | |
| 8316 * Q9.0.6:: What's new in XEmacs 20.2? | |
| 428 | 8317 @end menu |
| 8318 | |
| 2459 | 8319 @unnumberedsec 9.0: Changes |
| 8320 | |
| 8321 @node Q9.0.1, Q9.0.2, Current Events, Current Events | |
| 8322 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon? | |
| 611 | 8323 |
| 2417 | 8324 #### Write me. |
| 428 | 8325 |
| 2459 | 8326 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events |
| 8327 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4? | |
| 611 | 8328 |
| 8329 21.4 was the "stable" version of the 21.2 series, which was considered | |
| 8330 "experimental" throughout its life; thus there were no "official" | |
| 8331 releases at all. In essence, XEmacs is now following the "alternating" | |
| 8332 scheme of Linux, where at any point there are at least two different | |
| 8333 development branches, one "stable" and one "experimental". Periodic | |
| 8334 releases happen in both branches, but those in the experimental branch | |
| 8335 are not tested as well, and there's no guarantee they will work at all. | |
| 4311 | 8336 The experimental branch is open to any and all code that's acceptable |
| 611 | 8337 to the developers; the stable branch, however, is in general limited |
| 8338 only to bug fixes, and all contributions are carefully reviewed to make | |
| 8339 sure they will increase and not decrease stability. | |
| 8340 | |
| 8341 21.3 never existed at all; it was decided to follow the Linux scheme | |
| 8342 exactly, where odd-numbered series are experimental and even-numbered | |
| 8343 ones stable. | |
| 8344 | |
| 8345 The following lists summarizes the essential changes made in this | |
| 8346 version. For a fuller list, see the @file{NEWS} in the @file{etc} | |
| 8347 directory of the XEmacs distribution, or use @kbd{C-h n} or the | |
| 8348 @samp{Help} menu to view this file inside of XEmacs. | |
| 8349 | |
| 676 | 8350 @unnumberedsubsubsec User-visible changes in XEmacs 21.4 |
| 611 | 8351 |
| 8352 @itemize @bullet | |
| 8353 | |
| 8354 @item | |
| 8355 The delete key now deletes forward by default. | |
| 8356 @item | |
| 8357 Shifted motion keys now select text by default. | |
| 8358 @item | |
| 8359 You can now build XEmacs with support for GTK+ widget set. | |
| 8360 @item | |
| 8361 ~/.xemacs/init.el is now the preferred location for the init | |
| 8362 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom | |
| 8363 file will move to ~/.xemacs/custom.el.) | |
| 8364 @item | |
| 8365 Much-improved sample init.el, showing how to use many useful features. | |
| 8366 @item | |
| 8367 XEmacs support for menu accelerators has been much improved. | |
| 8368 @item | |
| 8369 Default menubar improvements. (Default menubar has many new commands and | |
| 8370 better organization. The font-menu is now available under MS Windows.) | |
| 8371 @item | |
| 2417 | 8372 Dialog box improvements, including a real file dialog box. (XEmacs now |
| 8373 has a proper file dialog box under MS Windows (and GTK)! The old | |
| 8374 clunky file dialog box is improved. Keyboard traversal now works | |
| 8375 correctly in MS Windows dialog boxes. There is a Search dialog box | |
| 8376 available from @samp{Edit->Find...}) | |
| 611 | 8377 @item |
| 8378 New buffer tabs. | |
| 8379 @item | |
| 8380 There is a new MS Windows installer, netinstall, ported from Cygwin. | |
| 8381 @item | |
| 8382 The subprocess quote-handling mechanism under Windows is much improved. | |
| 8383 @item | |
| 8384 Printing support now available under MS Windows. | |
| 8385 @item | |
| 8386 Selection improvements. (Kill and yank now interact with the clipboard under Windows. MS Windows support for selection is now much more robust. Motif selection support is now more correct (but slower).) | |
| 8387 @item | |
| 8388 Mail spool locking now works correctly. | |
| 8389 @item | |
| 8390 International support changes. (The default coding-priority-list is now | |
| 8391 safer. International keysyms are now supported under X. MS Windows | |
| 8392 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese, | |
| 8393 Ethiopic now supported. Proper support for words in Latin 3 and Latin | |
| 8394 4.) | |
| 8395 @item | |
| 8396 Help buffers contain hyperlinks, and other changes. | |
| 8397 @item | |
| 8398 The modeline's text is now scrollable. | |
| 8399 @item | |
| 8400 The mouse wheel under MS Windows now functions correctly. | |
| 8401 @item | |
| 8402 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.) | |
| 8403 @item | |
| 8404 Rectangle functions rewritten to avoid inserting extra spaces. | |
| 8405 @item | |
| 8406 New command `kill-entire-line' that always kills the entire line. | |
| 8407 @item | |
| 8408 Default values correctly stored in minibuffer histories. | |
| 8409 @item | |
| 8410 You can now create "indirect buffers", like in GNU Emacs. | |
| 8411 @item | |
| 8412 Pixel-based scrolling has been implemented. | |
| 8413 @item | |
| 8414 Operation progress can be displayed using graphical widgets. | |
| 8415 @item | |
| 8416 User names following a tilde can now be completed at file name prompts. | |
| 8417 @item | |
| 8418 XEmacs can now play sound using Enlightenment Sound Daemon (ESD). | |
| 8419 @item | |
| 8420 X-Face support is now available under MS Windows. | |
| 8421 @item | |
| 8422 The PostgreSQL Relational Database Management System is now supported. | |
| 8423 @item | |
| 8424 Indentation no longer indents comments that begin at column zero. | |
| 8425 @item | |
| 8426 Face and variable settings can have comments in Customize. | |
| 8427 @item | |
| 8428 New locations for early package hierarchies. | |
| 8429 @item | |
| 8430 The `auto-save' library has been greatly improved. | |
| 8431 @item | |
| 8432 New variable `mswindows-alt-by-itself-activates-menu'. | |
| 8433 @item | |
| 8434 Other init-file-related changes. (Init file in your home directory may be called `.emacs.el'. New command-line switches -user-init-file and -user-init-directory.) | |
| 8435 @item | |
| 8436 Etags changes. See @file{NEWS} for full details. | |
| 8437 @end itemize | |
| 8438 | |
| 676 | 8439 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4 |
| 611 | 8440 |
| 8441 Not yet written. | |
| 8442 | |
| 661 | 8443 @c APA: Texi2html produces invalid HTML from an empty list of bullets! |
| 8444 @c Please uncomment following list when it does contain bullets. | |
| 8445 @c @itemize @bullet | |
| 8446 @c @end itemize | |
| 611 | 8447 |
| 2459 | 8448 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events |
| 8449 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1? | |
| 611 | 8450 |
| 8451 21.1 was the "stable" version of "experimental" 21.0 series. | |
| 2459 | 8452 @xref{Q9.0.2, What's new in XEmacs 21.4?}. |
| 611 | 8453 |
| 8454 The following lists summarizes the essential changes made in this | |
| 8455 version. For a fuller list, see the @file{NEWS} in the @file{etc} | |
| 8456 directory of the XEmacs distribution, or use @kbd{C-h n} or the | |
| 8457 @samp{Help} menu to view this file inside of XEmacs. | |
| 8458 | |
| 676 | 8459 @unnumberedsubsubsec User-visible changes in XEmacs 21.1 |
| 611 | 8460 |
| 8461 @itemize @bullet | |
| 8462 | |
| 8463 @item | |
| 2459 | 8464 XEmacs is now supported under Microsoft Windows 95/98 and Windows |
| 2417 | 8465 NT/2000/XP operating systems. To discuss Windows-specific issues, |
| 8466 subscribe to the mailing list at | |
| 8467 @email{xemacs-winnt-request@@xemacs.org}. | |
| 611 | 8468 |
| 8469 @item | |
| 8470 XEmacs has been unbundled into constituent installable packages. | |
| 8471 | |
| 8472 @item | |
| 8473 @strong{Other notable changes}: The @samp{Options} menu has been ported to | |
| 8474 Custom; XEmacs now is able to choose X visuals and use private | |
| 8475 colormaps; You can drag the vertical divider of "horizontally" | |
| 8476 (side-by-side) split windows. | |
| 8477 | |
| 8478 @item | |
| 8479 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp | |
| 8480 integers and 32-bit pointers (previously, it was 28-bit integers and | |
| 8481 pointers); XEmacs can be built with LDAP support; @file{dir} files can be | |
| 8482 removed in the Info subsystem, and will be regenerated on-the-fly. | |
| 8483 | |
| 8484 @item | |
| 8485 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight} | |
| 8486 | |
| 8487 @item | |
| 8488 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus}, | |
| 8489 @file{gnuclient}. See @file{NEWS} for full details. | |
| 8490 | |
| 8491 @item | |
| 8492 @strong{New commands, variables and functions}: | |
| 8493 @code{center-to-window-line} (like @code{recenter} but doesn't force a | |
| 8494 redisplay); variable @code{user-full-name} (customize what your full | |
| 8495 name looks like in mail); @kbd{M-x customize-changed-options} (customize | |
| 8496 options whose default values changes because you upgraded your XEmacs); | |
| 8497 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to | |
| 8498 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but | |
| 8499 doesn't delete the char searched for); commands to store, retrieve and | |
| 8500 increment numbers in registers, useful for macros. | |
| 8501 | |
| 8502 @item | |
| 8503 @strong{Changes to commands, variables, and functions}: @kbd{M-x | |
| 8504 query-replace} and friends operate only on the region when it's active; | |
| 8505 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.} | |
| 8506 searches exact tag matches before inexact ones; function | |
| 8507 @code{user-full-name} with no arguments returns the var | |
| 8508 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts | |
| 8509 the result in the current buffer. | |
| 1138 | 8510 |
| 611 | 8511 @item |
| 8512 @strong{Other changes}: Under X, new application class @samp{XEmacs}; | |
| 8513 byte-compilation of user-specs now works. | |
| 8514 | |
| 8515 @item | |
| 8516 @strong{XEmacs/Mule (internationalization) changes}: Mule support now | |
| 8517 works on TTY's; Egg/SJ3 input method now officially supported (Quail and | |
| 8518 Egg/Skk already available through LEIM since 20.3); localized Japanese | |
| 8519 menubars if XEmacs is built with the right support. | |
| 8520 | |
| 8521 @end itemize | |
| 8522 | |
| 676 | 8523 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1 |
| 611 | 8524 |
| 8525 @itemize @bullet | |
| 8526 | |
| 8527 @item | |
| 8528 @strong{Specifier changes}: The window locale now has a higher | |
| 8529 precedence than the buffer locale when instantiating; new macro | |
| 8530 @code{let-specifier}; new specifiers | |
| 8531 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p', | |
| 8532 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p}, | |
| 8533 @code{vertical-divider-always-visible-p}, | |
| 8534 @code{vertical-divider-shadow-thickness}, | |
| 8535 @code{vertical-divider-line-width}, @code{vertical-divider-spacing}; | |
| 8536 specifiers and symbols whose value is a specifier allowed as modeline | |
| 8537 specifications. | |
| 8538 | |
| 8539 @item | |
| 8540 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF, | |
| 8541 prevents any attempt to permanently change the selected frame; new | |
| 8542 function @code{focus-frame} sets the window system focus a frame; new | |
| 8543 special forms @code{save-selected-frame} and @code{with-selected-frame}. | |
| 8544 | |
| 8545 @item | |
| 8546 @strong{Window function changes}: @code{select-window} now has optional | |
| 8547 argument @var{NORECORD} to inhibit recording a buffer change; | |
| 8548 @code{vertical-motion} now correctly handles optional @var{WINDOW} | |
| 8549 argument and has new optional argument @var{PIXELS}, to have the | |
| 8550 returned values be in pixels; new function | |
| 8551 @code{vertical-motion-pixels}; new functions | |
| 8552 @code{window-text-area-pixel-@{width,height,edges@}}; new functions | |
| 8553 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new | |
| 8554 function @code{window-displayed-text-pixel-height}. | |
| 8555 | |
| 8556 @item | |
| 8557 @strong{Other function changes}: Arithmetic comparison functions | |
| 8558 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of | |
| 8559 arguments; hashtables now have a consistent read/print syntax; keyword | |
| 8560 symbols cannot be set to a value other than themselves; @code{concat} no | |
| 8561 longer accepts integer arguments; new function @code{string}, like | |
| 8562 @code{list}, @code{vector}, etc.; new function @code{temp-directory} | |
| 8563 (OS-independent way to get a temp directory); @code{load-average} has | |
| 8564 optional argument @var{USE-FLOATS}; @code{make-event} implemented | |
| 8565 completely; new function @code{function-interactive} (returns a | |
| 8566 function's interactive spec); new functions @code{lmessage}, | |
| 8567 @code{lwarn} (printf-like versions of @code{display-wessage}, | |
| 8568 @code{display-warning}); new keyword @code{:version} to | |
| 8569 @code{defcustom}. | |
| 8570 | |
| 8571 @item | |
| 8572 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is | |
| 8573 available, it will be used (better performance on libc6 Linux systems); | |
| 8574 tracking line-numbers in modeline is now efficient; profiling records a | |
| 8575 call-count of all called functions, retrievable through | |
| 8576 @code{profile-call-count-results}. | |
| 8577 | |
| 8578 @item | |
| 8579 @strong{Startup and path searching}: code to assemble paths at startup | |
| 8580 rewritten for new package system; new function @code{split-path} (splits | |
| 8581 by @code{path-separator}); @code{Info-default-directory-list} obsolete, | |
| 8582 use @code{Info-directory-list} instead; site-lisp is deprecated and no | |
| 8583 longer on the load-path by default. | |
| 8584 | |
| 8585 @end itemize | |
| 8586 | |
| 2459 | 8587 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events |
| 8588 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4? | |
| 611 | 8589 |
| 8590 XEmacs 20.4 is a bugfix release with no user-visible changes. | |
| 8591 @c Filled in from NEWS file of 20.5-b33 | |
| 8592 | |
| 2459 | 8593 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events |
| 8594 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3? | |
| 428 | 8595 |
| 8596 XEmacs 20.3 was released in November 1997. It contains many bugfixes, | |
| 8597 and a number of new features, including Autoconf 2 based configuration, | |
| 8598 additional support for Mule (Multi-language extensions to Emacs), many | |
| 8599 more customizations, multiple frames on TTY-s, support for multiple info | |
| 8600 directories, an enhanced gnuclient, improvements to regexp matching, | |
| 8601 increased MIME support, and many, many synches with GNU Emacs 20. | |
| 8602 | |
| 8603 The XEmacs/Mule support has been only seriously tested in a Japanese | |
| 8604 locale, and no doubt many problems still remain. The support for | |
| 8605 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a | |
| 440 | 8606 price---about a 30% slowdown from 19.16. We're making progress on |
| 428 | 8607 improving performance and XEmacs 20.3 compiled without Mule (which is |
| 8608 the default) is definitely faster than XEmacs 19.16. | |
| 8609 | |
| 8610 XEmacs 20.3 is the first non-beta v20 release, and will be the | |
| 8611 basis for all further development. | |
| 8612 | |
| 2459 | 8613 @node Q9.0.6, , Q9.0.5, Current Events |
| 8614 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2? | |
| 611 | 8615 |
| 8616 The biggest changes in 20.2 include integration of EFS (the next | |
| 8617 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a | |
| 8618 major mode for editing Tex and LaTeX, and a lot of other stuff). Many | |
| 8619 bugs from 20.0 have been fixed for this release. 20.2 also contains a | |
| 8620 new system for customizing XEmacs options, invoked via @kbd{M-x | |
| 8621 customize}. | |
| 8622 | |
| 8623 XEmacs 20.2 is the development release (20.0 was beta), and is no longer | |
| 8624 considered unstable. | |
| 8625 | |
| 8626 For older news, see the file @file{ONEWS} in the @file{etc} directory of | |
| 8627 the XEmacs distribution. | |
| 428 | 8628 |
| 2417 | 8629 @node Legacy Versions, , Current Events, Top |
| 2459 | 8630 @unnumbered 10 New information about old XEmacsen |
| 8631 | |
| 8632 This is part 10 of the XEmacs Frequently Asked Questions list. It will | |
| 1495 | 8633 occasionally be updated to reflect new information about versions which |
| 8634 are no longer being revised by the XEmacs Project. The primary purpose | |
| 8635 is advice on compatibility of older XEmacsen with new packages and | |
| 8636 updated versions of packages, but bug fixes (which will not be applied | |
| 8637 to released XEmacsen, but users can apply themselves) are also accepted. | |
| 8638 | |
| 8639 @menu | |
| 2537 | 8640 10.0: XEmacs 21.1 |
| 2459 | 8641 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. |
| 2559 | 8642 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1. |
| 1495 | 8643 @end menu |
| 8644 | |
| 2459 | 8645 @unnumberedsec 10.0: XEmacs 21.1 |
| 8646 | |
| 2559 | 8647 @node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions |
| 2459 | 8648 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1. |
| 1495 | 8649 |
| 8650 @email{eeide@@cs.utah.edu, Eric Eide} wrote: | |
| 8651 | |
| 8652 @quotation | |
| 8653 Previously I wrote: | |
| 8654 | |
| 8655 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see | |
| 8656 Eric> any smileys :-(. | |
| 8657 | |
| 8658 After a bit of sleuthing, I discovered the essence of the problem. | |
| 8659 For me, the form: | |
| 8660 | |
| 8661 @lisp | |
| 8662 (with-temp-buffer | |
| 8663 (insert-file-contents "foo.xpm") | |
| 8664 (buffer-string)) | |
| 8665 @end lisp | |
| 8666 | |
| 8667 returns the empty string. This is because something somewhere | |
| 8668 replaces the XPM data with a glyph --- I haven't figured out where | |
| 8669 this occurs. | |
| 8670 @end quotation | |
| 8671 | |
| 8672 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies: | |
| 8673 | |
| 8674 @quotation | |
| 8675 Do this: | |
| 8676 | |
| 8677 @lisp | |
| 8678 (setq format-alist nil) | |
| 8679 @end lisp | |
| 8680 | |
| 8681 The image-mode stuff is gone from format-alist in the 21.4 | |
| 8682 branch, praise be. | |
| 8683 @end quotation | |
| 8684 | |
| 2559 | 8685 @node Q10.0.2, , Q10.0.1, Legacy Versions |
| 8686 @unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1. | |
| 8687 | |
| 8688 XEmacs relies on a process called "dumping" to generate a working | |
| 8689 executable. Under MS-Windows this process effectively fixes the memory | |
| 8690 addresses of information in the executable. When XEmacs starts up it tries | |
| 8691 to reserve these memory addresses so that the dumping process can be | |
| 8692 reversed -- putting the information back at the correct addresses. | |
| 8693 Unfortunately some .DLLs (for instance the soundblaster driver) occupy | |
| 8694 memory addresses that can conflict with those needed by the dumped XEmacs | |
| 8695 executable. In this instance XEmacs will fail to start without any | |
| 8696 explanation. Note that this is extremely machine specific. | |
| 8697 | |
| 8698 21.1.10 includes a fix for this that makes more intelligent guesses | |
| 8699 about which memory addresses will be free, and this should cure the | |
| 8700 problem for most people. 21.4 implements "portable dumping", which | |
| 8701 eliminates the problem altogether. We recommend you use the 21.4 | |
| 8702 binaries, but you can use the 21.1 binaries if you are very paranoid | |
| 8703 about stability. @xref{Q1.1.2, Are binaries available?}. | |
| 8704 | |
| 428 | 8705 @bye |