Mercurial > hg > xemacs-beta
annotate man/xemacs-faq.texi @ 4625:4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
| author | Stephen J. Turnbull <stephen@xemacs.org> |
|---|---|
| date | Thu, 26 Feb 2009 18:21:40 +0900 |
| parents | dd12adb12b8f |
| children | fd2495d78aac |
| 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? | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
344 * Q3.0.12:: Mac Alt/Option key as Meta. |
| 2417 | 345 |
| 346 3.1: The Mouse | |
| 347 * Q3.1.1:: How can I turn off Mouse pasting? | |
| 348 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons? | |
| 349 * Q3.1.3:: Clicking the left button does not do anything in buffer list. | |
| 350 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3? | |
| 2459 | 351 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is? |
| 352 | |
| 353 3.2: Buffers, Text Editing | |
| 354 * Q3.2.1:: Can I have the end of the buffer delimited in some way? | |
| 355 * Q3.2.2:: How do I insert today's date into a buffer? | |
| 356 * Q3.2.3:: How do I get a single minibuffer frame? | |
| 357 * Q3.2.4:: How can I enable auto-indent and/or Filladapt? | |
| 358 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 359 | |
| 360 3.3: Text Selections | |
| 361 * Q3.3.1:: How do I select a rectangular region? | |
| 362 * Q3.3.2:: How can I turn off or change highlighted selections? | |
| 363 * Q3.3.3:: How do I cause typing on an active region to remove it? | |
| 364 * Q3.3.4:: Can I turn off the highlight during isearch? | |
| 365 * Q3.3.5:: Why is killing so slow? | |
| 366 * Q3.3.6:: Why does @kbd{M-w} take so long? | |
| 367 | |
| 368 3.4: Editing Source Code | |
| 369 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode? | |
| 370 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly? | |
| 371 | |
| 372 4 Display Functions | |
| 373 | |
| 374 4.0: Textual Fonts and Colors | |
| 375 * Q4.0.1:: How do I specify a font? | |
| 376 * Q4.0.2:: How do I set the text, menu and modeline fonts? | |
| 377 * Q4.0.3:: How can I set color options from @file{init.el}? | |
| 378 * Q4.0.4:: How can I set the colors when highlighting a region? | |
| 379 * Q4.0.5:: How can I limit color map usage? | |
| 380 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them. | |
| 381 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs? | |
| 382 * Q4.0.8:: How do I display non-ASCII characters? | |
| 383 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}. | |
| 384 | |
| 385 4.1: Syntax Highlighting (Font Lock) | |
| 386 * Q4.1.1:: How can I do source code highlighting using font-lock? | |
| 387 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default? | |
| 388 | |
| 389 4.2: The Modeline | |
| 390 * Q4.2.1:: How can I make the modeline go away? | |
| 391 * Q4.2.2:: How do you have XEmacs display the line number in the modeline? | |
| 392 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline? | |
| 393 * Q4.2.4:: How can I change the modeline color based on the mode used? | |
| 394 | |
| 395 4.3: The Cursor | |
| 396 * Q4.3.1:: Is there a way to make the bar cursor thicker? | |
| 397 * Q4.3.2:: Is there a way to get back the block cursor? | |
| 398 * Q4.3.3:: Can I make the cursor blink? | |
| 399 | |
| 400 4.4: The Menubar | |
| 401 * Q4.4.1:: How do I get rid of the menubar? | |
| 402 * Q4.4.2:: How can I customize the menubar? | |
| 403 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 404 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 405 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working? | |
| 406 | |
| 407 4.5: The Toolbar | |
| 408 * Q4.5.1:: How do I get rid of the toolbar? | |
| 409 * Q4.5.2:: How can I customize the toolbar? | |
| 410 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar? | |
| 411 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar | |
| 412 | |
| 413 4.6: Scrollbars and Scrolling | |
| 414 * Q4.6.1:: How can I disable the scrollbar? | |
| 415 * Q4.6.2:: How can I change the scrollbar width? | |
| 416 * Q4.6.3:: How can I use resources to change scrollbar colors? | |
| 417 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this? | |
| 418 * Q4.6.5:: Scrolling one line at a time. | |
| 419 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes? | |
| 420 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off? | |
| 421 | |
| 422 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 423 * Q4.7.1:: How can I disable the gutter tabs? | |
| 424 * Q4.7.2:: How can I disable the progress bar? | |
| 425 * Q4.7.3:: There are bugs in the gutter or widgets. | |
| 426 * Q4.7.4:: How can I customize the gutter or gutter tabs? | |
| 427 | |
| 428 5 Interfacing with the Operating System and External Devices | |
| 429 | |
| 430 5.0: X Window System and Resources | |
| 431 * Q5.0.1:: Where is a list of X resources? | |
| 432 * Q5.0.2:: How can I detect a color display? | |
| 433 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}? | |
| 434 * Q5.0.4:: How can I have the window title area display the full path? | |
| 435 * Q5.0.5:: @samp{xemacs -name junk} doesn't work? | |
| 436 * 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
|
437 * Q5.0.7:: How can I use antialiased fonts under X11? |
| 2459 | 438 |
| 439 5.1: Microsoft Windows | |
| 440 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? | |
| 441 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 442 | |
| 443 5.2: Printing | |
| 444 * Q5.2.1:: What do I need to change to make printing work? | |
| 445 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer? | |
| 446 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 447 * Q5.2.4:: Can you print under MS Windows? | |
| 448 | |
| 449 5.3: Sound | |
| 450 * Q5.3.1:: How do I turn off the sound? | |
| 451 * Q5.3.2:: How do I get funky sounds instead of a boring beep? | |
| 452 * Q5.3.3:: What are NAS and ESD (EsounD)? | |
| 453 * Q5.3.4:: Sunsite sounds don't play. | |
| 454 | |
| 455 5.4: Running an Interior Shell, Invoking Subprocesses | |
| 456 * Q5.4.1:: What is an interior shell? | |
| 457 * Q5.4.2:: How do I start up a second shell buffer? | |
| 458 * Q5.4.3:: Telnet from shell filters too much | |
| 459 * Q5.4.4:: Strange things are happening in Shell Mode. | |
| 460 * Q5.4.5:: XEmacs complains "No such file or directory, diff" | |
| 2995 | 461 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed" |
| 2459 | 462 |
| 463 5.5: Multiple Device Support | |
| 464 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display? | |
| 465 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 466 * Q5.5.3:: How do I disable gnuserv from opening a new frame? | |
| 467 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 468 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 469 | |
| 470 6 Connecting to the Internet | |
| 471 | |
| 472 6.0: General Mail and News | |
| 473 * Q6.0.1:: What are the various packages for reading mail? | |
| 474 * Q6.0.2:: How can I send mail? | |
| 475 * Q6.0.3:: How do I get my outgoing mail archived? | |
| 476 * Q6.0.4:: How can I read and/or compose MIME messages? | |
| 477 * Q6.0.5:: How do I customize the From line? | |
| 478 * Q6.0.6:: How do I get my MUA to filter mail for me? | |
| 479 * Q6.0.7:: Remote mail reading with an MUA. | |
| 480 * Q6.0.8:: An MUA gets an error incorporating new mail. | |
| 481 * Q6.0.9:: Why isn't @file{movemail} working? | |
| 482 * Q6.0.10:: How do I make my MUA display graphical smilies? | |
| 483 * Q6.0.11:: How can I get those oh-so-neat X-Face lines? | |
| 484 | |
| 485 6.1: Reading Mail with VM | |
| 486 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP? | |
| 487 * Q6.1.2:: How can I get VM to automatically check for new mail? | |
| 488 * 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"? | |
| 489 * Q6.1.4:: Is there a mailing list or FAQ for VM? | |
| 490 * Q6.1.5:: How do I make VM stay in a single frame? | |
| 491 * Q6.1.6:: Customization of VM not covered in the manual, or here. | |
| 492 | |
| 493 6.2: Reading Netnews and Mail with Gnus | |
| 494 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 495 * Q6.2.2:: How do I make Gnus stay within a single frame? | |
| 496 | |
| 497 6.3: FTP Access | |
| 498 * Q6.3.1:: Can I edit files on other hosts? | |
| 499 * Q6.3.2:: What is EFS? | |
| 500 | |
| 501 6.4: Web Browsing with W3 | |
| 502 * Q6.4.1:: What is W3? | |
| 503 * Q6.4.2:: How do I run W3 from behind a firewall? | |
| 504 * Q6.4.3:: Is it true that W3 supports style sheets and tables? | |
| 505 | |
| 506 7 Advanced Customization Using XEmacs Lisp | |
| 507 | |
| 2537 | 508 7.0: Emacs Lisp and @file{init.el} |
| 509 * Q7.0.1:: What version of Emacs am I running? | |
| 510 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions? | |
| 511 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. | |
| 512 * Q7.0.4:: How can I add directories to the @code{load-path}? | |
| 513 * Q7.0.5:: How to check if a lisp function is defined? | |
| 514 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? | |
| 515 | |
| 516 7.1: Emacs Lisp Programming Techniques | |
| 517 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 518 * Q7.1.2:: Can I generate "fake" keyboard events? | |
| 519 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? | |
| 520 * Q7.1.4:: What is the performance hit of @code{let}? | |
| 521 * Q7.1.5:: What is the recommended use of @code{setq}? | |
| 522 * Q7.1.6:: What is the typical misuse of @code{setq}? | |
| 523 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down? | |
| 524 * Q7.1.8:: I like recursion, does it slow things down? | |
| 525 * Q7.1.9:: How do I put a glyph as annotation in a buffer? | |
| 526 * Q7.1.10:: @code{map-extents} won't traverse all of my extents! | |
| 527 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 528 | |
| 529 7.2: Mathematics | |
| 2559 | 530 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp? |
| 531 * Q7.2.2:: XEmacs segfaults when I use very big numbers! | |
| 532 * Q7.2.3:: Bignums are really slow! | |
| 533 * Q7.2.4:: Equal bignums don't compare as equal! What gives? | |
| 2459 | 534 |
| 535 8 Other External Packages | |
| 536 | |
| 537 8.0: TeX | |
| 538 * Q8.0.1:: Is there something better than LaTeX mode? | |
| 539 * Q8.0.2:: What is AUCTeX? Where do you get it? | |
| 540 * Q8.0.3:: Problems installing AUCTeX. | |
| 541 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline? | |
| 542 | |
| 543 8.1: Other Unbundled Packages | |
| 544 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 545 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets? | |
| 546 * Q8.1.3:: Is there a MatLab mode? | |
| 547 | |
| 548 8.2: Environments Built Around XEmacs | |
| 549 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop? | |
| 550 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21? | |
| 551 * Q8.2.3:: What is/was Energize? | |
| 552 * Q8.2.4:: What is Infodock? | |
| 553 | |
| 554 9 What the Future Holds | |
| 555 | |
| 556 9.0: Changes | |
| 557 * Q9.0.1:: What new features will be in XEmacs soon? | |
| 558 * Q9.0.2:: What's new in XEmacs 21.4? | |
| 559 * Q9.0.3:: What's new in XEmacs 21.1? | |
| 560 * Q9.0.4:: What's new in XEmacs 20.4? | |
| 561 * Q9.0.5:: What's new in XEmacs 20.3? | |
| 562 * Q9.0.6:: What's new in XEmacs 20.2? | |
| 563 | |
| 564 10 New information about old XEmacsen | |
| 565 | |
| 566 10.0: XEmacs 21.1 | |
| 567 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. | |
| 2559 | 568 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1. |
| 569 | |
| 428 | 570 @end detailmenu |
| 571 @end menu | |
| 572 | |
| 573 @node Introduction, Installation, Top, Top | |
| 574 @unnumbered 1 Introduction, Policy, Credits | |
| 575 | |
| 576 Learning XEmacs is a lifelong activity. Even people who have used Emacs | |
| 577 for years keep discovering new features. Therefore this document cannot | |
| 578 be complete. Instead it is aimed at the person who is either | |
| 579 considering XEmacs for their own use, or has just obtained it and is | |
| 580 wondering what to do next. It is also useful as a reference to | |
| 581 available resources. | |
| 582 | |
| 2417 | 583 The previous maintainer of the FAQ was |
| 584 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started | |
| 585 it, after getting tired of hearing JWZ complain about repeatedly | |
| 586 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then | |
| 587 took over and did a massive update reorganizing the whole thing. At | |
| 588 this point Anthony took back over, but then had to give it up again. | |
| 589 Some of the other contributors to this FAQ are listed later in this | |
| 590 document. | |
| 428 | 591 |
| 592 The previous version was converted to hypertext format, and edited by | |
| 593 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to | |
| 434 | 594 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then |
| 595 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it | |
| 2417 | 596 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}. |
| 597 | |
| 598 The current version of the FAQ has been heavily redone by | |
| 599 @email{ben@@xemacs.org, Ben Wing}. | |
| 428 | 600 |
| 601 If you notice any errors or items which should be added or amended to | |
| 2417 | 602 this FAQ please send email to @email{xemacs-beta@@xemacs.org}. |
| 603 Include @samp{XEmacs FAQ} on the Subject: line. | |
| 428 | 604 |
| 605 @menu | |
| 2537 | 606 1.0: What is XEmacs? |
| 2417 | 607 * Q1.0.1:: What is XEmacs? |
| 608 * Q1.0.2:: What is the current version of XEmacs? | |
| 2537 | 609 * Q1.0.3:: How do you pronounce XEmacs? |
| 610 * Q1.0.4:: What does XEmacs look like? | |
| 611 * Q1.0.5:: Who wrote XEmacs? | |
| 612 * Q1.0.6:: Who wrote the FAQ? | |
| 613 | |
| 614 1.1: Getting XEmacs | |
| 615 * Q1.1.1:: Where can I find XEmacs? | |
| 616 * Q1.1.2:: Are binaries available? | |
| 617 * Q1.1.3:: How do I get the bleeding-edge sources? | |
| 618 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 619 | |
| 620 1.2: Versions for Different Operating Systems | |
| 621 * Q1.2.1:: Do I need X11 to run XEmacs? | |
| 622 * Q1.2.2:: What versions of Unix does XEmacs run on? | |
| 623 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows? | |
| 624 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 625 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 626 * Q1.2.6:: What are the differences between the various MS Windows emacsen? | |
| 627 * Q1.2.7:: How does the port cope with differences in the Windows user interface? | |
| 628 * Q1.2.8:: Is there a port of XEmacs to the Macintosh? | |
| 629 * Q1.2.9:: Is there a port of XEmacs to MS-DOS? | |
| 630 * Q1.2.10:: Is there a port of XEmacs to OS/2? | |
| 631 * Q1.2.11:: Is there a port of XEmacs to NextStep? | |
| 632 * Q1.2.12:: Is there a port of XEmacs to VMS? | |
| 633 | |
| 634 1.3: Getting Started | |
| 635 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? | |
| 636 * Q1.3.2:: Where do I put my @file{init.el} file? | |
| 637 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs? | |
| 638 * Q1.3.4:: Any good XEmacs tutorials around? | |
| 639 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function? | |
| 640 * Q1.3.6:: And how do I bind it to a key? | |
| 641 * Q1.3.7:: What's the difference between a macro and a function? | |
| 642 * Q1.3.8:: What is @code{Custom}? | |
| 643 | |
| 644 1.4: Getting Help | |
| 645 * Q1.4.1:: Where can I get help? | |
| 646 * Q1.4.2:: Which mailing lists are there? | |
| 2559 | 647 * Q1.4.3:: Where are the mailing lists archived? |
| 648 * Q1.4.4:: How can I get two instances of info? | |
| 649 * Q1.4.5:: How do I add new Info directories? | |
| 2537 | 650 |
| 651 1.5: Contributing to XEmacs | |
| 652 * Q1.5.1:: How do I submit changes to the FAQ? | |
| 653 * Q1.5.2:: How do I become a beta tester? | |
| 654 * Q1.5.3:: How do I contribute to XEmacs itself? | |
| 2559 | 655 * Q1.5.4:: How do I get started developing XEmacs? |
| 656 * Q1.5.5:: What's the basic layout of the code? | |
| 2537 | 657 |
| 658 1.6: Politics (XEmacs vs. GNU Emacs) | |
| 659 * Q1.6.1:: What is GNU Emacs? | |
| 660 * Q1.6.2:: How does XEmacs differ from GNU Emacs? | |
| 661 * Q1.6.3:: How much does XEmacs differ? | |
| 662 * Q1.6.4:: Is XEmacs "GNU"? | |
| 663 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 664 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged? | |
| 665 | |
| 666 1.7: External Packages | |
| 2559 | 667 * Q1.7.1:: What is the package system? |
| 668 * Q1.7.2:: Which external packages are there? | |
| 669 * Q1.7.3:: Do I need to have the packages to run XEmacs? | |
| 670 * Q1.7.4:: Is there a way to find which package has particular functionality? | |
| 2537 | 671 |
| 672 1.8: Internationalization | |
| 673 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)? | |
| 674 * Q1.8.2:: How can I help with internationalization? | |
| 675 * Q1.8.3:: How do I type non-ASCII characters? | |
| 676 * Q1.8.4:: Can XEmacs messages come out in a different language? | |
| 677 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs | |
| 678 * Q1.8.6:: How do I portably code for MULE/XEmacs? | |
| 679 * Q1.8.7:: How about Cyrillic modes? | |
| 680 * Q1.8.8:: Does XEmacs support Unicode? | |
| 681 * Q1.8.9:: How does XEmacs display Unicode? | |
| 428 | 682 @end menu |
| 683 | |
| 2537 | 684 @unnumberedsec 1.0: What is XEmacs? |
| 2417 | 685 |
| 428 | 686 @node Q1.0.1, Q1.0.2, Introduction, Introduction |
| 687 @unnumberedsubsec Q1.0.1: What is XEmacs? | |
| 688 | |
| 479 | 689 XEmacs is a powerful, highly customizable open source text editor and |
| 2417 | 690 application development system, with full GUI support. It is |
| 691 protected under the GNU Public License and related to other versions | |
| 692 of Emacs, in particular GNU Emacs. Its emphasis is on modern | |
| 693 graphical user interface support and an open software development | |
| 694 model, similar to Linux. XEmacs has an active development community | |
| 695 numbering in the hundreds (and thousands of active beta testers on top | |
| 696 of this), and runs on all versions of MS Windows, on Mac OS X, on | |
| 697 Linux, and on nearly every other version of Unix in existence. | |
| 698 Support for XEmacs has been supplied by Sun Microsystems, University | |
| 699 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl | |
| 700 Corporation, BeOpen, and others, as well as the unpaid time of a great | |
| 701 number of individual developers. | |
| 428 | 702 |
| 703 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction | |
| 704 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs? | |
| 705 | |
| 2417 | 706 XEmacs versions 21.4.* are releases made from the current stable |
| 707 sources. XEmacs versions 21.5.* (which will be released as 22.0) are | |
| 708 releases made from the development sources. Check at | |
| 709 @uref{http://www.xemacs.org} for the current minor version. XEmacs | |
| 710 versions 21.1.* were the previous stable releases, now retired. | |
| 711 | |
| 712 XEmacs 20.4, released in February 1998, was the last release of v20. | |
| 713 | |
| 714 XEmacs 19.16, released in November, 1997. was the last release of v19, | |
| 715 and was also the last version without international language support. | |
| 428 | 716 |
| 717 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction | |
| 2537 | 718 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs? |
| 719 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
720 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
|
721 Kirshenbaum IPA. (See |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
722 @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
|
723 already and want to know how to map from Kirshenbaum to it.) |
| 428 | 724 |
| 725 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction | |
| 2537 | 726 @unnumberedsubsec Q1.0.4: What does XEmacs look like? |
| 727 | |
| 728 Screen snapshots are available at | |
| 729 @uref{http://www.xemacs.org/About/Screenshots/index.html} | |
| 730 as part of the XEmacs website. | |
| 731 | |
| 732 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction | |
| 733 @unnumberedsubsec Q1.0.5: Who wrote XEmacs? | |
| 734 | |
| 735 XEmacs is the result of the time and effort of many people, and the | |
| 736 active developers have changed over time. There are two major | |
| 737 components of the XEmacs effort -- writing the code itself and providing | |
| 738 all the support work (testing the code, releasing beta and final | |
| 739 versions, handling patches, reading bug reports, maintaining the web | |
| 740 site, managing the mailing lists, etc. etc.). Neither component would | |
| 741 work without the other. | |
| 742 | |
| 743 @subheading CODING | |
| 744 | |
| 745 The primary code contributor over the years has been Ben Wing (active | |
| 746 since late 1992). Between 1991 and 1995, large amounts of coding was | |
| 747 contributed by Jamie Zawinski and Chuck Thompson. Many other people | |
| 748 have authored major subsystems or otherwise contributed large amounts of | |
| 749 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris, | |
| 750 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard | |
| 751 Mlynarik, Stig, William Perry and plenty of others. | |
| 752 | |
| 753 Primary XEmacs-specific subsystems and their authors: | |
| 754 | |
| 755 @table @asis | |
| 756 @item Objects | |
| 757 @itemize @minus | |
| 758 @item | |
| 759 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994 | |
| 760 @item | |
| 761 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz | |
| 762 @item | |
| 763 Portable dumper, object descriptions: Olivier Galibert | |
| 764 @item | |
| 765 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students | |
| 766 @item | |
| 767 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing | |
| 768 @item | |
| 769 Profiling: Ben Wing | |
| 770 @item | |
| 771 Some byte-compilation and hash-table improvements: Martin Buchholz | |
| 772 @item | |
| 773 Bignum: Jerry James | |
| 774 @end itemize | |
| 775 | |
| 776 @item Internationalization/Mule | |
| 777 @itemize @minus | |
| 778 @item | |
| 779 mostly Ben Wing; many ideas for future work, Stephen Turnbull | |
| 780 @end itemize | |
| 781 | |
| 782 @item I/O | |
| 783 @itemize @minus | |
| 784 @item | |
| 785 Basic event/event-stream implementation: Jamie Zawinski | |
| 786 @item | |
| 787 Most event work since 1994: Ben Wing | |
| 788 @item | |
| 789 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing | |
| 790 @item | |
| 791 Process method abstraction, Windows process work: Kirill Katsnelson | |
| 792 @item | |
| 793 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing | |
| 794 @item | |
| 795 Lstreams: Ben Wing | |
| 796 @end itemize | |
| 797 | |
| 798 @item Display | |
| 799 @itemize @minus | |
| 800 @item | |
| 801 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people | |
| 802 @item | |
| 803 Glyphs: mostly Ben Wing | |
| 804 @item | |
| 805 Specifiers: Ben Wing | |
| 806 @item | |
| 807 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing | |
| 808 @item | |
| 809 Widgets: Andy Piper | |
| 810 @item | |
| 811 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c}) | |
| 812 @item | |
| 813 Menus: Jamie Zawinski, someone at Lucid (Lucid menus) | |
| 814 @item | |
| 815 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar) | |
| 816 @item | |
| 817 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson | |
| 818 @item | |
| 819 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing | |
| 820 @item | |
| 821 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing | |
| 822 @item | |
| 823 Toolbars: implementation, chuck, much interface work, Ben Wing | |
| 824 @item | |
| 825 Gutters, tabs: andy piper | |
| 826 @end itemize | |
| 827 | |
| 828 @item Device subsystems | |
| 829 @itemize @minus | |
| 830 @item | |
| 4311 | 831 X Windows: Jamie Zawinski, Ben Wing, others |
| 2537 | 832 @item |
| 833 GTK: William Perry, Malcolm Purvis | |
| 834 @item | |
| 835 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing | |
| 836 @item | |
| 837 TTY: Chuck Thompson, Ben Wing | |
| 838 @item | |
| 839 Cygwin: Andy Piper | |
| 840 @end itemize | |
| 841 | |
| 842 @item Misc | |
| 843 @itemize @minus | |
| 844 @item | |
| 845 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz | |
| 846 @item | |
| 847 Most initialization-related code: Ben Wing | |
| 848 @item | |
| 849 Internals manual, much of Lisp manual: Ben Wing | |
| 850 @item | |
| 851 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing | |
| 852 @end itemize | |
| 853 @end table | |
| 854 | |
| 855 @subheading SUPPORT | |
| 856 | |
| 857 Currently, support duties are handled by many different people. | |
| 858 | |
| 859 Release managers have been | |
| 860 | |
| 861 @itemize @minus | |
| 862 @item | |
| 863 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) | |
| 864 @item | |
| 865 Vin Shelton (May 2003 - present, 21.4.13 - present) | |
| 866 @item | |
| 867 Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16) | |
| 868 @item | |
| 869 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) | |
| 870 @item | |
| 871 Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20) | |
| 872 @item | |
| 873 Andy Piper (December 1998, 21.2.6) | |
| 874 @item | |
| 875 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14) | |
| 876 @item | |
| 877 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10) | |
| 878 @end itemize | |
| 879 | |
| 880 The recent overlapping dates are intentional, since two or three trees | |
| 881 are maintained simultaneously at any point. | |
| 882 | |
| 883 Other major support work: | |
| 884 | |
| 885 @itemize @minus | |
| 886 @item | |
| 887 Adrian Aichner wrote and maintains the web site. | |
| 888 @item | |
| 889 Stephen Turnbull has produced many of the beta and semi-stable releases | |
| 890 and has attempted to be the "face" of XEmacs on the newsgroups and | |
| 891 mailing lists. | |
| 892 @item | |
| 893 Steve Youngs currently produces the beta releases (???). | |
| 894 @item | |
| 4311 | 895 Steve Youngs, Ville Skyttä, and now Norbert Koch have taken turns |
| 2537 | 896 maintaining the packages. |
| 897 @item | |
| 898 Vin Shelton maintains the stable releases. | |
| 899 @item | |
| 900 Testing - #### Norbert, Adrian, ??? | |
| 901 @end itemize | |
| 902 | |
| 903 Portraits and email of some of the major developers: | |
| 904 | |
| 905 @itemize @bullet | |
| 906 @item @email{andy@@xemacs.org, Andy Piper} | |
| 907 @html | |
| 908 <br><img src="piper.png" alt="Portrait of Andy Piper"><br> | |
| 909 @end html | |
| 910 | |
| 911 @item @email{ben@@xemacs.org, Ben Wing} | |
| 912 @html | |
| 913 <br><img src="ben.png" alt="Portrait of Ben Wing"><br> | |
| 914 @end html | |
| 915 | |
| 916 @item @email{cthomp@@xemacs.org, Chuck Thompson} | |
| 917 @html | |
| 918 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br> | |
| 919 @end html | |
| 920 | |
| 921 @item @email{hniksic@@xemacs.org, Hrvoje Niksic} | |
| 922 | |
| 923 @html | |
| 924 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br> | |
| 925 @end html | |
| 926 | |
| 927 @item @email{jwz@@jwz.org, Jamie Zawinski} | |
| 928 @html | |
| 929 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br> | |
| 930 @end html | |
| 931 | |
| 932 @item @email{martin@@xemacs.org, Martin Buchholz} | |
| 933 @html | |
| 934 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br> | |
| 935 @end html | |
| 936 | |
| 937 @item @email{mly@@adoc.xerox.com, Richard Mlynarik} | |
| 938 @html | |
| 939 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br> | |
| 940 @end html | |
| 941 | |
| 942 @item @email{stephen@@xemacs.org, Stephen Turnbull} | |
| 943 | |
| 944 @item @email{steve@@xemacs.org, Steve Baur} | |
| 945 @html | |
| 946 <br><img src="slb.png" alt="Portrait of Steve Baur"><br> | |
| 947 @end html | |
| 948 @end itemize | |
| 949 | |
| 950 Many other people have contributed to XEmacs; this is partially | |
| 951 enumerated in the @samp{About XEmacs} option in the Help menu. | |
| 952 | |
| 953 @node Q1.0.6, Q1.1.1, Q1.0.5, Introduction | |
| 954 @unnumberedsubsec Q1.0.6: Who wrote the FAQ? | |
| 955 | |
| 956 The current version of this FAQ was created by @email{ben@@xemacs.org, | |
| 957 Ben Wing}. | |
| 958 | |
| 959 Previous contributors to the FAQ include | |
| 960 | |
| 961 @itemize @bullet | |
| 962 @item @email{steve@@xemacs.org, SL Baur} | |
| 963 | |
| 964 @item @email{hniksic@@xemacs.org, Hrvoje Niksic} | |
| 965 | |
| 966 @item @email{binge@@aloft.att.com, Curtis.N.Bingham} | |
| 967 | |
| 968 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} | |
| 969 | |
| 970 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley} | |
| 971 | |
| 972 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot} | |
| 973 | |
| 974 @item @email{daku@@nortel.ca, Mark Daku} | |
| 975 | |
| 976 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque} | |
| 977 | |
| 978 @item @email{eeide@@cs.utah.edu, Eric Eide} | |
| 979 | |
| 980 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet} | |
| 981 | |
| 982 @item @email{cflatter@@nrao.edu, Chris Flatters} | |
| 983 | |
| 984 @item @email{ginsparg@@adra.com, Evelyn Ginsparg} | |
| 985 | |
| 986 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall} | |
| 987 | |
| 988 @item @email{dkindred@@cmu.edu, Darrell Kindred} | |
| 989 | |
| 990 @item @email{dmoore@@ucsd.edu, David Moore} | |
| 991 | |
| 992 @item @email{arup+@@cmu.edu, Arup Mukherjee} | |
| 993 | |
| 994 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen} | |
| 995 | |
| 996 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell} | |
| 997 | |
| 998 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy} | |
| 999 | |
| 1000 @item @email{stig@@hackvan.com, Stig} | |
| 1001 | |
| 1002 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari} | |
| 1003 @end itemize | |
| 1004 | |
| 1005 @unnumberedsec 1.1: Getting XEmacs | |
| 1006 | |
| 1007 @node Q1.1.1, Q1.1.2, Q1.0.6, Introduction | |
| 1008 @unnumberedsubsec Q1.1.1: Where can I find XEmacs? | |
| 1009 | |
| 1010 To download XEmacs, visit the XEmacs WWW page at | |
| 1011 @uref{http://www.xemacs.org/Download/}. The most up-to-date list of | |
| 1012 distribution sites can always be found there. Try to pick a site that | |
| 1013 is networkologically close to you. If you know of other mirrors of | |
| 1014 the XEmacs archives, please send e-mail to | |
| 1015 @uref{mailto:webmaster@@xemacs.org} and we will list them here as well. | |
| 1016 | |
| 1017 The canonical distribution point is ftp.xemacs.org, available either | |
| 1018 through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP | |
| 1019 (@uref{ftp://ftp.xemacs.org/pub/xemacs/}). | |
| 1020 | |
| 1021 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction | |
| 1022 @unnumberedsubsec Q1.1.2: Are binaries available? | |
| 2417 | 1023 |
| 1024 MS Windows binaries are available at | |
| 1025 @uref{http://www.xemacs.org/Download/win32/} for the native versions | |
| 1026 of 21.4 and 21.1. Cygwin binaries are now available as part of the | |
| 1027 standard Cygwin installation process. XEmacs also comes pre-built as | |
| 1028 part of many Linux distributions, such as Red Hat and SuSE. | |
| 1029 | |
| 1030 Otherwise, you will need to build XEmacs yourself or get your system | |
| 1031 administrator to do it. Generally, this is not a difficult process | |
| 1032 under Unix and Mac OS X, as XEmacs has been tested under all of the | |
| 1033 common Unix versions and under Mac OS X and comes with an extensive | |
| 1034 configure script that is able to automatically detect most aspects of | |
| 1035 the configuration of your particular system. | |
| 1036 | |
| 2537 | 1037 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction |
| 1038 @unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources? | |
| 1039 | |
| 1040 If you are interested in developing XEmacs, or getting the absolutely most | |
| 1041 recent, up-to-the-moment, bleeding-edge source code, you can directly | |
| 1042 access the master CVS source tree (read-only, of course, until you ask for | |
| 1043 and are granted permission to directly modify portions of the source tree) | |
| 1044 at cvs.xemacs.org. Directions on how to access the source tree are located | |
| 1045 at @uref{http://www.xemacs.org/Develop/cvsaccess.html}. | |
| 1046 | |
| 1047 Nightly CVS snapshots are available at | |
| 1048 @uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}. | |
| 1049 | |
| 1050 @node Q1.1.4, Q1.2.1, Q1.1.3, Introduction | |
| 1051 @unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 1052 | |
| 1053 Pre-printed manuals are not available. If you are familiar with | |
| 1054 TeX, you can generate your own manual from the XEmacs sources. | |
| 1055 | |
| 1056 HTML and Postscript versions of XEmacs manuals are available from the | |
| 1057 XEmacs web site at | |
| 1058 @uref{http://www.xemacs.org/Documentation/index.html}. | |
| 1059 | |
| 1060 @unnumberedsec 1.2: Versions for Different Operating Systems | |
| 1061 | |
| 1062 @node Q1.2.1, Q1.2.2, Q1.1.4, Introduction | |
| 1063 @unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs? | |
| 1064 | |
| 1065 No. The name @dfn{XEmacs} is unfortunate in the sense that it is | |
| 1066 @strong{not} an X Window System-only version of Emacs. XEmacs has | |
| 1067 full color support on a color-capable character terminal. | |
| 1068 | |
| 1069 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction | |
| 1070 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on? | |
| 1071 | |
| 2559 | 1072 XEmacs is regularly tested on Linux, Solaris, SunOS, HP/UX, FreeBSD, |
| 1073 OpenBSD, BSD/OS aka BSDI, Tru64 aka DEC/OSF, SCO5, and probably | |
| 1074 others. It should work on all versions of Unix created in the last 10 | |
| 1075 years or so, perhaps with a bit of work on more obscure platforms to | |
| 1076 correct bit-rot. It uses a sophisticated configuration system to | |
| 1077 auto-detect zillions of features that are implemented differently in | |
| 1078 different versions of Unix, so it will probably work on your vendor's | |
| 1079 version, possibly with a bit of tweaking, even if we've never heard of | |
| 1080 it. | |
| 1081 | |
| 2537 | 1082 For problems with particular machines and versions of Unix, see the |
| 1083 @file{PROBLEMS} file. | |
| 1084 | |
| 1085 Much effort has gone into making XEmacs work on as many different | |
| 1086 machines, configurations, and compilers as possible. | |
| 1087 | |
| 1088 Much effort has gone into making XEmacs 64-bit clean. | |
| 1089 | |
| 1090 Much effort has gone into removing system-specific code, and replacing | |
| 1091 such code with autodetection at configure time. | |
| 1092 | |
| 1093 The XEmacs core should build "out of the box" on most Unix-like systems. | |
| 1094 | |
| 1095 XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix | |
| 1096 configurations as of 2001-02-10: | |
| 1097 | |
| 1098 @example | |
| 1099 alphaev56-dec-osf4.0e (both Compaq C and gcc) | |
| 1100 i386-unknown-freebsd4.2 | |
| 1101 i386-unknown-netbsdelf1.5 | |
| 1102 i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc) | |
| 1103 i686-pc-linux-gnu | |
| 1104 hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc) | |
| 1105 mips-sgi-irix6.5 (both MIPSpro cc and gcc) | |
| 1106 rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc) | |
| 1107 sparc-sun-solaris2.6 (both Sun's Forte C and gcc) | |
| 1108 sparc-sun-solaris2.7 (both Sun's Forte C and gcc) | |
| 1109 sparc-sun-sunos4.1.4 (gcc) | |
| 1110 @end example | |
| 1111 | |
| 3018 | 1112 Some systems have a dual mode 32-bit/64-bit compiler. On most of these, |
| 1113 XEmacs requires the @samp{--pdump} (in XEmacs 21.5, | |
| 1114 @samp{--enable-pdump}) configure option to build correctly with the | |
| 1115 64-bit version of the compiler. | |
| 2537 | 1116 |
| 1117 @example | |
| 1118 mips-sgi-irix6.5, CC="gcc -mabi=64" | |
| 1119 mips-sgi-irix6.5, CC="cc -64" | |
| 1120 rs6000-ibm-aix4.3.0.0, CC="cc -q64" | |
| 1121 @end example | |
| 1122 | |
| 1123 On most of these systems, XEmacs also builds with a C++ compiler, | |
| 1124 but not "out of the box". This feature is only for use by the | |
| 1125 maintainers. | |
| 1126 | |
| 1127 XEmacs 21.2 is known @emph{not} to work on any machines with m680x0 | |
| 1128 processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there. | |
| 1129 | |
| 1130 VMS has never been supported by XEmacs. In fact, all the old VMS code | |
| 1131 inherited from Emacs has been removed. Sorry, all you VMS fans out there. | |
| 1132 | |
| 1133 @node Q1.2.3, Q1.2.4, Q1.2.2, Introduction | |
| 1134 @unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows? | |
| 1135 | |
| 1136 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows | |
| 1137 and is fully-featured and actively developed. A group of dedicated | |
| 1138 developers actively maintains and improves the Windows-specific | |
| 1139 portions of the code. Some of the core developers, in fact, use | |
| 1140 Windows as their only development environment, and some features, such | |
| 1141 as printing, actually work better on Windows than native Unix and Mac | |
| 1142 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated | |
| 1143 to that effort (please use the -request address to | |
| 1144 subscribe). (Despite its name, XEmacs actually works on all versions | |
| 1145 of Windows.) | |
| 1146 | |
| 1147 The list name is misleading, as XEmacs supports and has been compiled on | |
| 1148 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows | |
| 1149 XP, and all newer versions of Windows. The MS Windows-specific code is | |
| 1150 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on | |
| 1151 MS-DOS. | |
| 1152 | |
| 1153 XEmacs also supports the Cygwin and MinGW development and runtime | |
| 1154 environments, where it also uses native Windows code for graphical | |
| 1155 features. In addition, under Cygwin it is possible to compile XEmacs | |
| 1156 to use an X server (and XFree86 is available as part of the standard | |
| 1157 Cygwin installation). | |
| 1158 | |
| 1159 @node Q1.2.4, Q1.2.5, Q1.2.3, Introduction | |
| 1160 @unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 1161 | |
| 1162 Yes, you can, but no you do not need to. In fact, we recommend that you | |
| 1163 use a native-GUI version unless you have a specific need for an X | |
| 1164 version. | |
| 1165 | |
| 1166 @node Q1.2.5, Q1.2.6, Q1.2.4, Introduction | |
| 1167 @unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 1168 | |
| 1169 To answer the second part of the question: No, you, you don't need | |
| 1170 Cygwin or MinGW to build or to run XEmacs. But if you have them and | |
| 1171 want to use them, XEmacs supports these environments. | |
| 1172 | |
| 1173 (One important reason to support Cygwin is that it lets the MS Windows | |
| 1174 developers test out their code in a Unix environment without actually | |
| 1175 having to have a Unix machine around. For this reason alone, Cygwin | |
| 1176 support is likely to remain supported for a long time in XEmacs. Same | |
| 1177 goes for the X support under Cygwin, for the same reasons. MinGW | |
| 1178 support, on the other hand, depends on volunteers to keep it up to date; | |
| 1179 but this is generally not hard.) | |
| 1180 | |
| 1181 Cygwin is a set of tools providing Unix-like API on top of Win32. | |
| 1182 It makes it easy to port large Unix programs without significant | |
| 1183 changes to their source code. It is a development environment as well | |
| 1184 as a runtime environment. | |
| 1185 | |
| 1186 When built with Cygwin, XEmacs supports all display types -- TTY, X & | |
| 1187 Win32 GUI, and can be built with support for all three simultaneously. | |
| 1188 If you build with Win32 GUI support then the Cygwin version uses the | |
| 1189 majority of the Windows-specific code, which is mostly related to | |
| 1190 display. If you want to build with X support you need X libraries (and | |
| 2559 | 1191 an X server to display XEmacs on); see @ref{Q2.3.7}. TTY and Win32 GUI |
| 2537 | 1192 require no additional libraries beyond what comes standard with Cygwin. |
| 1193 | |
| 1194 The advantages of the Cygwin version are that it integrates well with | |
| 1195 the Cygwin environment for existing Cygwin users; uses configure so | |
| 1196 building with different features is very easy; and actively supports X & | |
| 1197 TTY. Furthermore, the entire Cygwin environment and compiler are free, | |
| 1198 whereas Visual C++ costs money. | |
| 1199 | |
| 1200 The disadvantage is that it requires the whole Cygwin environment, | |
| 1201 whereas the native port requires only a suitable MS Windows compiler. | |
| 1202 Also, it follows the Unix filesystem and process model very closely | |
| 1203 (some will undoubtedly view this as an advantage). | |
| 1204 | |
| 1205 See @uref{http://www.cygwin.com/} for more information on | |
| 1206 Cygwin. | |
| 1207 | |
| 1208 MinGW is a collection of header files and import libraries that allow | |
| 1209 one to use GCC under the Cygwin environment to compile and produce | |
| 1210 exactly the same native Win32 programs that you can using Visual C++. | |
| 1211 Programs compiled with MinGW make use of the standard Microsoft runtime | |
| 1212 library @file{MSVCRT.DLL}, present on all Windows systems, and look, | |
| 1213 feel, and act like a standard Visual-C-produced application. (The only | |
| 1214 difference is the compiler.) This means that, unlike a | |
| 1215 standardly-compiled Cygwin application, no extra runtime support | |
| 1216 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the | |
| 1217 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y | |
| 1218 environment, for those die-hard Unix hackers out there), is the main | |
| 1219 advantage of MinGW. It is also potentially faster than Cygwin because | |
| 1220 it has less overhead when calling Windows, but you lose the POSIX | |
| 1221 emulation layer, which makes Unix programs harder to port. (But this is | |
| 1222 irrelevant for XEmacs since it's already ported to Win32.) | |
| 1223 | |
| 1224 See @uref{http://www.mingw.org/} for more information on MinGW. | |
| 1225 | |
| 1226 @node Q1.2.6, Q1.2.7, Q1.2.5, Introduction | |
| 1227 @unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen? | |
| 1228 | |
| 1229 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing. | |
| 1230 Could you briefly explain the differences between them? | |
| 1231 | |
| 1232 Here is a recount of various Emacs versions running on MS Windows: | |
| 1233 | |
| 1234 @itemize @bullet | |
| 1235 | |
| 1236 @item | |
| 1237 XEmacs | |
| 1238 | |
| 1239 @itemize @minus | |
| 1240 | |
| 1241 @item | |
| 1242 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned | |
| 1243 in such a way to allow clean support of multiple window systems. At | |
| 1244 this time the TTY support was added, making X and TTY the first two | |
| 1245 "window systems" supported by XEmacs. The 19.12 design is the basis for | |
| 1246 the current native MS Windows code. | |
| 1247 | |
| 1248 @item | |
| 1249 Some time during 1997, David Hobley (soon joined by Marc Paquette) | |
| 1250 imported some of the NT-specific portions of GNU Emacs, making XEmacs | |
| 1251 with X support compile under Windows NT, and creating the "X" port. | |
| 1252 | |
| 1253 @item | |
| 1254 Several months later, Jonathan Harris sent out initial patches to use | |
| 1255 the Win32 API, thus creating the native port. Since then, various | |
| 1256 people have contributed, including Kirill M. Katsnelson (contributed | |
| 1257 support for menubars, subprocesses and network, as well as loads of | |
| 1258 other code), Andy Piper (ported XEmacs to Cygwin environment, | |
| 1259 contributed Windows unexec, Windows-specific glyphs and toolbars code, | |
| 1260 and more), Ben Wing (loads of improvements; primary MS Windows developer | |
| 1261 since 2000), Jeff Sparkes (contributed scrollbars support) and many | |
| 1262 others. | |
| 1263 @end itemize | |
| 1264 | |
| 1265 @item | |
| 1266 NT Emacs | |
| 1267 | |
| 1268 @itemize @minus | |
| 1269 | |
| 1270 @item | |
| 1271 NT Emacs was an early version of GNU Emacs 19 modified to compile and | |
| 1272 run under MS Windows 95 and NT using the native Win32 API. It was | |
| 1273 written by Geoff Voelker, and has long since been incorporated into | |
| 1274 the mainline GNU Emacs distribution. | |
| 1275 @end itemize | |
| 1276 | |
| 1277 @item | |
| 1278 Win-Emacs | |
| 1279 | |
| 1280 @itemize @minus | |
| 1281 | |
| 1282 @item | |
| 1283 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X | |
| 1284 compatibility libraries. Win-Emacs was written by Ben Wing. The MS | |
| 1285 Windows code never made it back to Lucid Emacs, and its creator (Pearl | |
| 1286 Software) has long since gone out of business. | |
| 1287 @end itemize | |
| 1288 | |
| 1289 @item | |
| 1290 GNU Emacs for DOS | |
| 1291 | |
| 1292 @itemize @minus | |
| 1293 | |
| 1294 @item | |
| 1295 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS | |
| 1296 port of GCC). Such an Emacs is heavily underfeatured, because it does | |
| 1297 not support long file names, lacks proper subprocesses support, and | |
| 1298 is far too big compared with typical DOS editors. | |
| 1299 @end itemize | |
| 1300 | |
| 1301 @item | |
| 1302 GNU Emacs compiled with Win32 | |
| 1303 | |
| 1304 @itemize @minus | |
| 1305 | |
| 1306 @item | |
| 1307 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs | |
| 1308 under MS Windows using the DJGPP compiler and X libraries. The result | |
| 1309 is very similar to GNU Emacs compiled under MS DOS, only it works | |
| 1310 somewhat better because it runs in 32-bit mode, makes use of all the | |
| 1311 system memory, supports long file names, etc. | |
| 1312 @end itemize | |
| 1313 | |
| 1314 @end itemize | |
| 1315 | |
| 1316 @node Q1.2.7, Q1.2.8, Q1.2.6, Introduction | |
| 1317 @unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface? | |
| 1318 | |
| 1319 The XEmacs (and Emacs in general) user interface is pretty different | |
| 1320 from what is expected of a typical MS Windows program. How does the MS | |
| 1321 Windows port cope with it? | |
| 1322 | |
| 1323 As a general rule, we follow native MS Windows conventions as much as | |
| 1324 possible. 21.4 is a fairly complete Windows application, supporting | |
| 1325 native printing, system file dialog boxes, tool tips, etc. In cases | |
| 1326 where there's a clear UI conflict, we currently use normal Unix XEmacs | |
| 1327 behavior by default, but make sure the MS Windows "look and feel" (mark | |
| 1328 via shift-arrow, self-inserting deletes region, Alt selects menu items, | |
| 1329 etc.) is easily configurable (respectively: using the variable | |
| 1330 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact | |
| 1331 the default in these versions], or the @file{pc-select} package; using | |
| 1332 the @file{pending-del} package; and setting the variable | |
| 1333 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above). | |
| 1334 In fact, if you use the sample @file{init.el} file as your init file, | |
| 1335 you will get all these behaviors automatically turned on. | |
| 1336 | |
| 1337 In future versions, some of these features might be turned on by | |
| 1338 default in the MS Windows environment. | |
| 1339 | |
| 1340 @node Q1.2.8, Q1.2.9, Q1.2.7, Introduction | |
| 1341 @unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh? | |
| 1342 | |
| 1343 Yes. | |
| 1344 | |
| 1345 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly | |
| 1346 will not feel very much like a Mac application as it has no Mac-specific | |
| 1347 code in it. | |
| 1348 | |
| 1349 There is also a port of XEmacs 19.14 that works on all recent versions | |
| 1350 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com, | |
| 1351 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY | |
| 1352 mode only (one single Macintosh window, 25 colors), but has a large | |
| 1353 number of Mac-specific additions. It's available at | |
| 1354 @uref{http://homepage.mac.com/pjarvis/xemacs.html}. | |
| 1355 | |
| 1356 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction | |
| 2559 | 1357 @unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS? |
| 1358 | |
| 1359 No. We have never supported running on MS-DOS or Windows 3.1, and in | |
| 1360 fact have long since deleted all MS-DOS-related code. We're not | |
| 1361 particularly interested in patches for these platforms, as they would | |
| 1362 introduce huge amounts of code clutter due to the woefully | |
| 1363 underfeatured nature of these systems. (See GNU Emacs for a port to | |
| 1364 MS-DOS.) | |
| 2537 | 1365 |
| 1366 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction | |
| 2559 | 1367 @unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2? |
| 2537 | 1368 |
| 1369 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point | |
| 1370 working on it. | |
| 1371 | |
| 2559 | 1372 @node Q1.2.11, Q1.2.12, Q1.2.10, Introduction |
| 1373 @unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep? | |
| 2537 | 1374 |
| 1375 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did | |
| 1376 the port of GNU Emacs to NeXTstep and expressed interest in doing the | |
| 1377 XEmacs port, but never went any farther. | |
| 1378 | |
| 2559 | 1379 @node Q1.2.12, Q1.3.1, Q1.2.11, Introduction |
| 1380 @unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS? | |
| 2537 | 1381 |
| 1382 VMS has never been supported by XEmacs. In fact, all the old VMS code | |
| 1383 inherited from GNU Emacs has been removed. Sorry, all you VMS fans | |
| 1384 out there. | |
| 1385 | |
| 1386 @unnumberedsec 1.3: Getting Started | |
| 1387 | |
| 2559 | 1388 @node Q1.3.1, Q1.3.2, Q1.2.12, Introduction |
| 2537 | 1389 @unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one? |
| 1390 | |
| 1391 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to | |
| 1392 your tastes. Starting in 21.4, the preferred location for the init file | |
| 1393 is @file{~/.xemacs/init.el}; in previous versions, it was | |
| 1394 @file{~/.emacs}. 21.4 still accepts the old location, but the first | |
| 1395 time you run it, it will ask to migrate your file to the new location. | |
| 1396 If you answer yes, the file will be moved, and a "compatibility" | |
| 1397 @file{.emacs} file will be placed in the old location so that you can | |
| 1398 still run older versions of XEmacs, and versions of GNU Emacs, which | |
| 1399 expect the old location. The @file{.emacs} file present is just a stub | |
| 1400 that loads the real file in @file{~/.xemacs/init.el}. | |
| 1401 | |
| 1402 No two init files are alike, nor are they expected to be alike, but | |
| 1403 that's the point. The XEmacs distribution contains an excellent starter | |
| 1404 example in the @file{etc/} directory called @file{sample.init.el} | |
| 1405 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this | |
| 1406 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or | |
| 1407 @file{~/.emacs} in older versions, where @samp{~} means your home | |
| 1408 directory, of course. Then edit it to suit. | |
| 1409 | |
| 1410 You may bring the @file{sample.init.el} or @file{sample.emacs} file into | |
| 1411 an XEmacs buffer from the menubar. (The menu entry for it is always | |
| 1412 under the @samp{Help} menu, but its location under that has changed in | |
| 1413 various versions. Recently, look under the @samp{Samples} submenu.) To | |
| 1414 determine the location of the @file{etc/} directory type the command | |
| 1415 @kbd{C-h v data-directory @key{RET}}. | |
| 1416 | |
| 1417 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction | |
| 1418 @unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file? | |
| 1419 | |
| 1420 @file{init.el} is the name of the init file starting with 21.4, and is | |
| 1421 located in the subdirectory @file{.xemacs/} of your home directory. In | |
| 1422 prior versions, the init file is called @file{.emacs} and is located in | |
| 1423 your home directory. | |
| 1424 | |
| 1425 Your home directory under Windows is determined by the @samp{HOME} | |
| 1426 environment variable. If this is not set, it defaults to @samp{C:\}. | |
| 1427 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or | |
| 1428 select @samp{Control Panel->System->Advanced->Environment Variables...} | |
| 1429 under Windows NT/2000. | |
| 1430 | |
| 1431 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction | |
| 1432 @unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs? | |
| 1433 | |
| 1434 Yes. The sample @file{init.el} included in the XEmacs | |
| 1435 distribution will show you how to handle different versions and flavors | |
| 1436 of Emacs. | |
| 1437 | |
| 1438 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction | |
| 1439 @unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around? | |
| 1440 | |
| 1441 There's the XEmacs tutorial available from the Help Menu under | |
| 1442 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether | |
| 1443 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type | |
| 1444 the first letters of your preferred language, then type @key{RET}. | |
| 1445 | |
| 1446 @comment There's an Emacs Lisp tutorial at | |
| 1447 @comment | |
| 1448 @comment @example | |
| 1449 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}. | |
| 1450 @comment @end example | |
| 1451 @comment | |
| 1452 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web | |
| 1453 @comment page at | |
| 1454 @comment @iftex | |
| 1455 @comment @* | |
| 1456 @comment @end iftex | |
| 1457 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}. | |
| 1458 | |
| 1459 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction | |
| 1460 @unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function? | |
| 1461 | |
| 1462 The following function does a little bit of everything useful. It does | |
| 1463 something with the prefix argument, it examines the text around the | |
| 1464 cursor, and it's interactive so it may be bound to a key. It inserts | |
| 1465 copies of the current word the cursor is sitting on at the cursor. If | |
| 1466 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will | |
| 1467 insert 3 copies. | |
| 1468 | |
| 1469 @lisp | |
| 1470 (defun double-word (count) | |
| 1471 "Insert a copy of the current word underneath the cursor" | |
| 1472 (interactive "*p") | |
| 1473 (let (here there string) | |
| 1474 (save-excursion | |
| 1475 (forward-word -1) | |
| 1476 (setq here (point)) | |
| 1477 (forward-word 1) | |
| 1478 (setq there (point)) | |
| 1479 (setq string (buffer-substring here there))) | |
| 1480 (while (>= count 1) | |
| 1481 (insert string) | |
| 1482 (decf count)))) | |
| 1483 @end lisp | |
| 1484 | |
| 1485 The best way to see what is going on here is to let XEmacs tell you. | |
| 1486 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor | |
| 1487 sitting just to the right of the function you want explained. Eg. move | |
| 1488 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and | |
| 1489 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing | |
| 1490 this will tell you that the @code{*} requires a writable buffer, and | |
| 1491 @code{p} converts the prefix argument to a number, and | |
| 1492 @code{interactive} allows you to execute the command with @kbd{M-x}. | |
| 1493 | |
| 1494 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction | |
| 1495 @unnumberedsubsec Q1.3.6: And how do I bind it to a key? | |
| 1496 | |
| 1497 To bind to a key do: | |
| 1498 | |
| 1499 @lisp | |
| 1500 (global-set-key "\C-cd" 'double-word) | |
| 1501 @end lisp | |
| 1502 | |
| 1503 Or interactively, @kbd{M-x global-set-key} and follow the prompts. | |
| 1504 | |
| 1505 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction | |
| 1506 @unnumberedsubsec Q1.3.7: What's the difference between a macro and a function? | |
| 1507 | |
| 1508 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual: | |
| 1509 | |
| 1510 @dfn{Macros} enable you to define new control constructs and other | |
| 1511 language features. A macro is defined much like a function, but instead | |
| 1512 of telling how to compute a value, it tells how to compute another Lisp | |
| 1513 expression which will in turn compute the value. We call this | |
| 1514 expression the @dfn{expansion} of the macro. | |
| 1515 | |
| 1516 Macros can do this because they operate on the unevaluated expressions | |
| 1517 for the arguments, not on the argument values as functions do. They can | |
| 1518 therefore construct an expansion containing these argument expressions | |
| 1519 or parts of them. | |
| 1520 | |
| 1521 Do not confuse the two terms with @dfn{keyboard macros}, which are | |
| 1522 another matter, entirely. A keyboard macro is a key bound to several | |
| 1523 other keys. Refer to manual for details. | |
| 1524 | |
| 1525 @node Q1.3.8, Q1.4.1, Q1.3.7, Introduction | |
| 1526 @unnumberedsubsec Q1.3.8: What is @code{Custom}? | |
| 1527 | |
| 1528 @code{Custom} is a system for customizing XEmacs options. | |
| 1529 | |
| 1530 You can access @code{Advanced (Customize)} from the @code{Options} menu | |
| 1531 or invoking one of customize commands by typing eg. | |
| 1532 @kbd{M-x customize}, @kbd{M-x customize-face}, | |
| 1533 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}. | |
| 1534 | |
| 1535 There is also new @samp{browser} mode for Customize. | |
| 1536 Try it out with @kbd{M-x customize-browse} | |
| 1537 | |
| 1538 @unnumberedsec 1.4: Getting Help | |
| 1539 | |
| 1540 @node Q1.4.1, Q1.4.2, Q1.3.8, Introduction | |
| 1541 @unnumberedsubsec Q1.4.1: Where can I get help? | |
| 1542 | |
| 1543 Probably the easiest way, if everything is installed, is to use Info, by | |
| 1544 pressing @kbd{C-h i}, or looking for an Info item on the | |
| 1545 Help Menu. @kbd{M-x apropos} can be used to look for particular commands. | |
| 1546 | |
| 1547 For items not found in the manual, try reading this FAQ | |
| 1548 and reading the Usenet group comp.emacs.xemacs. | |
| 1549 | |
| 1550 If you choose to post to a newsgroup, @strong{please use | |
| 1551 comp.emacs.xemacs}. Please do not post XEmacs related questions to | |
| 1552 gnu.emacs.help. | |
| 1553 | |
| 1554 If you cannot post or read Usenet news, there is a corresponding mailing | |
| 1555 list @email{xemacs-news@@xemacs.org} which is available. It can be | |
| 1556 subscribed to via the Mailman Web interface or by sending mail to to | |
| 1557 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the | |
| 1558 body of the message. See also | |
| 1559 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a | |
| 1560 subscription, you may use the @email{xemacs-news-request@@xemacs.org} | |
| 1561 address or the Web interface. Send a message with a subject of | |
| 1562 @samp{unsubscribe} to be removed. | |
| 1563 | |
| 1564 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction | |
| 1565 @unnumberedsubsec Q1.4.2: Which mailing lists are there? | |
| 1566 | |
| 1567 For complete, up-to-date info on the lists and how to subscribe, see | |
| 1568 @uref{http://www.xemacs.org/Lists/}. | |
| 1569 | |
| 1570 @table @samp | |
| 1571 | |
| 1572 @item comp.emacs.xemacs | |
| 1573 is a Usenet newsgroup | |
| 1574 for XEmacs users to discuss problems and issues that arise | |
| 1575 for them. It's not generally an appropriate place to ask | |
| 1576 about apparent bugs (use @samp{xemacs-beta}), or future plans | |
| 1577 (use @samp{xemacs-design}). | |
| 1578 | |
| 1579 @item xemacs-announce | |
| 1580 is a read-only, low | |
| 1581 volume list for announcements concerning the XEmacs project | |
| 1582 and new releases of the XEmacs software. | |
| 1583 | |
| 1584 @item xemacs-beta | |
| 2559 | 1585 is an open list for bug reports about beta versions of XEmacs. This |
| 1586 includes the bug reports themselves, by both users and developers, as | |
| 1587 well as queries, follow-ups, and discussions further determining their | |
| 1588 nature and status. This is the primary channel for this kind of | |
| 1589 discussion; related code changes will usually not be applied until | |
| 1590 they have been discussed here. When such discussions touch on | |
| 1591 significant changes to the code (in particular, structural changes), | |
| 1592 or on changes to API's or external functionality, they should be moved | |
| 1593 to @samp{xemacs-design}. Requests and proposals for non-bug-related | |
| 1594 changes do not belong on @samp{xemacs-beta}, and should be sent to | |
| 1595 @samp{xemacs-design} instead. | |
| 2537 | 1596 |
| 1597 @item xemacs-beta-ja | |
| 1598 is an open list for bug | |
| 1599 reports and design discussion related to Mule features, | |
| 1600 including Japanese handling, in beta versions of XEmacs. | |
| 1601 Japanese is the preferred language of discussion. For most | |
| 1602 timely presentation to reviewers, please consider sending | |
| 1603 appropriate discussion to @samp{xemacs-mule} or | |
| 1604 @samp{xemacs-design} in English when convenient for | |
| 1605 the participants in discussion. When possible, bug reports | |
| 1606 not related to Mule (including Japanese) should be reported on | |
| 1607 @samp{xemacs-beta} in English. | |
| 1608 | |
| 1609 @item xemacs-buildreports | |
| 1610 is an open list for | |
| 1611 submission of build-reports on beta versions of XEmacs. For | |
| 1612 information on what the build-reports should contain, please | |
| 1613 see the `etc/BETA' file which is included in each beta | |
| 1614 distribution. | |
| 1615 | |
| 1616 @item xemacs-cvs | |
| 1617 is a read-only list for notices | |
| 1618 and information on what has been committed to the XEmacs CVS | |
| 1619 trees, by whom, and for what. | |
| 1620 | |
| 1621 @item xemacs-design | |
| 1622 is an open list for | |
| 1623 discussing the design of XEmacs. This includes discussion | |
| 1624 about planned and ongoing changes to functionality and API | |
| 1625 changes and additions as well as requests for them. This is | |
| 1626 the primary channel for this kind of discussion; related code | |
| 1627 changes will usually not be applied until they have been | |
| 1628 discussed here. This does not include bug reports, which go | |
| 1629 to @samp{xemacs-beta}. | |
| 1630 | |
| 1631 @item xemacs-mule | |
| 1632 is an open mailing list for | |
| 1633 discussion of International extensions to XEmacs including | |
| 1634 Mule, XIM, I18n issues, etc, and is not confined to | |
| 1635 developmental issues. This list is not restricted to | |
| 1636 English, postings in all languages are welcome. | |
| 1637 | |
| 1638 @item xemacs-news | |
| 1639 is an open list for discussion | |
| 1640 and bug reporting for XEmacs. This mailing list is | |
| 1641 bi-directionally gatewayed with the USENET newsgroup | |
| 1642 comp.emacs.xemacs. | |
| 1643 | |
| 1644 @item xemacs-nt | |
| 1645 is a developers-only mailing | |
| 1646 list and is intended for people who wish to work actively on | |
| 1647 the porting of XEmacs to Microsoft Windows NT and Microsoft | |
| 1648 Windows '95. | |
| 1649 | |
| 1650 @item xemacs-patches | |
| 1651 is an open, moderated | |
| 1652 list for submission of patches to the XEmacs distribution | |
| 1653 and its packages. Anyone may subscribe or submit to | |
| 1654 xemacs-patches, but all submissions are reviewed by the list | |
| 1655 moderator before they are distributed to the | |
| 1656 list. Discussion is not appropriate on xemacs-patches. | |
| 1657 | |
| 1658 @item xemacs-users-ja | |
| 1659 is an open list for | |
| 1660 discussion and bug reporting for XEmacs. Japanese is the | |
| 1661 preferred language of discussion. It is not gated to | |
| 1662 comp.emacs.xemacs or the @samp{xemacs} list. For | |
| 1663 fastest response, bugs not specifically related to Japanese | |
| 1664 or Mule features should be reported on | |
| 1665 @samp{xemacs-beta} (in English). | |
| 1666 | |
| 1667 @item xemacs-users-ru | |
| 1668 is an open list for | |
| 1669 discussion and bug reporting for XEmacs. Russian is the | |
| 1670 preferred language of discussion. It is not gated to | |
| 1671 comp.emacs.xemacs or the @samp{xemacs} list. For | |
| 1672 fastest response, bugs not specifically related to Russian | |
| 1673 or Mule features should be reported on | |
| 1674 @samp{xemacs-beta} (in English). | |
| 1675 @end table | |
| 1676 | |
| 1677 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction | |
| 1678 @unnumberedsubsec Q1.4.3: Where are the mailing lists archived? | |
| 1679 | |
| 1680 The archives can be found at @uref{http://list-archive.xemacs.org} | |
| 1681 | |
| 1682 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction | |
| 1683 @unnumberedsubsec Q1.4.4: How can I get two instances of info? | |
| 1684 | |
| 1685 Before 21.4, you can't. The @code{info} package does not provide for | |
| 1686 multiple info buffers. In 21.4, this should be fixed. #### how? | |
| 1687 | |
| 1688 @node Q1.4.5, Q1.5.1, Q1.4.4, Introduction | |
| 1689 @unnumberedsubsec Q1.4.5: How do I add new Info directories? | |
| 1690 | |
| 1691 You use something like: | |
| 1692 | |
| 1693 @lisp | |
| 1694 (setq Info-directory-list (cons | |
| 1695 (expand-file-name "~/info") | |
| 1696 Info-default-directory-list)) | |
| 1697 @end lisp | |
| 1698 | |
| 1699 @email{davidm@@prism.kla.com, David Masterson} writes: | |
| 1700 | |
| 1701 @quotation | |
| 1702 Emacs Info and XEmacs Info do many things differently. If you're trying to | |
| 1703 support a number of versions of Emacs, here are some notes to remember: | |
| 1704 | |
| 1705 @enumerate | |
| 1706 @item | |
| 1707 Emacs Info scans @code{Info-directory-list} from right-to-left while | |
| 1708 XEmacs Info reads it from left-to-right, so append to the @emph{correct} | |
| 1709 end of the list. | |
| 1710 | |
| 1711 @item | |
| 1712 Use @code{Info-default-directory-list} to initialize | |
| 1713 @code{Info-directory-list} @emph{if} it is available at startup, but not | |
| 1714 all Emacsen define it. | |
| 1715 | |
| 1716 @item | |
| 1717 Emacs Info looks for a standard @file{dir} file in each of the | |
| 1718 directories scanned from #1 and magically concatenates them together. | |
| 1719 | |
| 1720 @item | |
| 1721 XEmacs Info looks for a @file{localdir} file (which consists of just the | |
| 1722 menu entries from a @file{dir} file) in each of the directories scanned | |
| 1723 from #1 (except the first), does a simple concatenation of them, and | |
| 1724 magically attaches the resulting list to the end of the menu in the | |
| 1725 @file{dir} file in the first directory. | |
| 1726 @end enumerate | |
| 1727 | |
| 1728 Another alternative is to convert the documentation to HTML with | |
| 1729 texi2html and read it from a web browser like Lynx or W3. | |
| 1730 @end quotation | |
| 1731 | |
| 1732 @unnumberedsec 1.5: Contributing to XEmacs | |
| 1733 | |
| 1734 @node Q1.5.1, Q1.5.2, Q1.4.5, Introduction | |
| 1735 @unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ? | |
| 1736 | |
| 1737 The FAQ is actively maintained and modified regularly. All links should | |
| 1738 be up to date. Unfortunately, some of the information is out of date -- | |
| 1739 a situation which the FAQ maintainer is working on. All submissions are | |
| 1740 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ | |
| 1741 maintainers}. | |
| 1742 | |
| 1743 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line. | |
| 1744 If you think you have a better way of answering a question, or think a | |
| 1745 question should be included, we'd like to hear about it. Questions and | |
| 1746 answers included into the FAQ will be edited for spelling and grammar | |
| 1747 and will be attributed. Answers appearing without attribution are | |
| 1748 either from versions of the FAQ dated before May 1996 or are from | |
| 1749 previous FAQ maintainers. Answers quoted from Usenet news articles will | |
| 1750 always be attributed, regardless of the author. | |
| 1751 | |
| 1752 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction | |
| 1753 @unnumberedsubsec Q1.5.2: How do I become a beta tester? | |
| 1754 | |
| 1755 Send an email message to @email{xemacs-beta-request@@xemacs.org} with | |
| 1756 the line @samp{subscribe} in the body of the message. | |
| 1757 | |
| 1758 Be prepared to get your hands dirty, as beta testers are expected to | |
| 1759 identify problems as best they can. | |
| 1760 | |
| 2559 | 1761 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction |
| 2537 | 1762 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself? |
| 1763 | |
| 1764 It depends on the knowledge and time you possess. If you are able, by | |
| 1765 all means become a beta tester (@pxref{Q1.5.2}). If you are a | |
| 1766 programmer, try to build XEmacs and see if you can improve it. | |
| 1767 | |
| 1768 Otherwise, you can still help by using XEmacs as your everyday editor | |
| 1769 (for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you | |
| 1770 find to the mailing list. | |
| 1771 | |
| 1772 Another area where we need help is the documentation: We need good | |
| 1773 documentation for building XEmacs and for using it. This FAQ is a | |
| 1774 small step in that direction. | |
| 1775 | |
| 1776 Ben Wing @email{ben@@xemacs.org} writes: | |
| 1777 | |
| 1778 @quotation | |
| 1779 BTW if you have a wish list of things that you want added, you have to | |
| 1780 speak up about it! More specifically, you can do the following if you | |
| 1781 want a feature added (in increasing order of usefulness): | |
| 1782 | |
| 1783 @itemize @bullet | |
| 1784 @item | |
| 1785 Make a posting about a feature you want added. | |
| 1786 | |
| 1787 @item | |
| 1788 Become a beta tester and make more postings about those same features. | |
| 1789 | |
| 1790 @item | |
| 1791 Convince us that you're going to use the features in some cool and | |
| 1792 useful way. | |
| 1793 | |
| 1794 @item | |
| 1795 Come up with a clear and well-thought-out API concerning the features. | |
| 1796 | |
| 1797 @item | |
| 1798 Write the code to implement a feature and send us a patch. | |
| 1799 @end itemize | |
| 1800 | |
| 1801 (not that we're necessarily requiring you to write the code, but we can | |
| 1802 always hope :) | |
| 1803 @end quotation | |
| 1804 | |
| 2559 | 1805 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction |
| 1806 @unnumberedsubsec Q1.5.4: How do I get started developing XEmacs? | |
| 1807 | |
| 1808 First, get yourself set up under CVS so that you can access the CVS | |
| 1809 repositories containing the XEmacs sources and the XEmacs packages. | |
| 1810 | |
| 1811 Next, set up your layout. This is important, as a good layout will | |
| 1812 facilitate getting things done efficiently, while a bad layout will could | |
| 1813 lead to disaster, as you can't figure out which code is the most recent, | |
| 1814 which can be thrown away, etc. We suggest the following layout: (feel free | |
| 1815 to make changes) | |
| 1816 | |
| 1817 @itemize @bullet | |
| 1818 @item | |
| 1819 Everything goes under @file{/src/xemacs} (use a different directory if | |
| 1820 you want). From now, instead of saying @file{/src/xemacs}, we use | |
| 1821 @file{<xsrc-top>}, to make it easier in case someone picked a | |
| 1822 different directory. | |
| 1823 | |
| 1824 @item | |
| 1825 Package source is in @file{<xsrc-top>/package-src}. | |
| 1826 | |
| 1827 @item | |
| 1828 Installed packages go under @file{<xsrc-top>/xemacs-packages}, and | |
| 1829 @file{<xsrc-top>/mule-packages}. | |
| 1830 | |
| 1831 @item | |
| 1832 A "workspace" is a complete copy of the sources, in which you do work of | |
| 1833 a particular kind. Workspaces can be differentiated by which branch of | |
| 1834 the source tree they extend off of -- usually either the stable or | |
| 1835 experimental, unless other branches have been created (for example, Ben | |
| 1836 created a branch for his Mule work because (1) the project was long-term | |
| 1837 and involved an enormous number of changes, (2) people wanted to be able | |
| 1838 to look at what his work in progress, and (3) he wanted to be able to | |
| 1839 check things in and in general use source-code control, since it was a | |
| 1840 long-term project). Workspaces are also differentiated in what their | |
| 1841 purpose is -- general working workspace, workspace for particular | |
| 1842 projects, workspace keeping the latest copy of the code in one of the | |
| 1843 branches without mods, etc. | |
| 1844 | |
| 1845 @item | |
| 1846 Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.: | |
| 1847 | |
| 1848 @itemize @bullet | |
| 1849 @item | |
| 1850 @file{<xsrc-top>/working} (the workspace you're actively working on, | |
| 1851 periodically synched up with the latest trunk) | |
| 1852 | |
| 1853 @item | |
| 1854 @file{<xsrc-top>/stable} (for making changes to the stable version of | |
| 1855 XEmacs, which sits on a branch) | |
| 1856 | |
| 1857 @item | |
| 1858 @file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult | |
| 1859 task that's going to affect lots of source and take a long time, and | |
| 1860 so best done in its own workspace without the interference of other | |
| 1861 work you're doing. Also, you can commit just this one large change, | |
| 1862 separate from all the other changes). | |
| 1863 | |
| 1864 @item | |
| 1865 @file{<xsrc-top>/latest} (a copy of the latest sources on the trunk, | |
| 1866 i.e. the experimental version of XEmacs, with no patches in it; | |
| 1867 either update it periodically, by hand, or set up a cron job to do it | |
| 1868 automatically). Set it up so it can be built, and build it so you | |
| 1869 have a working XEmacs. (Building it might also go into the cron job.) | |
| 1870 | |
| 1871 This workspace serves a number of purposes: | |
| 1872 @enumerate | |
| 1873 @item | |
| 1874 You always have a recent version of XEmacs you can compare | |
| 1875 against when something you're working on breaks. It's true | |
| 1876 that you can do this with cvs diff, but when you need to do | |
| 1877 some serious investigation, this method just fails. | |
| 1878 @item | |
| 1879 You (almost) always have a working, up-to-date executable that | |
| 1880 can be used when your executable is crashing and you need to | |
| 1881 keep developing it, or when you need an `xemacs' to build | |
| 1882 packages, etc. | |
| 1883 @item | |
| 1884 When creating new workspaces, you can just copy the `latest' | |
| 1885 workspace using GNU @code{cp -a}. You have all the .elc's built, | |
| 1886 everything else probably configured, any spare files in place | |
| 1887 (e.g. some annoying xpm.dll under Windows, etc.). | |
| 1888 @end enumerate | |
| 1889 | |
| 1890 @item | |
| 1891 @file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but | |
| 1892 for the Stable branch of XEmacs, rather than the Experimental branch | |
| 1893 of XEmacs). This may or may not be necessary depending on how much | |
| 1894 development you do of the stable branch. | |
| 1895 @end itemize | |
| 1896 | |
| 1897 @item | |
| 1898 @file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs | |
| 1899 web site. | |
| 1900 | |
| 1901 @item | |
| 1902 @file{<xsrc-top>/in-patches} for patches received from email and saved | |
| 1903 to files. | |
| 1904 | |
| 1905 @item | |
| 1906 @file{<xsrc-top>/out-patches} for locally-generated patches to be sent | |
| 1907 to @email{xemacs-patches@@xemacs.org}. Less useful now that the | |
| 1908 patcher util has been developed. | |
| 1909 | |
| 1910 @item | |
| 1911 @file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with | |
| 1912 various configuration options turned off and on. The scripts in | |
| 1913 xemacs-builds/ben (see below) can be used to automate building XEmacs | |
| 1914 workspaces with many different configuration options and automatically | |
| 1915 filtering out the normal output so that you see only the abnormal | |
| 1916 output. | |
| 1917 | |
| 1918 @item | |
| 1919 @file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need | |
| 1920 to check out separately in CVS. This contains scripts used for building | |
| 1921 XEmacs, automating and simplifying using CVS, etc. Under various | |
| 1922 people's directories are their own build and other scripts. The | |
| 1923 currently most-maintained scripts are under ben/, where there are easily | |
| 1924 configurable scripts that can be used to easily build any workspace | |
| 1925 (esp. if you've more or less followed the layout presented above) | |
| 1926 unattended, with one or more configuration states (there's a | |
| 1927 pre-determined list of the most useful, but it's easy to change). The | |
| 1928 output is filtered and split up in various ways so that you can identify | |
| 1929 which output came from where, and you can see the output either full or | |
| 1930 with all "normal" output except occasional status messages filtered so | |
| 1931 that you only see the abnormal ones. | |
| 1932 @end itemize | |
| 1933 | |
| 1934 @node Q1.5.5, Q1.6.1, Q1.5.4, Introduction | |
| 1935 @unnumberedsubsec Q1.5.5: What's the basic layout of the code? | |
| 1936 | |
| 1937 The file @file{configure} is a shell script to acclimate XEmacs to the | |
| 1938 oddities of your processor and operating system. It will create a | |
| 1939 file named @file{Makefile} (a script for the @file{make} program), which helps | |
| 1940 automate the process of building and installing emacs. See INSTALL | |
| 1941 for more detailed information. | |
| 1942 | |
| 1943 The file @file{configure.in} is the input used by the autoconf program to | |
| 1944 construct the @file{configure} script. Since XEmacs has configuration | |
| 1945 requirements that autoconf can't meet, @file{configure.in} uses an unholy | |
| 1946 marriage of custom-baked configuration code and autoconf macros; it | |
| 1947 may be wise to avoid rebuilding @file{configure} from @file{configure.in} when | |
| 1948 possible. | |
| 1949 | |
| 1950 The file @file{Makefile.in} is a template used by @file{configure} to create | |
| 1951 @file{Makefile}. | |
| 1952 | |
| 1953 There are several subdirectories: | |
| 1954 | |
| 1955 @enumerate | |
| 1956 @item | |
| 1957 @file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its | |
| 1958 primitives, the redisplay code, and some basic editing functions). | |
| 1959 @item | |
| 1960 @file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else). | |
| 1961 @item | |
| 1962 @file{lib-src} holds the source code for some utility programs for use by | |
| 1963 or with XEmacs, like movemail and etags. | |
| 1964 @item | |
| 1965 @file{etc} holds miscellaneous architecture-independent data files | |
| 1966 XEmacs uses, like the tutorial text. The contents of the @file{lisp}, | |
| 1967 @file{info} and @file{man} subdirectories are architecture-independent too. | |
| 1968 @item | |
| 1969 @file{lwlib} holds the C code for the X toolkit objects used by XEmacs. | |
| 1970 @item | |
| 1971 @file{info} holds the Info documentation tree for XEmacs. | |
| 1972 @item | |
| 1973 @file{man} holds the source code for the XEmacs online documentation. | |
| 1974 @item | |
| 1975 @file{nt} holds files used compiling XEmacs under Microsoft Windows. | |
| 1976 @end enumerate | |
| 1977 | |
| 2537 | 1978 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs) |
| 1979 | |
| 2559 | 1980 @node Q1.6.1, Q1.6.2, Q1.5.5, Introduction |
| 2537 | 1981 @unnumberedsubsec Q1.6.1: What is GNU Emacs? |
| 1982 | |
| 1983 GNU Emacs and XEmacs are related open-source text editors. Both | |
| 1984 derive from GNU Emacs version 18; the split between the two happened | |
| 1985 in 1991 (for comparison, the oldest versions of GNU Emacs date from | |
| 1986 1984). For information on GNU Emacs, see | |
| 1987 @uref{http://www.gnu.org/software/emacs/emacs.html}. | |
| 1988 | |
| 1989 @node Q1.6.2, Q1.6.3, Q1.6.1, Introduction | |
| 1990 @unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs? | |
| 428 | 1991 |
| 1992 For a detailed description of the differences between GNU Emacs and | |
| 1993 XEmacs and a detailed history of XEmacs, check out the | |
| 1994 @example | |
| 430 | 1995 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file} |
| 428 | 1996 @end example |
| 1997 | |
| 2417 | 1998 @table @strong |
| 1999 @item User-Visible Editing Features | |
| 2000 XEmacs in general tries hard to conform to exist user-interface | |
| 2001 standards, and to work "out-of-the-box" without the need for obscure | |
| 2002 customization changes. GNU Emacs, particularly version 21, has gotten | |
| 2003 better about this (in many cases by copying the XEmacs behavior!), but | |
| 2004 still has some weirdnesses. For example, the standard method of | |
| 2005 selecting text using the Shift key works out-of-the-box in XEmacs. | |
| 2006 | |
| 2007 XEmacs has a built-in toolbar. Four toolbars can actually be configured | |
| 2008 simultaneously: top, bottom, left, and right toolbars. | |
| 2009 | |
| 2010 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19 | |
| 2011 (which provides a primitive form of vertical scrollbar), these are true | |
| 2012 toolkit scrollbars. A look-alike Motif scrollbar is provided for those | |
| 2013 who don't have Motif. (Even for those who do, the look-alike may be | |
| 2014 preferable as it is faster.) | |
| 2015 | |
| 2016 XEmacs has buffer tabs along the top of the frame (although the | |
| 2017 position can be changed) that make it very easy to switch buffers. | |
| 2018 | |
| 2019 The menubar under XEmacs is better-designed, with more thought put into | |
| 2020 it. | |
| 2021 | |
| 2022 XEmacs can ask questions using popup dialog boxes. Any command executed | |
| 2023 from a menu will ask yes/no questions with dialog boxes, while commands | |
| 2024 executed via the keyboard will use the minibuffer. | |
| 2025 | |
| 2026 XEmacs under MS Windows provides uses the standard file-dialog box for | |
| 2027 opening and saving files. Standard menu-accelerator behavior can easily | |
| 2028 be enabled using the Options menu, and integrates well into the existing | |
| 2029 keymap. | |
| 2030 | |
| 2031 XEmacs has (still experimental) support for widgets of various sorts -- | |
| 2032 buttons, text boxes, sliders, progress bars, etc. A progress bar is | |
| 2033 used in font lock to show the progress. | |
| 2034 | |
| 2035 Experimental support for drag-and-drop protocols is provided from | |
| 2036 XEmacs 21. | |
| 2037 | |
| 2038 @item General Platform Support | |
| 2039 If you're running on a machine with audio hardware, you can specify | |
| 2040 sound files for XEmacs to play instead of the default X beep. See the | |
| 2041 documentation of the function load-sound-file and the variable | |
| 2042 sound-alist. XEmacs also supports the network sound protocols NAS and | |
| 2043 EsounD. | |
| 2044 | |
| 2045 XEmacs 21 supports database protocols with LISP bindings, currently | |
| 2046 including Berkeley DB, LDAP, and PostgreSQL (21.2 only). | |
| 2047 | |
| 2048 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method | |
| 2049 servers directly, as well as through the X Input Method (XIM) | |
| 2050 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen | |
| 2051 support the Quail family of input methods (implemented in LISP) for many | |
| 2052 languages. | |
| 2053 | |
| 2054 XEmacs provides support for ToolTalk on systems that have | |
| 2055 it. | |
| 2056 | |
| 2057 @item Packaged LISP Libraries | |
| 2058 Many more packages are provided standard with XEmacs than with GNU Emacs | |
| 2059 19 or 20. | |
| 2060 | |
| 2061 XEmacs 21 supports an integrated package management system which uses | |
| 2062 EFS to download, then automatically install prebuilt LISP | |
| 2063 libraries. This allows XEmacs users much more straightforward access to | |
| 2064 the "latest and greatest" version of any given library. | |
| 2065 | |
| 2066 We are working on a standard method for enabling, disabling and | |
| 2067 otherwise controlling packages, which should make them very easy to use. | |
| 2068 | |
| 2069 @item LISP Programming | |
| 2070 From XEmacs 20 on, characters are a separate type. Characters can be | |
| 2071 converted to integers (and many integers can be converted to | |
| 2072 characters), but characters are not integers. GNU Emacs 19, XEmacs 19, | |
| 2073 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs | |
| 2074 20 (incorporating Mule 3 and later Mule 4) represent them as integers. | |
| 2075 | |
| 2076 From XEmacs 20 on, the buffer is treated as an array of characters, and | |
| 2077 the representation of buffer text is not exposed to LISP. The GNU Emacs | |
| 2078 20 functions like buffer-as-multibyte are not supported. | |
| 2079 | |
| 2080 In XEmacs, events are first-class objects. GNU Emacs 19 represents them | |
| 2081 as integers, which obscures the differences between a key gesture and | |
| 2082 the ancient ASCII code used to represent a particular overlapping subset | |
| 2083 of them. | |
| 2084 | |
| 2085 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19 | |
| 2086 represents them as complicated combinations of association lists and | |
| 2087 vectors. If you use the advertised functional interface to manipulation | |
| 2088 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU | |
| 2089 Emacs 19; if your code depends on the underlying implementation of | |
| 2090 keymaps, it will not. | |
| 2091 | |
| 2092 XEmacs uses "extents" to represent all non-textual aspects of buffers; | |
| 2093 GNU Emacs 19 uses two distinct objects, "text properties" and | |
| 2094 "overlays", which divide up the functionality between them. Extents are | |
| 2095 a superset of the union of the functionality of the two GNU Emacs data | |
| 2096 types. The full GNU Emacs 19 interface to text properties and overlays | |
| 2097 is supported in XEmacs (with extents being the underlying | |
| 2098 representation). | |
| 2099 | |
| 2100 Extents can be made to be copied into strings, and then restored, by | |
| 2101 kill and yank. Thus, one can specify this behavior on either "extents" | |
| 2102 or "text properties", whereas in GNU Emacs 19 text properties always | |
| 2103 have this behavior and overlays never do. | |
| 2104 | |
| 2105 @item Window System Programming Interface | |
| 2106 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes | |
| 2107 it be a more well-behaved X citizen (and also improves portability). A | |
| 2108 result of this is that it is possible to include other Xt "Widgets" in | |
| 2109 the XEmacs window. Also, XEmacs understands the standard Xt command-line | |
| 2110 arguments. | |
| 2111 | |
| 2112 XEmacs supports Motif applications, generic Xt (e.g. Athena) | |
| 2113 applications, and raw Xlib applications. An XEmacs variant which | |
| 2114 supports GTK+ is available (integration as an option in the XEmacs | |
| 2115 mainline is planned for XEmacs 22), although code to take advantage of | |
| 2116 the support is as yet scarce. | |
| 2117 | |
| 2118 An XEmacs frame can be placed within an "external client widget" managed | |
| 2119 by another application. This allows an application to use an XEmacs | |
| 2120 frame as its text pane rather than the standard Text widget that is | |
| 2121 provided with Motif or Athena. | |
| 2122 | |
| 2123 @item Community Participation | |
| 2459 | 2124 Joining the XEmacs development team is simple. Mail to |
| 2125 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If | |
| 2126 you want to be, of course. You're also welcome to just post | |
| 2127 development-related questions and bug reports.) The GNU Emacs | |
| 2417 | 2128 development team and internal mailing lists are still by invitation |
| 2129 only. | |
| 2130 | |
| 2131 The "bleeding edge" of mainline XEmacs development is available by | |
| 2132 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk | |
| 2133 module for the latest in GUI features!) | |
| 2134 | |
| 2135 Development and maintenance of Lisp libraries is separated from the core | |
| 2136 editor development at a fairly low level. This provides better | |
| 2137 modularization and a better division of responsibility between external | |
| 2138 library maintainers and the XEmacs core development team. Even for | |
| 2139 packages the size of Gnus, XEmacs users normally have access to a | |
| 2140 pre-built version within a few weeks of a major release, and minor | |
| 2141 updates often within days. | |
| 2142 | |
| 2143 CVS commit authority is broadly dispersed. Recognized maintainers of | |
| 2144 LISP libraries who are willing to maintain XEmacs packaged versions | |
| 2145 automatically qualify for CVS accounts for their packages. | |
| 2146 @end table | |
| 2147 | |
| 2537 | 2148 @node Q1.6.3, Q1.6.4, Q1.6.2, Introduction |
| 2149 @unnumberedsubsec Q1.6.3: How much does XEmacs differ? | |
| 2417 | 2150 |
| 2151 RMS has asserted at times that XEmacs is merely a "patch" on top of | |
| 2537 | 2152 GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the |
| 2417 | 2153 code, if that, remains unchanged, and nearly 14 years of work has gone |
| 2154 into XEmacs at this point. (GNU Emacs itself is only than 20 years | |
| 2155 old, and thus XEmacs has existed as a separate product for over 2/3 of | |
| 2156 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has | |
| 2157 perhaps 65,000 more lines of C code than GNU Emacs 21.2. | |
| 2158 | |
| 2159 However, the XEmacs developers strive to keep their code compatible with | |
| 2160 GNU Emacs, especially on the Lisp level. Much effort goes into | |
| 2161 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to | |
| 2162 benefit from GNU Emacs development work. (In contrast, almost no code | |
| 2163 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs | |
| 2164 developers are instructed by RMS not to even look at XEmacs source code! | |
| 2165 This stems from self-imposed licensing restrictions on the part of GNU | |
| 2166 Emacs -- and almost certainly out of hostility, as well.) | |
| 2167 | |
| 2537 | 2168 @node Q1.6.4, Q1.6.5, Q1.6.3, Introduction |
| 2169 @unnumberedsubsec Q1.6.4: Is XEmacs "GNU"? | |
| 2417 | 2170 |
| 2171 RMS insists on the term "GNU XEmacs" and maintains that | |
| 2172 | |
| 2173 @quotation | |
| 2174 XEmacs is GNU software because it's a modified version of a | |
| 2175 GNU program. And it is GNU software because the FSF is the copyright | |
| 2176 holder for most of it, and therefore the legal responsibility for | |
| 2177 protecting its free status falls on us whether we want it or not. This | |
| 2178 is why the term "GNU XEmacs" is legitimate. | |
| 2179 @end quotation | |
| 2180 | |
| 2181 In fact, FSF is @emph{not} the copyright holder for most of the code, | |
| 2537 | 2182 as very little unmodified FSF code remains (@pxref{Q1.6.3}). |
| 2417 | 2183 |
| 2184 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre | |
| 2185 to the XEmacs developers given RMS's hostility and general lack of | |
| 2186 interest in cooperation. "GNU" software in general is part of the GNU | |
| 2187 Project, is distributed by it on their FTP site, and receives support | |
| 2188 (or at least cooperation), as well as implicit endorsement, from it. | |
| 2189 The GNU Project, however, has never supported XEmacs and never | |
| 2190 distributed XEmacs, and RMS's hostility is the farthest thing possible | |
| 2191 from an endorsement. In fact, the GNU Project distributes a number of | |
| 2192 non-GNU software projects on the FSF web site, but again XEmacs is not | |
| 2193 one of them. | |
| 2194 | |
| 2537 | 2195 @node Q1.6.5, Q1.6.6, Q1.6.4, Introduction |
| 2196 @unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 2417 | 2197 |
| 2198 Unfortunately even the naming of these two applications has become | |
| 2199 politicized. Much of this stems from RMS, who has a history of | |
| 2200 politicizing similar issues. (Compare the controversy over "Lignux" | |
| 2201 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU | |
| 2202 Emacs" be used, which are neutral and acceptable to most people. RMS, | |
| 2203 however, is not willing to accept these terms. He insists that, if | |
| 2204 his product is called "GNU Emacs", then ours must be called "GNU | |
| 2537 | 2205 XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other |
| 2417 | 2206 hand, if our product is to be called "XEmacs", as we prefer, then his |
| 2207 product must simply be called "Emacs". The intent of this seems | |
| 2208 clear: RMS wants to make sure the names reflect his view that his | |
| 2209 version is the "real" Emacs and ours is merely a derivative, | |
| 2537 | 2210 second-class product (@pxref{Q1.6.3}). |
| 2417 | 2211 |
| 2212 The XEmacs developers hope that you will use the neutral terms | |
| 2213 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on | |
| 2214 the other hand, is a generic term for a class of programmable text | |
| 2215 editors with a similar look-and-feel, and usually a Lisp-based | |
| 2216 extension language. These trace themselves back to early editors such | |
| 2217 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,, | |
| 2218 internals, XEmacs Internals Manual}. | |
| 2219 | |
| 2220 We also call upon RMS, in the spirit of furthering cooperation, to | |
| 2221 stop politicizing this issue and use the neutral terms "XEmacs" and | |
| 2222 "GNU Emacs". We have already acceded to RMS' wishes in this respect, | |
| 2223 and we expect him to do the same. (In the past, the XEmacs developers | |
| 2224 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in | |
| 2225 reference to GNU Emacs; these terms were apparently modeled after RMS' | |
| 2226 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress | |
| 2227 Emacs, produced by James Gosling. RMS, however, considers such terms | |
| 2228 to be insulting, so we refrain from using them as much as possible in | |
| 2229 preference to GNU Emacs.) | |
| 2230 | |
| 2537 | 2231 @node Q1.6.6, Q1.7.1, Q1.6.5, Introduction |
| 2232 @unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged? | |
| 2417 | 2233 |
| 2234 There are currently irreconcilable differences in the views about | |
| 2235 technical, programming, design, organizational and legal matters | |
| 2236 between Richard Stallman (RMS), the author and leader of the GNU Emacs | |
| 2237 project, and the XEmacs development team which provide little hope for | |
| 2238 a merge to take place in the short-term future. There have been | |
| 2239 repeated attempts at merging by all of the major XEmacs developers, | |
| 2240 starting from the early days of Lucid Emacs (in 1991), but they have | |
| 2241 all failed. RMS has very strong views about how GNU Emacs should be | |
| 2242 structured and how his project should be run, and during the repeated | |
| 2243 merge efforts has never demonstrated any realistic interest in | |
| 2244 sufficiently compromising or ceding control to allow a middle ground | |
| 2245 to be found. The basic problem seems to be the very different goals | |
| 2246 of RMS and the XEmacs project. The primary goals of the XEmacs | |
| 2247 project are technical and organizational -- we want to create the best | |
| 2248 editor possible, and to make it as easy as possible for people around | |
| 2249 the world to contribute. The primary goals of RMS, on the other hand, | |
| 2250 are political, and GNU Emacs, and any potential merge efforts with | |
| 2251 XEmacs, are strictly subservient to these goals. In fact, in many | |
| 2252 ways RMS sees GNU Emacs as the "poster child" of his aims, the one | |
| 2253 program in the GNU project that above all others must set an example | |
| 2254 to the world. (This has to do with the fact that GNU Emacs was the | |
| 2255 first program in the GNU project, and the only one that he is still | |
| 2256 personally involved with on a day-to-day basis.) Given his goals, his | |
| 2257 position is completely reasonable -- but unfortunately, makes any | |
| 2258 merge impossible. | |
| 2259 | |
| 2260 From the XEmacs perspective, the most intractable issues appear to be | |
| 2261 legal and organizational, specifically: | |
| 428 | 2262 |
| 2263 @itemize @bullet | |
| 2264 @item | |
| 2417 | 2265 RMS requires "legal papers" to be signed for all contributions of code |
| 2266 to GNU Emacs over 10 lines or so, transferring the copyright and all | |
| 2267 legal rights to the code to the Free Software Foundation. XEmacs does | |
| 2268 not and has never required this, since it has the practical effect of | |
| 2269 discouraging individual and in particular corporate contributions -- | |
| 2270 corporations will almost never sign away their legal rights to code | |
| 2271 since it makes it impossible to reuse the code in any product that | |
| 2272 whose license is not compatible with the GNU General Public License. | |
| 2273 Since RMS has shown no inclination to compromise on this issue, a | |
| 2274 merge would require that most of the existing XEmacs code would need | |
| 2275 to be thrown away and rewritten -- something the XEmacs developers are | |
| 2276 understandably reluctant to do. | |
| 2277 | |
| 2278 @item | |
| 2279 A repeated stumbling block in the merge talks has been the issue of | |
| 2280 organizational control over the resulting product. RMS has made it | |
| 2281 clear that he intends to have final say over design issues in a merged | |
| 2282 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly | |
| 2283 clashed over design decisions, and RMS' insistence on getting his way | |
| 2284 in such disagreements was the very reason for the split in the first | |
| 2285 place. This same issue has come up again and again in merge talks and | |
| 2286 we have never been able to come to a satisfactory resolution. To the | |
| 2287 extent that RMS is willing to compromise at all, it appears to be of a | |
| 2288 purely political rather than technical nature -- "If we support this | |
| 2289 feature of yours, we also get to support this other feature of mine." | |
| 2290 The XEmacs developers cannot see how such a process would lead to | |
| 2291 anything but a mess of incompatible things hodgepodged together. | |
| 2292 | |
| 2293 @item | |
| 2294 Because of the years of separate development, distinct and | |
| 2295 incompatible interfaces have developed and merging would be extremely | |
| 2296 difficult even with the above non-technical issues resolved. The | |
| 2297 problem has been exacerbated by the issue of legal papers -- because | |
| 2298 XEmacs code is not "kosher" from RMS' perspective, he discourages | |
| 2299 developers from even looking at it out of legal concerns. Although it | |
| 2300 is still possible to read the XEmacs documentation and run the | |
| 2301 program, the practical effect of this prohibition has been to strongly | |
| 2302 discourage code-sharing and cooperative development -- although a | |
| 2303 great deal of GNU Emacs code has been incorporated into XEmacs, | |
| 2304 practically none has gone the other direction. | |
| 428 | 2305 @end itemize |
| 2306 | |
| 2307 If you have a comment to add regarding the merge, it is a good idea to | |
| 2417 | 2308 avoid posting to the newsgroups, because of the very heated flamewars |
| 2309 that often result. Mail your questions to | |
| 2310 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}. | |
| 2311 | |
| 2537 | 2312 @unnumberedsec 1.7: External Packages |
| 2313 | |
| 2559 | 2314 @node Q1.7.1, Q1.7.2, Q1.6.6, Introduction |
| 2315 @unnumberedsubsec Q1.7.1: What is the package system? | |
| 2316 | |
| 2317 In order to reduce the size and increase the maintainability of | |
| 2318 XEmacs, the majority of the Elisp packages that came with previous | |
| 2319 releases have been unbundled. They have been replaced by the package | |
| 2320 system. Each elisp add-on (or groups of them when they are small) now | |
| 2321 comes in its own tarball that contains a small search hierarchy. | |
| 2322 | |
| 2323 You select just the ones you need. Install them by untarring them into | |
| 2324 the right place. On startup XEmacs will find them, set up the load | |
| 2325 path correctly, install autoloads, etc, etc. | |
| 2326 | |
| 2327 @xref{Q2.1.1}, for more info on how to download and install the packages. | |
| 2328 | |
| 2329 @node Q1.7.2, Q1.7.3, Q1.7.1, Introduction | |
| 2330 @unnumberedsubsec Q1.7.2: Which external packages are there? | |
| 2537 | 2331 |
| 2332 @subheading Normal Packages | |
| 2333 | |
| 2334 A very broad collection of elisp packages. | |
| 2417 | 2335 |
| 2336 @table @asis | |
| 2537 | 2337 @item Sun |
| 2338 Support for Sparcworks. | |
| 2339 | |
| 2340 @item ada | |
| 2341 Ada language support. | |
| 2342 | |
| 2343 @item apel | |
| 2344 A Portable Emacs Library. Used by XEmacs MIME support. | |
| 2345 | |
| 2346 @item auctex | |
| 2347 Basic TeX/LaTeX support. | |
| 2348 | |
| 2349 @item bbdb | |
| 2350 The Big Brother Data Base: a rolodex-like database program. | |
| 2351 | |
| 2352 @item build | |
| 2353 Build XEmacs from within (UNIX, Windows). | |
| 2354 | |
| 2355 @item c-support | |
| 2356 Basic single-file add-ons for editing C code. | |
| 2357 | |
| 2358 @item calc | |
| 2359 Emacs calculator. | |
| 2360 | |
| 2361 @item calendar | |
| 2362 Calendar and diary support. | |
| 2363 | |
| 2364 @item cc-mode | |
| 2365 C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support. | |
| 2366 | |
| 2367 @item clearcase | |
| 2368 New Clearcase Version Control for XEmacs (UNIX, Windows). | |
| 2369 | |
| 2370 @item clearcase | |
| 2371 Support for the Clearcase version control system. | |
| 2372 | |
| 2373 @item cookie | |
| 2374 "Fortune cookie"-style messages. Includes Spook (suspicious phrases) | |
| 2375 and Yow (Zippy quotes). | |
| 2376 | |
| 2377 @item crisp | |
| 2378 Crisp/Brief emulation. | |
| 2379 | |
| 2380 @item debug | |
| 2381 GUD, gdb, dbx debugging support. | |
| 2382 | |
| 2383 @item dictionary | |
| 2384 Interface to RFC2229 dictionary servers. | |
| 2385 | |
| 2386 @item dired | |
| 2387 The DIRectory EDitor is for manipulating, and running commands on | |
| 2388 files in a directory. | |
| 2389 | |
| 2390 @item docbookide | |
| 2391 DocBook editing support. | |
| 2392 | |
| 2393 @item ecb | |
| 2394 Emacs source code browser. | |
| 2395 | |
| 2396 @item ecrypto | |
| 2397 Crypto functionality in Emacs Lisp. | |
| 2398 | |
| 2399 @item edebug | |
| 2400 An Emacs Lisp debugger. | |
| 2401 | |
| 2402 @item ediff | |
| 2403 Interface over GNU patch. | |
| 2404 | |
| 2405 @item edit-utils | |
| 2406 Miscellaneous editor extensions, you probably need this. | |
| 2407 | |
| 2408 @item edt | |
| 2409 DEC EDIT/EDT emulation. | |
| 2410 | |
| 2411 @item efs | |
| 2412 Treat files on remote systems the same as local files. | |
| 2413 | |
| 2414 @item eieio | |
| 2415 Enhanced Implementation of Emacs Interpreted Objects. | |
| 2416 | |
| 2417 @item elib | |
| 2418 Portable Emacs Lisp utilities library. | |
| 2419 | |
| 2420 @item emerge | |
| 2421 Another interface over GNU patch. | |
| 2422 | |
| 2423 @item erc | |
| 2424 ERC is an Emacs InternetRelayChat client. | |
| 2425 | |
| 2426 @item escreen | |
| 2427 Multiple editing sessions withing a single frame (like screen). | |
| 2428 | |
| 2429 @item eshell | |
| 2430 Command shell implemented entirely in Emacs Lisp. | |
| 2431 | |
| 2432 @item ess | |
| 2433 ESS: Emacs Speaks Statistics. | |
| 2434 | |
| 2435 @item eterm | |
| 2436 Terminal emulation. | |
| 2437 | |
| 2438 @item eudc | |
| 2439 Emacs Unified Directory Client (LDAP, PH). | |
| 2440 | |
| 2441 @item footnote | |
| 2442 Footnoting in mail message editing modes. | |
| 2443 | |
| 2444 @item forms | |
| 2445 Forms editing support (obsolete, use Widget instead). | |
| 2446 | |
| 2447 @item fortran-modes | |
| 2448 Fortran support. | |
| 2449 | |
| 2450 @item fortran-modes | |
| 2451 Fortran language support. | |
| 2452 | |
| 2453 @item frame-icon | |
| 2454 Set up mode-specific icons for each frame under XEmacs. | |
| 2455 | |
| 2456 @item fsf-compat | |
| 2457 GNU Emacs compatibility files. | |
| 2458 | |
| 2459 @item games | |
| 2460 Tetris, Sokoban, and Snake. | |
| 2461 | |
| 2462 @item general-docs | |
| 2463 General documentation. Presently, empty. | |
| 2464 | |
| 2465 @item gnats | |
| 2466 XEmacs bug reports. | |
| 2467 | |
| 2468 @item gnus | |
| 2469 The Gnus Newsreader and Mailreader. | |
| 2470 | |
| 2471 @item haskell-mode | |
| 2472 Haskell editing support. | |
| 2473 | |
| 2474 @item hm--html-menus | |
| 2475 HTML editing. | |
| 2476 | |
| 2477 @item hyperbole | |
| 2478 Hyperbole: The Everyday Info Manager. | |
| 2479 | |
| 2480 @item ibuffer | |
| 2481 Advanced replacement for buffer-menu. | |
| 2482 | |
| 2483 @item idlwave | |
| 2484 Editing and Shell mode for the Interactive Data Language. | |
| 2485 | |
| 2486 @item igrep | |
| 2487 Enhanced front-end for Grep. | |
| 2488 | |
| 2489 @item ilisp | |
| 2490 Front-end for interacting with Inferior Lisp (external lisps). | |
| 2491 | |
| 2492 @item ispell | |
| 2493 Spell-checking with GNU ispell. | |
| 2494 | |
| 2495 @item jde | |
| 2496 Integrated Development Environment for Java. | |
| 2497 | |
| 2498 @item liece | |
| 2499 IRC (Internet Relay Chat) client for Emacs. Note, this package is | |
| 2500 deprecated and will be removed, use riece instead. | |
| 2501 | |
| 2502 @item mail-lib | |
| 2503 Fundamental lisp files for providing email support. | |
| 2504 | |
| 2505 @item mailcrypt | |
| 2506 Support for messaging encryption with PGP. | |
| 2507 | |
| 2508 @item mew | |
| 2509 Messaging in an Emacs World; a MIME-based email program. | |
| 2510 | |
| 2511 @item mh-e | |
| 2512 The XEmacs Interface to the MH Mail System. | |
| 2513 | |
| 2514 @item mine | |
| 2515 Elisp implementation of the game 'Minehunt'. | |
| 2516 | |
| 2517 @item misc-games | |
| 2518 Other amusements and diversions. | |
| 2519 | |
| 2520 @item mmm-mode | |
| 2521 Support for Multiple Major Modes within a single buffer. | |
| 2522 | |
| 2523 @item net-utils | |
| 2524 Miscellaneous Networking Utilities. | |
| 2525 | |
| 2526 @item ocaml | |
| 2527 Objective Caml editing support. | |
| 2528 | |
| 2529 @item oo-browser | |
| 2530 OO-Browser: The Multi-Language Object-Oriented Code Browser. | |
| 2531 | |
| 2532 @item ocaml | |
| 2533 Objective Caml editing support. | |
| 2534 | |
| 2535 @item os-utils | |
| 2536 Miscellaneous single-file O/S utilities, for printing, archiving, | |
| 2537 compression, remote shells, etc. | |
| 2538 | |
| 2539 @item pc | |
| 2540 PC style interface emulation. | |
| 2541 | |
| 2542 @item pcl-cvs | |
| 2543 CVS frontend. | |
| 2544 | |
| 2545 @item pcomplete | |
| 2546 Provides programmatic completion. | |
| 2547 | |
| 2548 @item perl-modes | |
| 2549 Perl support. | |
| 2550 | |
| 2551 @item pgg | |
| 2552 Emacs interface to various PGP implementations. | |
| 2553 | |
| 2554 @item prog-modes | |
| 2555 Support for various programming languages. | |
| 2556 | |
| 2557 @item ps-print | |
| 2558 Printing functions and utilities. | |
| 2559 | |
| 2560 @item psgml | |
| 2561 Validated HTML/SGML editing. | |
| 2562 | |
| 2563 @item psgml-dtds | |
| 2564 A collection of DTDs for psgml. Note that this package is deprecated | |
| 2565 and will be removed in the future, most likely Q2/2003. Instead of using | |
| 2566 this, you should install needed DTDs yourself. | |
| 2567 | |
| 2568 @item python-modes | |
| 2569 Python language support. | |
| 2570 | |
| 2571 @item reftex | |
| 2572 Emacs support for LaTeX cross-references, citations. | |
| 2573 | |
| 2574 @item riece | |
| 2575 IRC (Internet Relay Chat) client for Emacs. | |
| 2576 | |
| 2577 @item rmail | |
| 2578 An obsolete Emacs mailer. If you do not already use it don't start. | |
| 2579 | |
| 2580 @item ruby-modes | |
| 2581 Ruby support. | |
| 2582 | |
| 2583 @item sasl | |
| 2584 Simple Authentication and Security Layer (SASL) library. | |
| 2585 | |
| 2586 @item scheme | |
| 2587 Front-end support for Inferior Scheme. | |
| 2588 | |
| 2589 @item semantic | |
| 2590 Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator. | |
| 2591 | |
| 2592 @item sgml | |
| 2593 SGML/Linuxdoc-SGML editing. | |
| 2594 | |
| 2595 @item sh-script | |
| 2596 Support for editing shell scripts. | |
| 2597 | |
| 2598 @item sieve | |
| 2599 Manage Sieve email filtering scripts. | |
| 2600 | |
| 2601 @item slider | |
| 2602 User interface tool. | |
| 2603 | |
| 2604 @item sml-mode | |
| 2605 SML editing support. | |
| 2606 | |
| 2607 @item sounds-au | |
| 2608 XEmacs Sun sound files. | |
| 2609 | |
| 2610 @item sounds-wav | |
| 2611 XEmacs Microsoft sound files. | |
| 2612 | |
| 2613 @item speedbar | |
| 2614 Provides a separate frame with convenient references. | |
| 2615 | |
| 2616 @item strokes | |
| 2617 Mouse enhancement utility. | |
| 2618 | |
| 2619 @item supercite | |
| 2620 An Emacs citation tool for News & Mail messages. | |
| 2621 | |
| 2622 @item texinfo | |
| 2623 XEmacs TeXinfo support. | |
| 2624 | |
| 2625 @item text-modes | |
| 2626 Miscellaneous support for editing text files. | |
| 2627 | |
| 2628 @item textools | |
| 2629 Miscellaneous TeX support. | |
| 2630 | |
| 2631 @item time | |
| 2632 Display time & date on the modeline. | |
| 2633 | |
| 2634 @item tm | |
| 2635 Emacs MIME support. Not needed for gnus >= 5.8.0. | |
| 2636 | |
| 2637 @item tooltalk | |
| 2638 Support for building with Tooltalk. | |
| 2639 | |
| 2640 @item tpu | |
| 2641 DEC EDIT/TPU support. | |
| 2642 | |
| 2643 @item tramp | |
| 2644 Remote shell-based file editing. This is similar to EFS or Ange-FTP, | |
| 2645 but works with rsh/ssh and rcp/scp. | |
| 2646 | |
| 2647 @item vc | |
| 2648 Version Control for Free systems. | |
| 2649 | |
| 2650 @item vc-cc | |
| 2651 Version Control for ClearCase (UnFree) systems. | |
| 2652 | |
| 2653 @item vhdl | |
| 2654 Support for VHDL. | |
| 2655 | |
| 2656 @item view-process | |
| 2657 A Unix process browsing tool. | |
| 2658 | |
| 2659 @item viper | |
| 2660 VI emulation support. | |
| 2661 | |
| 2662 @item vm | |
| 2663 An Emacs mailer. | |
| 2664 | |
| 2665 @item w3 | |
| 2666 A Web browser. | |
| 2667 | |
| 2668 @item x-symbol | |
| 2669 Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts. | |
| 2670 | |
| 2671 @item xemacs-base | |
| 2672 Fundamental XEmacs support, you almost certainly need this. | |
| 2673 | |
| 2674 @item xemacs-devel | |
| 2675 XEmacs Lisp developer support. This package contains utilities for | |
| 2676 supporting Lisp development. It is a single-file package so it may be | |
| 2677 tailored. | |
| 2678 | |
| 2679 @item xlib | |
| 2680 Emacs interface to X server. | |
| 2681 | |
| 2682 @item xslide | |
| 2683 XSL editing support. | |
| 2684 | |
| 2685 @item xslt-process | |
| 2686 A minor mode for (X)Emacs which allows running an XSLT processor on a | |
| 2687 buffer. | |
| 2688 | |
| 2689 @item xwem | |
| 2690 X Emacs Window Manager. | |
| 2691 | |
| 2692 @item zenirc | |
| 2693 ZENIRC IRC Client. | |
| 2417 | 2694 @end table |
| 2695 | |
| 2537 | 2696 @subheading Mule Support (mule) |
| 2697 | |
| 2698 MULti-lingual Enhancement. Support for world scripts such as | |
| 2699 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc. | |
| 2700 To use these packages your XEmacs must be compiled with Mule | |
| 2701 support. | |
| 2702 | |
| 2703 @table @asis | |
| 2704 @item edict | |
| 2705 MULE: Lisp Interface to EDICT, Kanji Dictionary. | |
| 2706 | |
| 2707 @item egg-its | |
| 2708 MULE: Wnn (4.2 and 6) support. SJ3 support. | |
| 2709 | |
| 2710 @item latin-unity | |
| 2711 MULE: find single ISO 8859 character set to encode a buffer. | |
| 2712 | |
| 2713 @item latin-unity | |
| 2714 Unify character sets in a buffer. When characters belong to disjoint | |
| 2715 character sets, this attempts to translate the characters so | |
| 2716 that they belong to one character set. If the buffer coding system is | |
| 2717 not sufficient, this suggests different coding systems. | |
| 2718 | |
| 2719 @item leim | |
| 2720 MULE: Quail. All non-English and non-Japanese language support. | |
| 2721 | |
| 2722 @item locale | |
| 2723 MULE: Localized menubars and localized splash screens. | |
| 2724 | |
| 2725 @item lookup | |
| 2726 Dictionary support. (This isn't an English dictionary program) | |
| 2727 | |
| 2728 @item mule-base | |
| 2729 MULE: Basic Mule support, required for building with Mule. | |
| 2730 | |
| 2731 @item mule-ucs | |
| 2732 MULE: Extended coding systems (including Unicode) for XEmacs. | |
| 2733 | |
| 2734 @item mule-ucs | |
| 2735 Extended coding systems (including Unicode) for XEmacs. | |
| 2736 | |
| 2737 @item skk | |
| 2738 Another Japanese Language Input Method. Can be used without a | |
| 2739 separate process running as a dictionary server. | |
| 2740 @end table | |
| 2741 | |
| 2559 | 2742 @node Q1.7.3, Q1.7.4, Q1.7.2, Introduction |
| 2743 @unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs? | |
| 2744 | |
| 2745 Strictly speaking, no. XEmacs will build and install just fine without | |
| 2746 any packages installed. However, only the most basic editing functions | |
| 2747 will be available with no packages installed, so installing packages is | |
| 2748 an essential part of making your installed XEmacs _useful_. | |
| 2749 | |
| 2750 @node Q1.7.4, Q1.8.1, Q1.7.3, Introduction | |
| 2751 @unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality? | |
| 2752 | |
| 2753 If you want to find out which package contains the functionality you | |
| 2754 are looking for, use @kbd{M-x package-get-package-provider}, and give it a | |
| 2755 symbol that is likely to be in that package. | |
| 2756 | |
| 2757 For example, if some code you want to use has a @code{(require 'thingatpt)} | |
| 2758 in it: | |
| 2759 | |
| 2760 @example | |
| 2761 M-x package-get-package-provider RET thingatpt RET | |
| 2762 @end example | |
| 2763 | |
| 2764 which will return something like: @samp{(fsf-compat "1.08").} | |
| 2765 | |
| 2537 | 2766 @unnumberedsec 1.8: Internationalization |
| 2767 | |
| 2559 | 2768 @node Q1.8.1, Q1.8.2, Q1.7.4, Introduction |
| 2537 | 2769 @unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)? |
| 442 | 2770 |
| 2771 Both the stable and development versions of XEmacs include | |
| 1135 | 2772 internationalization support (aka MULE). MULE currently (21.4) works on |
| 2773 UNIX and Linux systems. It is possible to build with MULE on Windows | |
| 2774 systems, but if you really need MULE on Windows, it is recommended that | |
| 2775 you build and use the development (21.5) version, and deal with the | |
| 2776 instability of the development tree. Binaries compiled without MULE | |
| 2777 support run faster than MULE capable XEmacsen. | |
| 428 | 2778 |
| 2537 | 2779 @node Q1.8.2, Q1.8.3, Q1.8.1, Introduction |
| 2780 @unnumberedsubsec Q1.8.2: How can I help with internationalization? | |
| 430 | 2781 |
| 2782 If you would like to help, you may want to join the | |
| 2783 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are | |
| 2784 people who speak/write languages other than English, who are willing to | |
| 2785 use XEmacs/MULE regularly, and have some experience with Elisp. | |
| 428 | 2786 |
| 1135 | 2787 Translations of the TUTORIAL and man page are welcome, and XEmacs does |
| 2788 support multilingual menus, but we have few current translations. | |
| 2789 | |
| 2537 | 2790 @xref{Q1.5.2, How do I become a Beta Tester?}. |
| 2791 | |
| 2792 @node Q1.8.3, Q1.8.4, Q1.8.2, Introduction | |
| 2793 @unnumberedsubsec Q1.8.3: How do I type non-ASCII characters? | |
| 2417 | 2794 |
| 2459 | 2795 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in |
| 2417 | 2796 part 3 of this FAQ, for some simple methods that also work in non-MULE |
| 2797 builds of XEmacs (but only for one-octet coded character sets, and | |
| 2798 mostly for ISO 8859/1). Many of the methods available for Cyrillic | |
| 2537 | 2799 (@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE |
| 2800 has more general capabilities. @xref{Q1.8.5, Please explain the | |
| 2417 | 2801 various input methods in MULE/XEmacs}. |
| 2802 | |
| 2459 | 2803 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers |
| 2417 | 2804 display of non-ASCII characters. |
| 2805 | |
| 2537 | 2806 @node Q1.8.4, Q1.8.5, Q1.8.3, Introduction |
| 2807 @unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language? | |
| 428 | 2808 |
| 1135 | 2809 The message-catalog support was written but is badly bit-rotted. XEmacs |
| 2810 20 and 21 did @emph{not} support it, and early releases of XEmacs 22 | |
| 2811 will not either. | |
| 2812 | |
| 2813 However, menubar localization @emph{does} work. To enable it, add to | |
| 2814 your @file{Emacs} file entries like this: | |
| 428 | 2815 |
| 2816 @example | |
| 440 | 2817 Emacs*XlwMenu.resourceLabels: True |
| 2818 Emacs*XlwMenu.file.labelString: Fichier | |
| 442 | 2819 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen |
| 428 | 2820 @end example |
| 2821 | |
| 2822 The name of the resource is derived from the non-localized entry by | |
| 2823 removing punctuation and capitalizing as above. | |
| 2824 | |
| 2537 | 2825 @node Q1.8.5, Q1.8.6, Q1.8.4, Introduction |
| 2826 @unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs | |
| 428 | 2827 |
| 1135 | 2828 Mule supports a wide variety of input methods. There are three basic |
| 2829 classes: Lisp implementations, generic platform support, and library | |
| 2830 interfaces. | |
| 2831 | |
| 2832 @emph{Lisp implementations} include Quail, which provides table-driven input | |
| 2833 methods for almost all the character sets that Mule supports (including | |
| 2834 all of the ISO 8859 family, the Indic languages, Thai, and so on), and | |
| 2835 SKK, for Japanese. (SKK also supports an interface to an external | |
| 2836 "dictionary server" process.) Quail supports both typical "dead-key" | |
| 2837 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN | |
| 2838 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic | |
| 2839 methods used for Asian ideographic languages like Chinese. | |
| 2840 | |
| 2841 Lisp implementations can be less powerful (but they are not perceptibly | |
| 2842 inefficient), and of course are not portable to non-Emacs applications. | |
| 2843 The incompatibility can be very annoying. On the other hand, they | |
| 2844 require no special platform support or external libraries, so if you can | |
| 2845 display the characters, Mule can input them for you and you can edit, | |
| 2846 anywhere. | |
| 2847 | |
| 2848 @emph{Generic platform support} is currently limited to the X Input | |
| 2849 Method (XIM) framework, although support for MSIME (for MS Windows) is | |
| 2850 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework) | |
| 2851 support is extremely desirable. XIM is enabled at build time by use of | |
| 2852 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see | |
| 2853 your platform documentation. However, normally the input method you use | |
| 2854 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment | |
| 2855 variables. | |
| 2856 | |
| 2857 Of course, input skills are portable across most applications. However, | |
| 2858 especially in modern GUI systems the habit of using bucky bits has | |
| 2859 fallen into sad disuse, and many XIM systems are poorly configured for | |
| 2860 use with Emacs. For example, the kinput2 input manager (a separate | |
| 2861 process providing an interface between Japanese dictionary servers such | |
| 2862 as Canna and Wnn, and the application) tends to gobble up keystrokes | |
| 2863 generating Meta characters. This means that to edit while using an XIM | |
| 2864 input method, you must toggle the input method off every time you want | |
| 2865 to use @kbd{M-f}. Your mileage may vary. | |
| 2866 | |
| 2867 @emph{Library interfaces} are most common for Japanese, although Wnn | |
| 2868 supports Chinese (traditional and simplified) and Korean. There are | |
| 2869 Chinese and Korean input servers available, but we do not know of any | |
| 2870 patches for XEmacs to use them directly. You can use them via | |
| 2871 IM-enabled terminals, by manipulating the terminal coding systems. We | |
| 2872 describe only the Japanese-oriented systems here. The advantage of | |
| 2873 these systems is that they are very powerful, and on platforms where | |
| 2874 they are available there is typically a wide range of applications that | |
| 2875 support them. Thus your input skills are portable across applications. | |
| 2876 | |
| 2877 Mule provides built-in interfaces to the following input methods: Wnn4, | |
| 2878 Wnn6, Canna, and SJ3. These can be configured at build time. There are | |
| 2879 patches available (no URL, sorry) to support the SKK server, as well. | |
| 2880 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna | |
| 2881 is specialized to Canna. | |
| 428 | 2882 |
| 2883 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto | |
| 1135 | 2884 University. It is a powerful and complex system. Wnn4 is free and Wnn6 |
| 2885 is not. Wnn uses grammatical hints and probability of word association, | |
| 2886 so in principle Wnn can be cleverer than other methods. | |
| 2887 | |
| 2888 Canna, made by NEC, supports only Japanese. It is a simple and powerful | |
| 2889 system. Canna uses only grammar, but its grammar and dictionary are | |
| 2890 quite sophisticated. So for standard modern Japanese, Canna seems | |
| 2891 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now | |
| 2892 there is a Microsoft Windows version). | |
| 2893 | |
| 2894 SJ3, by Sony, supports only Japanese. | |
| 428 | 2895 |
| 2896 Egg consists of following parts: | |
| 2897 | |
| 2898 @enumerate | |
| 2899 @item | |
| 2900 Input character Translation System (ITS) layer. | |
| 2901 It translates ASCII inputs to Kana/PinYin/Hangul characters. | |
| 2902 | |
| 2903 @item | |
| 2904 Kana/PinYin/Hangul to Kanji transfer layer. | |
| 1135 | 2905 The interface layer to network Kana-Kanji server (Wnn and Sj3). |
| 428 | 2906 @end enumerate |
| 2907 | |
| 1135 | 2908 These input methods are modal. They have a raw (alphabet) mode, a |
| 2909 phonetic input mode, and Kana-Kanji transfer mode. However there are | |
| 2910 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a | |
| 2911 mode-less input method running on Egg. For Canna, @samp{canna.el} has a | |
| 2912 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some | |
| 2913 boiled-egg-like utilities. | |
| 2914 | |
| 2915 Much of this information was provided by @email{morioka@@jaist.ac.jp, | |
| 2916 MORIOKA Tomohiko}. | |
| 428 | 2917 |
| 2537 | 2918 @node Q1.8.6, Q1.8.7, Q1.8.5, Introduction |
| 2919 @unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs? | |
| 428 | 2920 |
| 1135 | 2921 MULE has evolved rapidly over the last few years, and the original third |
| 2922 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite | |
| 2923 different implementations. The APIs also vary although recent versions | |
| 2924 of XEmacs have tended to converge to the GNU Emacs standard. | |
| 2925 | |
| 2926 MULE implementations are going to continue to evolve. Both GNU Emacs | |
| 2927 and XEmacs are working hard on Unicode support, which will involve new | |
| 2928 APIs and probably variations on old ones. For XEmacs 22, the old ISO | |
| 2929 2022-based system for recognizing encodings will be replaced by a much | |
| 2930 more flexible system, which should improve accuracy of automatic coding | |
| 2931 detections, but will also involve new APIs. | |
| 2932 | |
| 428 | 2933 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes: |
| 2934 | |
| 2935 @quotation | |
| 1135 | 2936 The application implementor must write separate code for these mule |
| 2937 variants. [Please don't hesitate to report these variants to us; they | |
| 2938 are not, strictly speaking, bugs, but they give third-party developers | |
| 2939 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.] | |
| 428 | 2940 |
| 2941 MULE and the next version of Emacs are similar but the symbols are very | |
| 2942 different---requiring separate code as well. | |
| 2943 | |
| 2944 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of | |
| 2945 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called | |
| 1135 | 2946 @code{emu} to provide a common interface. [There is an XEmacs package |
| 2947 of APEL which provides much more comprehensive coverage. Be careful, | |
| 2948 however; APEL has problems of its own. -- Ed.] | |
| 428 | 2949 |
| 2950 I have the following suggestions about dealing with mule variants: | |
| 2951 | |
| 2952 @itemize @bullet | |
| 2953 @item | |
| 2954 @code{(featurep 'mule)} @code{t} on all mule variants | |
| 2955 | |
| 2956 @item | |
| 2957 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version | |
| 2958 of Emacs will not have this symbol. | |
| 2959 | |
| 2960 @item | |
| 2961 MULE has a variable @code{mule-version}. Perhaps the next version of | |
| 2962 Emacs will have this variable as well. | |
| 2963 @end itemize | |
| 2964 | |
| 2965 Following is a sample to distinguish mule variants: | |
| 2966 | |
| 2967 @lisp | |
| 2968 (if (featurep 'mule) | |
| 2969 (cond ((boundp 'MULE) | |
| 2970 ;; for original Mule | |
| 2971 ) | |
| 440 | 2972 ((string-match "XEmacs" emacs-version) |
| 2973 ;; for XEmacs with Mule | |
| 2974 ) | |
| 2975 (t | |
| 2976 ;; for next version of Emacs | |
| 2977 )) | |
| 428 | 2978 ;; for old emacs variants |
| 2979 ) | |
| 2980 @end lisp | |
| 2981 @end quotation | |
| 2982 | |
| 2537 | 2983 @node Q1.8.7, Q1.8.8, Q1.8.6, Introduction |
| 2984 @unnumberedsubsec Q1.8.7: How about Cyrillic modes? | |
| 428 | 2985 |
| 2986 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes: | |
| 2987 | |
| 2988 @quotation | |
| 2989 There is a cyrillic mode in the file @file{mysetup.zip} in | |
| 2990 @iftex | |
| 2991 @* | |
| 2992 @end iftex | |
| 2993 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a | |
| 2994 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el} | |
| 2995 which can be obtained from | |
| 2996 @end quotation | |
| 2997 | |
| 871 | 2998 @uref{http://www.math.uga.edu/~valery/russian.el}. |
| 428 | 2999 |
| 3000 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes: | |
| 3001 | |
| 3002 @quotation | |
| 3003 There is another cyrillic mode for both GNU Emacs and XEmacs by | |
| 3004 @email{manin@@camelot.mssm.edu, Dmitrii | |
| 3005 (Mitya) Manin} at | |
| 3006 @iftex | |
| 3007 | |
| 3008 @end iftex | |
| 3009 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}. | |
| 3010 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead. | |
| 3011 @c Changed to russian host instead | |
| 3012 @end quotation | |
| 3013 | |
| 3014 @email{rebecca.ore@@op.net, Rebecca Ore} writes: | |
| 3015 | |
| 3016 @quotation | |
| 3017 The fullest resource I found on Russian language use (in and out of | |
| 661 | 3018 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html} |
| 428 | 3019 @end quotation |
| 3020 | |
| 2537 | 3021 @node Q1.8.8, Q1.8.9, Q1.8.7, Introduction |
| 3022 @unnumberedsubsec Q1.8.8: Does XEmacs support Unicode? | |
| 2417 | 3023 |
| 3024 To get Unicode support, you need a Mule-enabled XEmacs. | |
| 3025 | |
| 3026 21.5 has internal support for Unicode and supports it fully, although we | |
| 3027 don't yet use it as the internal encoding. | |
| 3028 | |
| 3029 21.4 supports Unicode partially -- as an external encoding for files, | |
| 2537 | 3030 processes, and terminals, but without font support. @xref{Q1.8.9, How |
| 2417 | 3031 does XEmacs display Unicode?}. To get Unicode support in 21.4, |
| 3032 install Mule-UCS from packages in the usual way, and put | |
| 745 | 3033 |
| 1616 | 3034 @example |
| 745 | 3035 (require 'un-define) |
| 3036 (set-coding-priority-list '(utf-8)) | |
| 1616 | 3037 (set-coding-category-system 'utf-8 'utf-8) |
| 3038 @end example | |
| 3039 | |
| 3040 in your init file to enable the UTF-8 coding system. You may wish to | |
| 3041 view the documentation of @code{set-coding-priority-list} if you find | |
| 3042 that files that are not UTF-8 are being mis-recognized as UTF-8. | |
| 745 | 3043 |
| 2417 | 3044 Install standard national fonts (not Unicode fonts) for all character |
| 2537 | 3045 sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}. |
| 745 | 3046 |
| 3047 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not | |
| 3048 support 31-bit forms of Unicode (UTF-32 or UCS-4). | |
| 3049 | |
| 2537 | 3050 @node Q1.8.9, , Q1.8.8, Introduction |
| 3051 @unnumberedsubsec Q1.8.9: How does XEmacs display Unicode? | |
| 745 | 3052 |
| 3053 Mule doesn't have a Unicode charset internally, so there's nothing to | |
| 3054 bind a Unicode registry to. It would not be straightforward to create, | |
| 3055 either, because Unicode is not ISO 2022-compatible. You'd have to | |
| 3056 translate it to multiple 96x96 pages. | |
| 3057 | |
| 3058 This means that Mule-UCS uses ordinary national fonts for display. This | |
| 3059 is not really a problem, except for those languages that use the Unified | |
| 3060 Han characters. The problem here is that Mule-UCS maps from Unicode | |
| 3061 code points to national character sets in a deterministic way. By | |
| 3062 default, this means that Japanese fonts are tried first, then Chinese, | |
| 3063 then Korean. To change the priority ordering, use the command | |
| 3064 `un-define-change-charset-order'. | |
| 3065 | |
| 3066 It also means you can't use Unicode fonts directly, at least not without | |
| 3067 extreme hackery. You can run -nw with (set-terminal-coding-system | |
| 3068 'utf-8) if you really want a Unicode font for some reason. | |
| 3069 | |
| 3070 Real Unicode support will be introduced in XEmacs 22.0. | |
| 3071 | |
| 2459 | 3072 @node Installation, Editing, Introduction, Top |
| 2417 | 3073 @unnumbered 2 Installation and Troubleshooting |
| 428 | 3074 |
| 3075 This is part 2 of the XEmacs Frequently Asked Questions list. This | |
| 2417 | 3076 section is devoted to Installation, Maintenance and Troubleshooting. |
| 428 | 3077 |
| 3078 @menu | |
| 2559 | 3079 2.0: Installation (General) |
| 3080 * Q2.0.1:: How do I build and install XEmacs? | |
| 3081 * Q2.0.2:: Where do I find external libraries? | |
| 3082 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files? | |
| 3083 * Q2.0.4:: Running XEmacs without installing | |
| 3084 * Q2.0.5:: XEmacs is too big | |
| 3085 | |
| 3086 2.1: Package Installation | |
| 3087 * Q2.1.1:: How do I install the packages? | |
| 3088 * Q2.1.2:: Can I install the packages individually? | |
| 3089 * Q2.1.3:: Can I install the packages automatically? | |
| 3090 * Q2.1.4:: Can I upgrade or remove packages? | |
| 3091 * Q2.1.5:: Which packages to install? | |
| 3092 * Q2.1.6:: Can you describe the package location process in more detail? | |
| 3093 * Q2.1.7:: EFS fails with "500 AUTH not understood" | |
| 3094 | |
| 3095 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) | |
| 3096 * Q2.2.1:: Libraries in non-standard locations | |
| 3097 * Q2.2.2:: Why can't I strip XEmacs? | |
| 3404 | 3098 * Q2.2.3:: X11/bitmaps/gray (or other X11-related file) not found. |
| 2559 | 3099 |
| 3100 2.3: Windows Installation (Windows, Cygwin, MinGW) | |
| 3101 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows? | |
| 3102 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs? | |
| 3103 * Q2.3.3:: How do I compile the native port? | |
| 3104 * Q2.3.4:: What do I need for Cygwin? | |
| 3105 * Q2.3.5:: How do I compile under Cygwin? | |
| 3106 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 3107 * Q2.3.7:: How do I compile with X support? | |
| 3108 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 3109 | |
| 3110 2.4: General Troubleshooting | |
| 3111 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running? | |
| 3112 * Q2.4.2:: Help! XEmacs just crashed on me! | |
| 3113 * Q2.4.3:: XEmacs crashes and I compiled it myself. | |
| 3114 * Q2.4.4:: How to debug an XEmacs problem with a debugger | |
| 3115 * Q2.4.5:: I get a cryptic error message when trying to do something. | |
| 3116 * Q2.4.6:: XEmacs hangs when I try to do something. | |
| 3117 * Q2.4.7:: I get an error message when XEmacs is running in batch mode. | |
| 3118 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 3119 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken? | |
| 3120 * Q2.4.10:: How do I debug process-related problems? | |
| 3121 * Q2.4.11:: XEmacs is outputting lots of X errors. | |
| 3122 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more! | |
| 3123 | |
| 3124 2.5: Startup-Related Problems | |
| 3125 * Q2.5.1:: XEmacs cannot connect to my X Terminal! | |
| 3126 * Q2.5.2:: Startup problems related to paths or package locations. | |
| 3127 * Q2.5.3:: XEmacs won't start without network. | |
| 3128 * Q2.5.4:: Startup warnings about deducing proper fonts? | |
| 3129 * Q2.5.5:: Warnings from incorrect key modifiers. | |
| 3130 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? | |
| 428 | 3131 @end menu |
| 3132 | |
| 2559 | 3133 @unnumberedsec 2.0: Installation (General) |
| 2417 | 3134 |
| 428 | 3135 @node Q2.0.1, Q2.0.2, Installation, Installation |
| 2559 | 3136 @unnumberedsubsec Q2.0.1: How do I build and install XEmacs? |
| 3137 | |
| 3138 See the file @file{etc/NEWS} for information on new features and other | |
| 3139 user-visible changes since the last version of XEmacs. | |
| 3140 | |
| 3141 The file @file{INSTALL} in the top-level directory says how to bring | |
| 3142 up XEmacs on Unix and Cygwin, once you have loaded the entire subtree | |
| 3143 of this directory. | |
| 3144 | |
| 3145 See the file @file{nt/README} for instructions on building XEmacs for | |
| 3146 Microsoft Windows. | |
| 3147 | |
| 3148 @xref{Q2.1.1}, for the installation of (essential) add on packages. | |
| 2417 | 3149 |
| 3150 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation | |
| 2559 | 3151 @unnumberedsubsec Q2.0.2: Where do I find external libraries? |
| 2417 | 3152 |
| 2459 | 3153 All external libraries used by XEmacs can be found on the XEmacs web |
| 2417 | 3154 site |
| 3155 @iftex | |
| 3156 @* | |
| 3157 @end iftex | |
| 2459 | 3158 @uref{http://www.xemacs.org/Download/optLibs.html}. |
| 2417 | 3159 |
| 3160 The library versions available here are known to work with XEmacs. | |
| 3161 (Newer versions will probably work as well but we can't guarantee it.) | |
| 3162 We try to keep the libraries up-to-date but may not always succeed. | |
| 2459 | 3163 Check the above page for the canonical locations of the external libraries, |
| 3164 allowing you to download the latest, bleeding-edge versions. | |
| 2417 | 3165 |
| 2559 | 3166 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation |
| 3167 @unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files? | |
| 2417 | 3168 |
| 3169 You can specify what paths to use by using a number of different flags | |
| 3170 when running configure. See the section MAKE VARIABLES in the top-level | |
| 3171 file INSTALL in the XEmacs distribution for a listing of those flags. | |
| 3172 | |
| 3173 Most of the time, however, the simplest fix is: @strong{do not} specify | |
| 3174 paths as you might for GNU Emacs. XEmacs can generally determine the | |
| 3175 necessary paths dynamically at run time. The only path that generally | |
| 3176 needs to be specified is the root directory to install into. That can | |
| 3177 be specified by passing the @code{--prefix} flag to configure. For a | |
| 3178 description of the XEmacs install tree, please consult the @file{NEWS} | |
| 3179 file. | |
| 3180 | |
| 2559 | 3181 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation |
| 3182 @unnumberedsubsec Q2.0.4: Running XEmacs without installing | |
| 442 | 3183 |
| 3184 How can I just try XEmacs without installing it? | |
| 428 | 3185 |
| 3186 XEmacs will run in place without requiring installation and copying of | |
| 3187 the Lisp directories, and without having to specify a special build-time | |
| 3188 flag. It's the copying of the Lisp directories that requires so much | |
| 3189 space. XEmacs is largely written in Lisp. | |
| 3190 | |
| 3191 A good method is to make a shell alias for xemacs: | |
| 3192 | |
| 3193 @example | |
| 2459 | 3194 alias xemacs=/src/xemacs-21.5/src/xemacs |
| 428 | 3195 @end example |
| 3196 | |
| 3197 (You will obviously use whatever directory you downloaded the source | |
| 2459 | 3198 tree to instead of @file{/src/xemacs-21.5}). |
| 428 | 3199 |
| 3200 This will let you run XEmacs without massive copying. | |
| 3201 | |
| 2559 | 3202 @node Q2.0.5, Q2.1.1, Q2.0.4, Installation |
| 3203 @unnumberedsubsec Q2.0.5: XEmacs is too big | |
| 428 | 3204 |
| 442 | 3205 The space required by the installation directories can be |
| 428 | 3206 reduced dramatically if desired. Gzip all the .el files. Remove all |
| 442 | 3207 the packages you'll never want to use. Remove the TexInfo manuals. |
| 428 | 3208 Remove the Info (and use just hardcopy versions of the manual). Remove |
| 3209 most of the stuff in etc. Remove or gzip all the source code. Gzip or | |
| 3210 remove the C source code. Configure it so that copies are not made of | |
| 1138 | 3211 the support lisp. |
| 428 | 3212 |
| 3213 These are all Emacs Lisp source code and bytecompiled object code. You | |
| 3214 may safely gzip everything named *.el here. You may remove any package | |
| 3215 you don't use. @emph{Nothing bad will happen if you delete a package | |
| 3216 that you do not use}. You must be sure you do not use it though, so be | |
| 3217 conservative at first. | |
| 3218 | |
| 1648 | 3219 Any package with the possible exceptions of xemacs-base, and EFS are |
| 3220 candidates for removal. Ask yourself, @emph{Do I ever want to use this | |
| 3221 package?} If the answer is no, then it is a candidate for removal. | |
| 428 | 3222 |
| 3223 First, gzip all the .el files. Then go about package by package and | |
| 3224 start gzipping the .elc files. Then run XEmacs and do whatever it is | |
| 1648 | 3225 you normally do. If nothing bad happens, then remove the package. You |
| 3226 can remove a package via the PUI interface | |
| 3227 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages | |
| 3228 you wish to delete, and then @kbd{x} to delete them. | |
| 3229 | |
| 3230 Another method is to do @code{M-x package-get-delete-package}. | |
| 428 | 3231 |
| 2559 | 3232 @unnumberedsec 2.1: Package Installation |
| 3233 | |
| 3234 @node Q2.1.1, Q2.1.2, Q2.0.5, Installation | |
| 3235 @unnumberedsubsec Q2.1.1: How do I install the packages? | |
| 3236 | |
| 3237 There are three ways to install the packages. | |
| 3238 | |
| 3239 @enumerate | |
| 3240 @item | |
| 3241 Manually, all at once, using the 'Sumo Tarball'. | |
| 3242 @item | |
| 3243 Manually, using individual package tarballs. | |
| 3244 @item | |
| 3245 Automatically, using the package tools from XEmacs. | |
| 3246 @end enumerate | |
| 3247 | |
| 3248 If you don't want to mess with the packages, it is easiest to just | |
| 3249 grab them manually, all at once. (For the other two ways, | |
| 3250 @xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file | |
| 3251 | |
| 3252 @file{xemacs-sumo.tar.gz} | |
| 3253 | |
| 3254 For an XEmacs compiled with Mule you also need | |
| 3255 | |
| 3256 @file{xemacs-mule-sumo.tar.gz} | |
| 3257 | |
| 3258 These are in the @file{packages} directory on your XEmacs mirror | |
| 3259 archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its | |
| 3260 mirrors. N.B. They are called 'Sumo Tarballs' for good reason. They | |
| 3261 are currently about 19MB and 4.5MB (gzipped) respectively. | |
| 3262 | |
| 3263 Install them on Unix and Mac OS X using the shell/Terminal command | |
| 3264 | |
| 3265 @code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xf -} | |
| 3266 | |
| 3267 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to | |
| 3268 @file{configure}, and defaults to @file{/usr/local}. | |
| 3269 | |
| 3270 If you have GNU tar you can use: | |
| 3271 | |
| 3272 @code{cd $prefix/lib/xemacs ; tar zxvf <tarballname>} | |
| 3273 | |
| 3018 | 3274 If you have the packages somewhere nonstandard and don't want to bother |
| 3275 with @samp{$prefix} (for example, you're a developer and are compiling | |
| 3276 the packages yourself, and want your own private copy of everything), | |
| 3277 you can also directly specify this using @file{configure}. To do this | |
| 3179 | 3278 with 21.5 and above use the @samp{--with-late-packages} parameter to |
| 3018 | 3279 specify the directory under which you untarred the above tarballs. |
| 3280 Under 21.4 and previous you need to use @samp{--package-path}. Using | |
| 3281 these options looks something like this: | |
| 2559 | 3282 |
| 3283 @example | |
| 3284 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ... | |
| 3285 @end example | |
| 3286 | |
| 3287 Under Windows, you need to place the above @samp{tar.gz} files in the | |
| 3288 directory specified using the @samp{PACKAGE_PREFIX} value in | |
| 3289 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}. | |
| 3290 (To untar a @samp{tar.gz} file you will need to use a utility such as | |
| 3291 WinZip, unless you have Cygwin or a similar environment installed, in | |
| 3292 which case the above Unix shell command should work fine.) If you want | |
| 3293 the packages somewhere else, just change @samp{PACKAGE_PREFIX}. | |
| 3294 | |
| 3295 Note that XEmacs finds the packages automatically anywhere underneath | |
| 3296 the directory tree where it expects to find the packages. All you | |
| 3297 need to do is put stuff there; you don't need to run any program to | |
| 4311 | 3298 tell XEmacs to find the packages, or do anything of that sort. |
| 2559 | 3299 |
| 3300 However, XEmacs will only notice newly installed packages when it | |
| 3301 starts up, so you will have to restart if you are already running | |
| 3302 XEmacs. | |
| 3303 | |
| 3304 For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's | |
| 3305 Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}. | |
| 3306 | |
| 3307 As the Sumo tarballs are not regenerated as often as the individual | |
| 3308 packages, it is recommended that you use the automatic package tools | |
| 3309 afterwards to pick up any recent updates. | |
| 3310 | |
| 3311 @emph{NOTE}: For detailed information about how the package | |
| 3312 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp | |
| 3313 Reference Manual}. | |
| 3314 | |
| 3315 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation | |
| 3316 @unnumberedsubsec Q2.1.2: Can I install the packages individually? | |
| 3317 | |
| 3318 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. | |
| 3319 | |
| 3320 Note: If you are upgrading packages already installed, it's best to | |
| 3321 remove the old package first (@pxref{Q2.1.4}). | |
| 3322 | |
| 3323 For example if we are installing the @samp{xemacs-base} | |
| 3324 package (version 1.48): | |
| 3325 | |
| 3326 @example | |
| 3327 mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet | |
| 3328 cd $prefix/lib/xemacs/xemacs-packages RET | |
| 3329 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET | |
| 3330 @end example | |
| 3331 | |
| 3332 Or if you have GNU tar, the last step can be: | |
| 3333 | |
| 3334 @example | |
| 3335 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET | |
| 3336 @end example | |
| 3337 | |
| 3338 For MULE related packages, it is best to untar into the @samp{mule-packages} | |
| 3339 hierarchy, i.e. for the @samp{mule-base} package, version 1.37: | |
| 3340 | |
| 3341 @example | |
| 3342 mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet | |
| 3343 cd $prefix/lib/xemacs/mule-packages RET | |
| 3344 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET | |
| 3345 @end example | |
| 3346 | |
| 3347 Or if you have GNU tar, the last step can be: | |
| 3348 | |
| 3349 @example | |
| 3350 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET | |
| 3351 @end example | |
| 3352 | |
| 3353 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation | |
| 3354 @unnumberedsubsec Q2.1.3: Can I install the packages automatically? | |
| 3355 | |
| 3356 XEmacs comes with some tools to make the periodic updating and | |
| 3357 installing easier. It will notice if new packages or versions are | |
| 3358 available and will fetch them from the FTP site. | |
| 3359 | |
| 3360 Unfortunately this requires that a few packages are already in place. | |
| 3361 You will have to install them by hand as above or use a SUMO tarball. | |
| 3362 This requirement will hopefully go away in the future. The packages | |
| 3363 you need are: | |
| 3364 | |
| 3365 @example | |
| 3366 efs - To fetch the files from the FTP site or mirrors. | |
| 3367 xemacs-base - Needed by efs. | |
| 3368 @end example | |
| 3369 | |
| 3370 and optionally: | |
| 3371 | |
| 3372 @example | |
| 3373 mailcrypt - For PGP verification of the package-index file. | |
| 3374 @end example | |
| 3375 | |
| 3376 After installing these by hand, fire up XEmacs and follow these | |
| 3377 steps. | |
| 3378 | |
| 3379 @enumerate | |
| 3380 @item | |
| 3381 Choose a download site. | |
| 3382 @itemize @bullet | |
| 3383 @item | |
| 3384 via menu: Tools -> Packages -> Set Download Site | |
| 3385 @item | |
| 3386 via keyb: M-x customize-variable RET package-get-remote RET | |
| 3387 (put in the details of remote host and directory) | |
| 3388 @end itemize | |
| 3389 | |
| 3390 If the package tarballs _AND_ the package-index file are in a | |
| 3391 local directory, you can: M-x pui-set-local-package-get-directory RET | |
| 3392 | |
| 3393 @item | |
| 3394 Obtain a list of packages and display the list in a buffer named | |
| 3395 "*Packages*". | |
| 3396 @itemize @bullet | |
| 3397 @item | |
| 3398 menu: Tools -> Packages -> List & Install | |
| 3399 @item | |
| 3400 keyb: M-x pui-list-packages RET | |
| 3401 @end itemize | |
| 3402 | |
| 3403 XEmacs will now connect to the remote site and download the | |
| 3404 latest package-index file. | |
| 3405 | |
| 3406 The resulting buffer, "*Packages*" has brief instructions at the | |
| 3407 end of the buffer. | |
| 3408 | |
| 3409 @item | |
| 3410 Choose the packages you wish to install. | |
| 3411 @itemize @bullet | |
| 3412 @item | |
| 3413 mouse: Click button 2 on the package name. | |
| 3414 @item | |
| 3415 keyb: RET on the package name | |
| 3416 @end itemize | |
| 3417 | |
| 3418 @item | |
| 3419 Make sure you have everything you need. | |
| 3420 @itemize @bullet | |
| 3421 @item | |
| 3422 menu: Packages -> Add Required | |
| 3423 @item | |
| 3424 keyb: r | |
| 3425 @end itemize | |
| 3426 | |
| 3427 XEmacs will now search for packages that are required by the | |
| 3428 ones that you have chosen to install and offer to select | |
| 3429 those packages also. | |
| 3430 | |
| 3431 For novices and gurus alike, this step can save your bacon. | |
| 3432 It's easy to forget to install a critical package. | |
| 3433 | |
| 3434 @item | |
| 3435 Download and install the packages. | |
| 3436 @itemize @bullet | |
| 3437 @item | |
| 3438 menu: Packages -> Install/Remove Selected | |
| 3439 @item | |
| 3440 keyb: x | |
| 3441 @end itemize | |
| 3442 @end enumerate | |
| 3443 | |
| 3444 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation | |
| 3445 @unnumberedsubsec Q2.1.4: Can I upgrade or remove packages? | |
| 3446 | |
| 3447 As the exact files and their locations contained in a package may | |
| 3448 change it is recommended to remove a package first before installing a | |
| 4311 | 3449 new version. In order to facilitate removal each package contains a |
| 3450 pkginfo/MANIFEST.pkgname file which lists all the files belonging to | |
| 3451 the package. M-x package-admin-delete-binary-package RET can be used | |
| 3452 to remove a package using this file. | |
| 2559 | 3453 |
| 3454 Note that the interactive package tools included with XEmacs already do | |
| 3455 this for you. | |
| 3456 | |
| 3457 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation | |
| 3458 @unnumberedsubsec Q2.1.5: Which packages to install? | |
| 3459 | |
| 3460 Unless you are an advanced user, just install everything. | |
| 3461 | |
| 3462 If you really want to install only what's absolutely needed, a good | |
| 3463 minimal set of packages for XEmacs-latin1 would be | |
| 3464 | |
| 3465 @example | |
| 3466 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs, | |
| 3467 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes, | |
| 3468 text-modes, time, mailcrypt | |
| 3469 @end example | |
| 3470 | |
| 3471 If you are using the XEmacs package tools, don't forget to do: | |
| 3472 | |
| 3473 @example | |
| 3474 Packages -> Add Required | |
| 3475 @end example | |
| 3476 | |
| 3477 To make sure you have everything that the packages you have chosen to | |
| 3478 install need. | |
| 3479 | |
| 3480 @xref{Q1.7.2}, for a description of the various packages. | |
| 3481 | |
| 3482 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation | |
| 3483 @unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail? | |
| 3484 | |
| 3485 On startup XEmacs looks for packages in so-called package hierarchies. | |
| 3486 Normally, there are three system wide hierarchies, like this: | |
| 3487 | |
| 3488 @example | |
| 3489 $prefix/lib/xemacs/xemacs-packages/ | |
| 3490 Normal packages go here. | |
| 3491 | |
| 3492 $prefix/lib/xemacs/mule-packages/ | |
| 3493 Mule packages go here and are only searched by MULE-enabled XEmacsen. | |
| 3494 | |
| 3495 $prefix/lib/xemacs/site-packages/ | |
| 3496 Local and 3rd party packages go here. | |
| 3497 @end example | |
| 3498 | |
| 3499 This is what you get when you untar the SUMO tarballs under | |
| 3500 @file{$prefix/lib/xemacs}. | |
| 3501 | |
| 3502 @file{$prefix} is specified using the @samp{--prefix} parameter to | |
| 3503 @file{configure}, and defaults to @file{usr/local}. | |
| 3504 | |
| 3505 If the package path is not explicitly specified, XEmacs looks for the | |
| 3506 package directory @file{xemacs-packages} (and @file{mule-packages} and | |
| 3507 @file{site-packages}) first under @samp{~/.xemacs}, then for a sister | |
| 3508 directory @file{lib/xemacs-VERSION} of the directory in which the | |
| 3509 XEmacs executable is located, then for a sister directory | |
| 3510 @file{lib/xemacs}. The XEmacs executable (under Unix at least) is | |
| 3511 installed by default in @file{/usr/local/bin}; this explains why | |
| 3512 XEmacs in its default installation will find packages that you put | |
| 3513 under @file{/usr/local/lib/xemacs}. | |
| 3514 | |
| 3515 You can specify where exactly XEmacs looks for packages by using the | |
| 3179 | 3516 @samp{--with-user-packages} (an alias for @samp{--with-early-packages}) |
| 3517 or @samp{--with-system-packages} (an alias for | |
| 3518 @samp{--with-late-packages}) or @samp{--with-legacy-packages} | |
| 3519 (an alias for @samp{--with-last-packages}) | |
| 3520 parameters to @file{configure} (or the equivalent settings in | |
| 3521 @file{config.inc}, under Windows), or setting the | |
| 3522 @samp{EMACSEARLYPACKAGES}, @samp{EMACSLATEPACKAGES}, and | |
| 3523 @samp{EMACSLASTPACKAGES} environment variables (which have the same | |
| 3524 format as the configure options). @xref{Q2.1.1}. | |
| 2559 | 3525 |
| 3526 See @file{configure.usage} for more info about the format of these | |
| 3527 @file{configure} parameters. | |
| 3528 | |
| 3529 In addition to the system wide packages, each user can have his own | |
| 3530 packages installed under @file{~/.xemacs/}. If you want to install | |
| 3531 packages there using the interactive tools, you need to set | |
| 3532 @code{package-get-install-to-user-init-directory} to @code{t}. | |
| 3533 | |
| 3534 The site-packages hierarchy replaces the old @file{site-lisp} | |
| 3535 directory. XEmacs no longer looks into a @file{site-lisp} directly by | |
| 3536 default. A good place to put @file{site-start.el} would be in | |
| 3537 @file{$prefix/lib/xemacs/site-packages/lisp/}. | |
| 3538 | |
| 3539 @node Q2.1.7, Q2.2.1, Q2.1.6, Installation | |
| 3540 @unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW) | |
| 2417 | 3541 |
| 3542 A typical error: FTP Error: USER request failed; 500 AUTH not understood. | |
| 3543 | |
| 4311 | 3544 Thanks to Giacomo Boffi @email{giacomo.boffi@@polimi.it} who recommends |
| 2417 | 3545 on comp.emacs.xemacs: |
| 3546 | |
| 3547 tell your ftp client to not attempt AUTH authentication (or do not | |
| 3548 use FTP servers that don't understand AUTH) | |
| 3549 | |
| 3550 and notes that you need to add an element (often "-u") to | |
| 3551 `efs-ftp-program-args'. Use M-x customize-variable, and verify the | |
| 3552 needed flag with `man ftp' or other local documentation. | |
| 3553 | |
| 2559 | 3554 @unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) |
| 3555 | |
| 3556 @node Q2.2.1, Q2.2.2, Q2.1.7, Installation | |
| 3557 @unnumberedsubsec Q2.2.1: Libraries in non-standard locations | |
| 428 | 3558 |
| 2459 | 3559 If your libraries are in a non-standard location, you can specify the location |
| 3018 | 3560 using the following flags to @file{configure}. Under 21.4 or earlier: |
| 2459 | 3561 |
| 3562 @example | |
| 3563 --site-libraries=WHATEVER | |
| 3564 --site-includes=WHATEVER | |
| 3565 @end example | |
| 3566 | |
| 3018 | 3567 Under 21.5 or later: |
| 3568 | |
| 3569 @example | |
| 3570 --with-site-libraries=WHATEVER | |
| 3571 --with-site-includes=WHATEVER | |
| 3572 @end example | |
| 3573 | |
| 2459 | 3574 If you have multiple paths to specify, use the following syntax: |
| 428 | 3575 |
| 3576 @example | |
| 3577 --site-libraries='/path/one /path/two /path/etc' | |
| 3578 @end example | |
| 3579 | |
| 3018 | 3580 If the libraries and headers reside in the directories @samp{lib} and |
| 3581 @samp{include} of a common root (say @samp{/sw}) then both can be | |
| 3582 specified with a single option: | |
| 3583 | |
| 3584 @example | |
| 3585 --site-prefixes=WHATEVER | |
| 3586 @end example | |
| 3587 | |
| 3588 or for 21.5: | |
| 3589 | |
| 3590 @example | |
| 3591 --with-site-prefixes=WHATEVER | |
| 3592 @end example | |
| 3593 | |
| 3404 | 3594 @node Q2.2.2, Q2.2.3, Q2.2.1, Installation |
| 2559 | 3595 @unnumberedsubsec Q2.2.2: Why can't I strip XEmacs? |
| 428 | 3596 |
| 3597 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes: | |
| 3598 | |
| 3599 @quotation | |
| 3600 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The | |
| 3601 link gives you a bare-boned emacs (called temacs). temacs is then run, | |
| 3602 preloading some of the lisp files. The result is then dumped into a new | |
| 3603 executable, named xemacs, which will contain all of the preloaded lisp | |
| 3604 functions and data. | |
| 3605 | |
| 3606 Now, during the dump itself, the executable (code+data+symbols) is | |
| 3607 written on disk using a special unexec() function. This function is | |
| 3608 obviously heavily system dependent. And on some systems, it leads to an | |
| 3609 executable which, although valid, cannot be stripped without damage. If | |
| 3610 memory serves, this is especially the case for AIX binaries. On other | |
| 462 | 3611 architectures it might work OK. |
| 428 | 3612 |
| 3613 The Right Way to strip the emacs binary is to strip temacs prior to | |
| 3614 dumping xemacs. This will always work, although you can do that only if | |
| 3615 you install from sources (as temacs is @file{not} part of the binary | |
| 3616 kits). | |
| 3617 @end quotation | |
| 3618 | |
| 3619 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes: | |
| 3620 | |
| 3621 @quotation | |
| 3622 Here is the trick: | |
| 3623 | |
| 3624 @enumerate | |
| 3625 @item | |
| 3626 [ ./configure; make ] | |
| 3627 | |
| 3628 @item | |
| 3629 rm src/xemacs | |
| 3630 | |
| 3631 @item | |
| 3632 strip src/temacs | |
| 3633 | |
| 3634 @item | |
| 3635 make | |
| 3636 | |
| 3637 @item | |
| 3638 cp src/xemacs /usr/local/bin/xemacs | |
| 3639 | |
| 3640 @item | |
| 3641 cp lib-src/DOC-19.16-XEmacs | |
| 3642 @iftex | |
| 3643 \ @* | |
| 3644 @end iftex | |
| 3645 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout | |
| 3646 @end enumerate | |
| 3647 @end quotation | |
| 3648 | |
| 3404 | 3649 @node Q2.2.3, Q2.3.1, Q2.2.2, Installation |
| 3650 @unnumberedsubsec Q2.2.3: X11/bitmaps/gray (or other X11-related file) not found. | |
| 3651 | |
| 3652 The X11R6 distribution was monolithic, but the X11R7 distribution is | |
| 3653 much more modular. Many OS distributions omit these bitmaps (assuming | |
| 3654 nobody uses them, evidently). Your OS distribution should have a | |
| 3655 developer's package containing these files, probably with a name | |
| 3656 containing the string "bitmap". Known package names (you may need to | |
| 3657 add an extension such as .deb or .rpm) include x11/xbitmaps (Ubuntu) | |
| 3658 and xorg-x11-xbitmaps (Fedora Core 5). | |
| 3659 | |
| 2559 | 3660 @unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW) |
| 3661 | |
| 3404 | 3662 @node Q2.3.1, Q2.3.2, Q2.2.3, Installation |
| 2559 | 3663 @unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows? |
| 2417 | 3664 |
| 3665 XEmacs can be built in several ways in the MS Windows environment. | |
| 3666 | |
| 3667 The standard way is what we call the "native" port. It uses the Win32 | |
| 3668 API and has no connection with X whatsoever -- it does not require X | |
| 3669 libraries to build, nor does it require an X server to run. The native | |
| 3670 port is the most reliable version and provides the best graphical | |
| 3671 support. Almost all development is geared towards this version, and | |
| 3672 there is little reason not to use it. | |
| 3673 | |
| 3674 The second way to build is the Cygwin port. It takes advantage of | |
| 2537 | 3675 Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin |
| 2417 | 3676 and MinGW, and do I need them to run XEmacs?}, for more information. |
| 3677 | |
| 3678 A third way is the MinGW port. It uses the Cygwin environment to | |
| 2537 | 3679 build but does not require it at runtime. @xref{Q1.2.5, What are |
| 2417 | 3680 Cygwin and MinGW, and do I need them to run XEmacs?}, for more |
| 3681 information. | |
| 3682 | |
| 3683 Finally, you might also be able to build the non-Cygwin, non-MinGW "X" | |
| 3684 port. This was actually the first version of XEmacs that ran under MS | |
| 3685 Windows, and although the code is still in XEmacs, it's essentially | |
| 3686 orphaned and it's unlikely it will compile without a lot of work. If | |
| 3687 you want an MS Windows versin of XEmacs that supports X, use the Cygwin | |
| 3688 version. (The X support there is actively maintained, so that Windows | |
| 3689 developers can test the X support in XEmacs.) | |
| 3690 | |
| 2559 | 3691 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation |
| 3692 @unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs? | |
| 2417 | 3693 |
| 3694 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have | |
| 3695 some beta testers currently trying to compile with VC.NET, aka version | |
| 3696 7.0, but we can't yet report complete success.) For the Cygwin and | |
| 3697 MinGW versions, you need the Cygwin environment, which comes with GCC, | |
| 2537 | 3698 the compiler used for those versions. @xref{Q1.2.5, What are Cygwin |
| 2417 | 3699 and MinGW, and do I need them to run XEmacs?}, for more information on |
| 3700 Cygwin and MinGW. | |
| 3701 | |
| 2559 | 3702 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation |
| 3703 @unnumberedsubsec Q2.3.3: How do I compile the native port? | |
| 2417 | 3704 |
| 3705 Please read the file @file{nt/README} in the XEmacs distribution, which | |
| 3706 contains the full description. | |
| 3707 | |
| 2559 | 3708 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation |
| 3709 @unnumberedsubsec Q2.3.4: What do I need for Cygwin? | |
| 2417 | 3710 |
| 3711 You can find the Cygwin tools and compiler at: | |
| 3712 | |
| 3713 @uref{http://www.cygwin.com/} | |
| 3714 | |
| 3715 Click on the @samp{Install or update now!} link, which will download a | |
| 3716 file @file{setup.exe}, which you can use to download everything | |
| 3717 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is | |
| 3718 probably the best.) You should go ahead and install everything -- | |
| 3719 you'll get various ancillary libraries that XEmacs needs or likes, | |
| 3720 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you | |
| 3721 want to compile under X. | |
| 3722 | |
| 3723 If you want to compile without X, you will need the @file{xpm-nox} | |
| 3724 library, which must be specifically selected in the Cygwin netinstaller; | |
| 3725 it is not selected by default. The package has had various names. | |
| 3726 Currently it is called @file{cygXpm-noX4.dll}. | |
| 3727 | |
| 2559 | 3728 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation |
| 3729 @unnumberedsubsec Q2.3.5: How do I compile under Cygwin? | |
| 2417 | 3730 |
| 3731 Similar as on Unix; use the usual `configure' and `make' process. | |
| 3732 Some problems to watch out for: | |
| 3733 | |
| 3734 @itemize @bullet | |
| 3735 @item | |
| 3736 make sure HOME is set. This controls where you | |
| 3737 @file{init.el} file comes from; | |
| 3738 | |
| 3739 @item | |
| 3740 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work; | |
| 3741 | |
| 3742 @item | |
| 3743 picking up some other grep or other UNIX-like tools can kill configure; | |
| 3744 | |
| 3745 @item | |
| 3746 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive | |
| 3747 number; | |
| 3748 | |
| 3749 @item | |
| 3750 (Unconfirmed) The Cygwin version doesn't understand | |
| 3751 @file{//machine/path} type paths so you will need to manually mount a | |
| 3752 directory of this form under a unix style directory for a build to work | |
| 3753 on the directory; | |
| 3754 | |
| 3755 @item | |
| 3756 If you're building @strong{WITHOUT} X11, don't forget to change symlinks | |
| 3757 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to | |
| 3758 the non-X versions of these libraries. By default they point to the X | |
| 3759 versions. So: | |
| 3760 | |
| 3761 @example | |
| 3762 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a | |
| 3763 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a | |
| 3764 @end example | |
| 3765 | |
| 3766 (This advice may now be obsolete because of the availability of the | |
| 3767 cygXpm-noX4.dll package from Cygwin. Send confirmation to | |
| 3768 @email{faq@@xemacs.org}.) | |
| 3769 | |
| 3770 @item | |
| 3771 Other problems are listed in the @file{PROBLEMS} file, in the top-level | |
| 3772 directory of the XEmacs sources. | |
| 3773 | |
| 3774 @end itemize | |
| 3775 | |
| 3776 | |
| 2559 | 3777 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation |
| 3778 @unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 2417 | 3779 |
| 3780 Similar to the method for Unix. Things to remember: | |
| 3781 | |
| 3782 @itemize @bullet | |
| 3783 @item | |
| 3784 Specify the target host on the command line for @file{./configure}, e.g. | |
| 3785 @samp{./configure i586-pc-mingw32}. | |
| 3786 | |
| 3787 @item | |
| 3788 Be sure that your build directory is mounted such that it has the | |
| 3789 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows | |
| 3790 path (@file{c:\build\xemacs}). | |
| 3791 | |
| 3792 @item | |
| 3793 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng}, | |
| 3794 @file{compface}, etc. | |
| 3795 | |
| 3796 @item | |
| 3797 Specify the target location of the extra libs on the command line | |
| 3018 | 3798 to @file{configure}, e.g.for 21.4 or earlier |
| 3799 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32} and for | |
| 3800 21.5 or later | |
| 3801 @samp{./configure --with-site-prefixes=/build/libs i586-pc-mingw32}. | |
| 2417 | 3802 @end itemize |
| 3803 | |
| 2559 | 3804 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation |
| 3805 @unnumberedsubsec Q2.3.7: How do I compile with X support? | |
| 2417 | 3806 |
| 3807 To compile under Cygwin, all you need to do is install XFree86, which | |
| 3808 is available as part of the standard Cygwin installation. | |
| 3809 @uref{http://www.cygwin.com/}. Once installed, @file{configure} | |
| 3810 should automatically find the X libraries and compile with X support. | |
| 3811 | |
| 3812 As noted above, the non-Cygwin X support is basically orphaned, and | |
| 3813 probably won't work. But if it want to try, it's described in | |
| 3814 @file{nt/README} in some detail. Basically, you need to get X11 | |
| 2459 | 3815 libraries from @uref{http://ftp.x.org}, and compile them. If the |
| 2417 | 3816 precompiled versions are available somewhere, we don't know of it. |
| 3817 | |
| 2559 | 3818 @node Q2.3.8, Q2.4.1, Q2.3.7, Installation |
| 3819 @unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 1058 | 3820 |
| 3821 The Cygwin binary distributed with the netinstaller uses an external DLL | |
| 3822 to handle XPM images (such as toolbar buttons). You may get an error like | |
| 3823 | |
| 2559 | 3824 @example |
| 3825 This application has failed to start because cygXpm-noX4.dll was not found. | |
| 3826 Re-installing the application may fix this problem. | |
| 3827 @end example | |
| 1058 | 3828 |
| 3829 Andy Piper <andy@@xemacs.org> sez: | |
| 3830 | |
| 2559 | 3831 @example |
| 3832 cygXpm-noX4 is part of the cygwin distribution under libraries or | |
| 3833 graphics, but is not installed by default. You need to run the | |
| 3834 cygwin setup again and select this package. | |
| 3835 @end example | |
| 1058 | 3836 |
| 3837 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs | |
| 3838 distribution. | |
| 3839 | |
| 2559 | 3840 @unnumberedsec 2.4: General Troubleshooting |
| 3841 | |
| 3842 @node Q2.4.1, Q2.4.2, Q2.3.8, Installation | |
| 3843 @unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running? | |
| 3844 | |
| 3845 The file @file{PROBLEMS} contains information on many common problems that | |
| 3846 occur in building, installing and running XEmacs. | |
| 3847 | |
| 3848 Reports of bugs in XEmacs should be sent to | |
| 3849 @email{xemacs-beta@@xemacs.org}. You can also post to the newsgroup | |
| 3850 comp.emacs.xemacs (or equivalentlt, send to the mailing list | |
| 3851 @email{xemacs@@xemacs.org}), but it is less likely that the developers | |
| 3852 will see it in a timely fashion. @xref{Bugs,,, xemacs, the XEmacs | |
| 3853 User's Manual}, for more information on how to report bugs. | |
| 3854 @xref{Q1.4.2}, for more information on mailing lists relating to | |
| 3855 XEmacs. | |
| 3856 | |
| 3857 There are three ways to read the Bugs section. | |
| 3858 | |
| 3859 @enumerate | |
| 3860 @item | |
| 3861 In a printed copy of the XEmacs manual. | |
| 3862 | |
| 3863 @item | |
| 3864 With Info. First, start XEmacs. From the menu, select | |
| 3865 @samp{Help->Info (Online Docs)->Info Contents} to enter Info, then | |
| 3866 click on @samp{XEmacs}, then on @samp{Bugs}. Or, use the keyboard: do | |
| 3867 @kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs | |
| 3868 manual, then @kbd{m Bugs RET} to get to the section on bugs. Or use | |
| 3869 standalone Info in a like manner. (Standalone Info is part of the | |
| 3870 Texinfo distribution, not part of the XEmacs distribution.) | |
| 3871 | |
| 3872 @item | |
| 3873 By hand. Do | |
| 3874 @example | |
| 3875 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs," | |
| 3876 @end example | |
| 3877 @end enumerate | |
| 3878 | |
| 3879 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation | |
| 3880 @unnumberedsubsec Q2.4.2: Help! XEmacs just crashed on me! | |
| 428 | 3881 |
| 3882 First of all, don't panic. Whenever XEmacs crashes, it tries extremely | |
| 3883 hard to auto-save all of your files before dying. (The main time that | |
| 3884 this will not happen is if the machine physically lost power or if you | |
| 3885 killed the XEmacs process using @code{kill -9}). The next time you try | |
| 3886 to edit those files, you will be informed that a more recent auto-save | |
| 3887 file exists. You can use @kbd{M-x recover-file} to retrieve the | |
| 3888 auto-saved version of the file. | |
| 3889 | |
| 462 | 3890 You can use the command @kbd{M-x recover-session} after a crash to pick |
| 3891 up where you left off. | |
| 428 | 3892 |
| 3893 Now, XEmacs is not perfect, and there may occasionally be times, or | |
| 3894 particular sequences of actions, that cause it to crash. If you can | |
| 3895 come up with a reproducible way of doing this (or even if you have a | |
| 3896 pretty good memory of exactly what you were doing at the time), the | |
| 2417 | 3897 maintainers would be very interested in knowing about it. The best |
| 3898 way to report a bug is using @kbd{M-x report-emacs-bug} (or by | |
| 3899 selecting @samp{Send Bug Report...} from the Help menu). If that | |
| 3900 won't work (e.g. you can't get XEmacs working at all), send ordinary | |
| 3901 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include | |
| 3902 the output from the crash, especially including the Lisp backtrace, as | |
| 3903 well as the XEmacs configuration from @kbd{M-x describe-installation} | |
| 3904 (or equivalently, the file @file{Installation} in the top of the build | |
| 3905 tree). Note that the developers do @emph{not} usually follow | |
| 3906 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for | |
| 3907 general questions about XEmacs than bug reports. | |
| 428 | 3908 |
| 1183 | 3909 If at all possible, include a C stack backtrace of the core dump that |
| 2417 | 3910 was produced. This shows where exactly things went wrong, and makes |
| 3911 it much easier to diagnose problems. To do this under Unix and Mac OS | |
| 3912 X, you need to locate the core file (it's called @file{core}, and is | |
| 3913 usually sitting in the directory that you started XEmacs from, or your | |
| 3914 home directory if that other directory was not writable). Then, go to | |
| 3915 that directory and execute a command like: | |
| 428 | 3916 |
| 3917 @example | |
| 3918 gdb `which xemacs` core | |
| 3919 @end example | |
| 3920 | |
| 3921 and then issue the command @samp{where} to get the stack backtrace. You | |
| 3922 might have to use @code{dbx} or some similar debugger in place of | |
| 3923 @code{gdb}. If you don't have any such debugger available, complain to | |
| 3924 your system administrator. | |
| 3925 | |
| 2417 | 3926 It's possible that a core file didn't get produced or the stack trace |
| 3927 from gdb is garbage, in which case you're out of luck unless you can | |
| 3928 reproduce the bug. A nonexistent core file can happen in some | |
| 3929 circumstances on some operating systems, depending on what exactly | |
| 3930 triggered the crash. It's also possible, however, that your limits | |
| 3931 are set to turn them off. You may be able to reenable them using a | |
| 3932 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find | |
| 3933 out how your limits are set, use the command @samp{limit}.) However, if | |
| 3934 you didn't explicitly set your limits this way, go complain to your | |
| 3935 system administrator and tell him not to disable core files by | |
| 3936 default. | |
| 3937 | |
| 3938 A garbaged stack trace can happen for various reasons. Some versions | |
| 3939 of gdb are broken on certain operating systems and aren't able to read | |
| 3940 the core file. It's also possible that the stack got overwritten | |
| 3941 during the crash. A very simple reason, however, is that your version | |
| 3942 of XEmacs was compiled without debugging information or had the | |
| 3943 debugging information stripped. A compilation with optimization can | |
| 3944 also result in partly or completely garbaged stack trace. In such | |
| 3945 cases, you will need to recompile XEmacs with debugging information | |
| 2559 | 3946 and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem |
| 2417 | 3947 with a debugger}. Note also that core files currently don't work at |
| 3948 all under Cygwin, and the only way to get a backtrace is to run XEmacs | |
| 3949 from gdb. | |
| 3950 | |
| 3951 If you cannot get a backtrace from the core dump, but can reproduce | |
| 3952 the problem, try running XEmacs under gdb. The goal is to get clean C | |
| 3953 and Lisp backtraces and submit a bug report including full | |
| 3954 configuration information as described above, as this will greatly | |
| 3955 assist in the process of tracking down the bug. However, even partial | |
| 3956 information is better than none. The process of getting backtraces | |
| 2559 | 3957 from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs |
| 2417 | 3958 problem with a debugger}. |
| 428 | 3959 |
| 1183 | 3960 If you're under Microsoft Windows, you're out of luck unless you happen |
| 3961 to have a debugging aid installed on your system, for example Visual | |
| 3962 C++. In this case, the crash will result in a message giving you the | |
| 3963 option to enter a debugger (for example, by pressing @samp{Cancel}). Do | |
| 3964 this and locate the stack-trace window. (If your XEmacs was built | |
| 3965 without debugging information, the stack trace may not be very useful.) | |
| 3966 | |
| 428 | 3967 When making a problem report make sure that: |
| 3968 | |
| 3969 @enumerate | |
| 3970 @item | |
| 3971 Report @strong{all} of the information output by XEmacs during the | |
| 3972 crash. | |
| 3973 | |
| 3974 @item | |
| 2417 | 3975 You mention what O/S and Hardware you are running XEmacs on. |
| 428 | 3976 |
| 3977 @item | |
| 3978 What version of XEmacs you are running. | |
| 3979 | |
| 3980 @item | |
| 3981 What build options you are using. | |
| 3982 | |
| 3983 @item | |
| 2417 | 3984 If the problem is related to graphics and you are running Unix or Mac |
| 3985 OS X, we will also need to know what version of the X Window System | |
| 3986 you are running, and what window manager you are using. | |
| 1183 | 3987 |
| 3988 @item | |
| 3989 If the problem happened on a TTY, please include the terminal type. | |
| 2417 | 3990 |
| 3991 @item | |
| 3992 Try very hard to get both C and Lisp backtraces, as described above. | |
| 428 | 3993 @end enumerate |
| 3994 | |
| 1135 | 3995 Much of the information above is automatically generated by @kbd{M-x |
| 3996 report-emacs-bug}. Even more, and often useful, information can be | |
| 3997 generated by redirecting the output of @code{make} and @code{make check} | |
| 3998 to a file (@file{beta.err} is the default used by @code{build-report}), | |
| 3999 and executing @kbd{M-x build-report}. | |
| 4000 | |
| 2417 | 4001 |
| 2559 | 4002 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation |
| 4003 @unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself. | |
| 2417 | 4004 |
| 4005 There have been a variety of reports of crashes due to compilers with | |
| 4006 buggy optimizers. If you are compiling with optimization, consider | |
| 2559 | 4007 turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a |
| 2417 | 4008 debugger}) and recompiling. |
| 4009 | |
| 4010 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in | |
| 4011 the top-level source directory) to read what it says about your | |
| 4012 platform. | |
| 4013 | |
| 3018 | 4014 If you compiled XEmacs 21.4 or ealier using @samp{--use-union-type}, or |
| 4015 21.5 or later using @samp{--enable-union-type} (or in either case used | |
| 4016 the option @samp{USE_UNION_TYPE} in @file{config.inc} under Windows), | |
| 4017 try recompiling again without it. The union type has been known to | |
| 4018 trigger compiler errors in a number of cases. | |
| 2417 | 4019 |
| 2559 | 4020 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation |
| 4021 @unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger | |
| 428 | 4022 |
| 4023 If XEmacs does crash on you, one of the most productive things you can | |
| 4024 do to help get the bug fixed is to poke around a bit with the debugger. | |
| 4025 Here are some hints: | |
| 4026 | |
| 4027 @itemize @bullet | |
| 4028 @item | |
| 4029 First of all, if the crash is at all reproducible, consider very | |
| 563 | 4030 strongly recompiling your XEmacs with debugging symbols and with no |
| 4031 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} -- | |
| 4032 that's an "oh" followed by a zero), and with the configure options | |
| 3018 | 4033 @samp{--debug=yes} and @samp{--error-checking=all} |
| 4034 (@samp{--enable-debug=yes} and @samp{--enable-error-checking=all} on | |
| 4035 XEmacs 21.5 or later). This will make your XEmacs run somewhat slower, | |
| 4036 but you are a lot more likely to catch the problem earlier (closer to | |
| 4037 its source). It makes it a lot easier to determine what's going on with | |
| 4038 a debugger. The way to control the compiler flags is with the | |
| 4039 configuration option @samp{--cflags} (@samp{--with-cflags} in 21.5). If | |
| 4040 you have a recent version of 21.5, you should use | |
| 2417 | 4041 @samp{--without-optimization} in preference to directly setting |
| 4042 @samp{--cflags}. | |
| 1258 | 4043 |
| 4044 @item | |
| 4045 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie | |
| 4046 process), or it's inconvenient to run XEmacs again because XEmacs is | |
| 4047 already running or is running in batch mode as part of a bunch of | |
| 4048 scripts, you may be able to attach to the existing process with your | |
| 2417 | 4049 debugger. Under Unix and Mac OS X, the typical way to do this is to |
| 4050 first use some variant of the @samp{ps} command to figure out the | |
| 4051 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under | |
| 4052 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V, | |
| 4053 or @samp{ps -aW | grep xemacs} under Cygwin. Then run | |
| 4054 | |
| 4055 @example | |
| 4056 gdb /path/to/xemacs/xemacs #### | |
| 4057 @end example | |
| 4058 | |
| 4059 Where @code{####} is the process id of your XEmacs. (If you're not | |
| 4060 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs | |
| 4061 will stop and you can type @samp{where} in gdb to get a stack trace as | |
| 4062 usual. To get things moving again, you can just type @samp{quit} in | |
| 4063 gdb. It'll tell you the program is running and ask if you want to | |
| 4064 quit anyways. Say @samp{y} and it'll quit and have your emacs | |
| 4065 continue from where it was at. | |
| 4066 | |
| 4067 If you're running another debugger, a similar method may work, or you | |
| 4068 may have to run the debugger first and then use the @code{attach} | |
| 4069 command or something similar. | |
| 4070 | |
| 4071 Under Microsoft Windows, use the menu item @samp{Build->Start | |
| 4072 Debug->Attach to Process...} and select the XEmacs process from the list | |
| 4073 given. | |
| 1258 | 4074 |
| 4075 @item | |
| 4076 If you're able to run XEmacs under a debugger and reproduce the crash, | |
| 4077 here are some things you can do: | |
| 428 | 4078 |
| 4079 @item | |
| 4080 If XEmacs is hitting an assertion failure, put a breakpoint on | |
| 4081 @code{assert_failed()}. | |
| 4082 | |
| 4083 @item | |
| 4084 If XEmacs is hitting some weird Lisp error that's causing it to crash | |
| 4085 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is | |
| 2417 | 4086 declared static in @file{eval.c}. |
| 428 | 4087 |
| 4088 @item | |
| 563 | 4089 If XEmacs is outputting lots of X errors, put a breakpoint on |
| 2417 | 4090 @code{x_error_handler()}; that will tell you which call is causing |
| 4091 them. Note that the result may not be very useful by default because | |
| 4092 X Windows normally operates asynchronously: A bunch of commands are | |
| 4093 buffered up and then sent to the server all at once. This greatly | |
| 4094 improves performance over a network but means that an error may not be | |
| 4095 reported until the server receives the commands, which can be long | |
| 4096 after XEmacs made the erroneous calls. For best results, you need to | |
| 4097 make the X server synchronous before getting the backtrace. This can | |
| 4098 be done by starting XEmacs with the @samp{-sync} option or executing | |
| 4099 the Lisp code @code{(x-debug-mode t)}. | |
| 563 | 4100 |
| 4101 @item | |
| 428 | 4102 Internally, you will probably see lots of variables that hold objects of |
| 1258 | 4103 type @code{Lisp_Object}. These are references to Lisp objects. |
| 4104 Printing them out with the debugger probably won't be too | |
| 4105 useful---you'll likely just see a number. To decode them, do this: | |
| 428 | 4106 |
| 4107 @example | |
| 2417 | 4108 call debug_print (OBJECT) |
| 428 | 4109 @end example |
| 4110 | |
| 4111 where @var{OBJECT} is whatever you want to decode (it can be a variable, | |
| 1258 | 4112 a function call, etc.). This uses the Lisp printing routines to out a |
| 4113 readable representation on the TTY from which the xemacs process was | |
| 4114 invoked. | |
| 428 | 4115 |
| 2417 | 4116 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent |
| 4117 of @code{debug_print}. You can also try @code{dpa} if you can't see | |
| 4118 the output from @code{debug_print} (this will return a string containing | |
| 4119 the output), or use @code{debug_p3} if @code{debug_print} itself triggers | |
| 4120 a crash (this is a less comprehensive but super-safe way to print out | |
| 4121 a Lisp object). | |
| 4122 | |
| 428 | 4123 @item |
| 4124 If you want to get a Lisp backtrace showing the Lisp call | |
| 4125 stack, do this: | |
| 4126 | |
| 4127 @example | |
| 2417 | 4128 call debug_backtrace () |
| 428 | 4129 @end example |
| 4130 | |
| 2417 | 4131 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent |
| 4132 of @code{debug_backtrace}. | |
| 4133 | |
| 4134 @item | |
| 4135 Using @code{debug_print} and @code{debug_backtrace} has two | |
| 4136 disadvantages - they can only be used with a running (including hung | |
| 4137 or zombie) xemacs process, and they do not display the internal C | |
| 4138 structure of a Lisp Object. Even if all you've got is a core dump, | |
| 4139 all is not lost. | |
| 428 | 4140 |
| 4141 If you're using GDB, there are some macros in the file | |
| 438 | 4142 @file{src/.gdbinit} in the XEmacs source distribution that should make |
| 4143 it easier for you to decode Lisp objects. This file is automatically | |
| 4144 read by gdb if gdb is run in the directory where xemacs was built, and | |
| 4145 contains these useful macros to inspect the state of xemacs: | |
| 4146 | |
| 4147 @table @code | |
| 4148 @item pobj | |
| 4149 Usage: pobj lisp_object @* | |
| 4150 Print the internal C representation of a lisp object. | |
| 4151 | |
| 4152 @item xtype | |
| 4153 Usage: xtype lisp_object @* | |
| 4154 Print the Lisp type of a lisp object. | |
| 4155 | |
| 4156 @item lbt | |
| 4157 Usage: lbt @* | |
| 4158 Print the current Lisp stack trace. | |
| 1258 | 4159 Requires a running xemacs process. (It works by calling the db |
| 4160 routine described above.) | |
| 438 | 4161 |
| 4162 @item ldp | |
| 4163 Usage: ldp lisp_object @* | |
| 4164 Print a Lisp Object value using the Lisp printer. | |
| 1258 | 4165 Requires a running xemacs process. (It works by calling the dp |
| 4166 routine described above.) | |
| 438 | 4167 |
| 4168 @item run-temacs | |
| 4169 Usage: run-temacs @* | |
| 4170 Run temacs interactively, like xemacs. | |
| 4171 Use this with debugging tools (like purify) that cannot deal with dumping, | |
| 4172 or when temacs builds successfully, but xemacs does not. | |
| 4173 | |
| 4174 @item dump-temacs | |
| 4175 Usage: dump-temacs @* | |
| 4176 Run the dumping part of the build procedure. | |
| 4177 Use when debugging temacs, not xemacs! | |
| 4178 Use this when temacs builds successfully, but xemacs does not. | |
| 4179 | |
| 4180 @item check-xemacs | |
| 4181 Usage: check-xemacs @* | |
| 4182 Run the test suite. Equivalent to 'make check'. | |
| 4183 | |
| 4184 @item check-temacs | |
| 4185 Usage: check-temacs @* | |
| 4186 Run the test suite on temacs. Equivalent to 'make check-temacs'. | |
| 4187 Use this with debugging tools (like purify) that cannot deal with dumping, | |
| 4188 or when temacs builds successfully, but xemacs does not. | |
| 4189 @end table | |
| 428 | 4190 |
| 4191 If you are using Sun's @file{dbx} debugger, there is an equivalent file | |
| 438 | 4192 @file{src/.dbxrc}, which defines the same commands for dbx. |
| 428 | 4193 |
| 4194 @item | |
| 4195 If you're using a debugger to get a C stack backtrace and you're seeing | |
| 4196 stack traces with some of the innermost frames mangled, it may be due to | |
| 4197 dynamic linking. (This happens especially under Linux.) Consider | |
| 3018 | 4198 reconfiguring with @samp{--dynamic=no} (@samp{--with-dynamic=no} in 21.5 |
| 4199 or later). Also, sometimes (again under Linux), stack backtraces of | |
| 4200 core dumps will have the frame where the fatal signal occurred mangled; | |
| 4201 if you can obtain a stack trace while running the XEmacs process under a | |
| 4202 debugger, the stack trace should be clean. | |
| 428 | 4203 |
| 1183 | 4204 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so |
| 4205 version 1.8 if dynamic linking and debugging is a problem on Linux. | |
| 428 | 4206 |
| 4207 @item | |
| 4208 If you're using a debugger to get a C stack backtrace and you're | |
| 4209 getting a completely mangled and bogus stack trace, it's probably due to | |
| 4210 one of the following: | |
| 4211 | |
| 4212 @enumerate a | |
| 4213 @item | |
| 4214 Your executable has been stripped. Bad news. Tell your sysadmin not to | |
| 4215 do this---it doesn't accomplish anything except to save a bit of disk | |
| 4216 space, and makes debugging much much harder. | |
| 4217 | |
| 4218 @item | |
| 4219 Your stack is getting trashed. Debugging this is hard; you have to do a | |
| 4220 binary-search type of narrowing down where the crash occurs, until you | |
| 4221 figure out exactly which line is causing the problem. Of course, this | |
| 1258 | 4222 only works if the bug is highly reproducible. Also, in many cases if |
| 4223 you run XEmacs from the debugger, the debugger can protect the stack | |
| 4224 somewhat. However, if the stack is being smashed, it is typically the | |
| 4225 case that there is a wild pointer somewhere in the program, often quite | |
| 4226 far from where the crash occurs. | |
| 428 | 4227 |
| 4228 @item | |
| 4229 If your stack trace has exactly one frame in it, with address 0x0, this | |
| 4230 could simply mean that XEmacs attempted to execute code at that address, | |
| 4231 e.g. through jumping to a null function pointer. Unfortunately, under | |
| 4232 those circumstances, GDB under Linux doesn't know how to get a stack | |
| 1183 | 4233 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I |
| 428 | 4234 have no idea why GDB under Linux is so bogus. Complain to the GDB |
| 1183 | 4235 authors, or to comp.os.linux.development.system.) Again, you'll have to |
| 428 | 4236 use the narrowing-down process described above. |
| 4237 | |
| 4238 @item | |
| 462 | 4239 You will get a Lisp backtrace output when XEmacs crashes, so you'll have |
| 4240 something useful. | |
| 428 | 4241 |
| 4242 @end enumerate | |
| 4243 | |
| 4244 @item | |
| 4245 If you compile with the newer gcc variants gcc-2.8 or egcs, you will | |
| 438 | 4246 also need gdb 4.17 or above. Earlier releases of gdb can't handle the |
| 4247 debug information generated by the newer compilers. | |
| 428 | 4248 |
| 4249 @item | |
| 438 | 4250 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named |
| 4251 @file{src/gdbinit}. This had the disadvantage of not being sourced | |
| 4252 automatically by gdb, so you had to set that up yourself. | |
| 428 | 4253 |
| 1183 | 4254 @item |
| 4255 If you are running Microsoft Windows, the the file @file{nt/README} for | |
| 4256 further information about debugging XEmacs. | |
| 4257 | |
| 428 | 4258 @end itemize |
| 4259 | |
| 2559 | 4260 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation |
| 4261 @unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something. | |
| 2417 | 4262 |
| 4263 When I try to use some particular option of some particular package, I | |
| 4264 get a cryptic error message in the minibuffer. | |
| 4265 | |
| 4266 If the message went by too quickly, use @samp{Help->Recent Messages} | |
| 4267 from the menubar (or type @kbd{C-h l}) to see recent messages. | |
| 4268 | |
| 4269 If you can't figure out what's going on, select | |
| 4270 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or | |
| 4271 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make | |
| 4272 the error happen again. This will put in the debugger (you can get | |
| 4273 out of this and continue what you were doing before by typing @kbd{c}) | |
| 4274 and give you a backtrace that may be enlightening. If not, try | |
| 4275 reading through this FAQ; if that fails, you could try posting to | |
| 4276 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and | |
| 4277 someone may be able to help. If you can identify which XEmacs Lisp | |
| 4278 source file the error is coming from you can get a more detailed stack | |
| 4279 backtrace by doing the following: | |
| 428 | 4280 |
| 4281 @enumerate | |
| 4282 @item | |
| 2417 | 4283 Visit the .el file in an XEmacs buffer. |
| 4284 | |
| 4285 @item | |
| 4286 Issue the command @kbd{M-x eval-current-buffer}. | |
| 4287 | |
| 4288 @item | |
| 4289 Reproduce the error. | |
| 428 | 4290 @end enumerate |
| 4291 | |
| 2417 | 4292 For more information on debugging Lisp code, @xref{Debugging,,, |
| 4293 lispref, XEmacs Lisp Reference Manual}. | |
| 4294 | |
| 2559 | 4295 @node Q2.4.6, Q2.4.7, Q2.4.5, Installation |
| 4296 @unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something. | |
| 2417 | 4297 |
| 4298 XEmacs might just be slow; some operations take a long time. XEmacs | |
| 4299 may also be waiting on a response from the network, for example when | |
| 4300 you are trying to send mail. | |
| 4301 | |
| 4302 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for | |
| 4303 example, Lisp code explicitly disabled this by setting | |
| 4304 @code{inhibit-quit}), you can use the "critical quit" mechanism by | |
| 4305 typing @kbd{Control-Shift-G}. This should also pop you into the | |
| 4306 debugger and give you a backtrace, which can tell you where the | |
| 2559 | 4307 problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a |
| 2417 | 4308 debugger}). (Note that setting @code{debug-on-quit} or selecting |
| 4309 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular | |
| 4310 @kbd{C-g} to enter the debugger and give you a backtrace.) | |
| 4311 | |
| 4312 If you can't interrupt XEmacs this way, or for some reason XEmacs is | |
| 4313 not talking to the keyboard, you can try sending the @samp{SIGINT} | |
| 4314 signal using the @samp{kill} command. | |
| 4315 | |
| 4316 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that | |
| 4317 you can't interrupt it at all, you could try attaching to the process | |
| 2559 | 4318 and getting a C stack backtrace. @xref{Q2.4.4, How to debug an XEmacs |
| 2417 | 4319 problem with a debugger}. |
| 4320 | |
| 2559 | 4321 @node Q2.4.7, Q2.4.8, Q2.4.6, Installation |
| 4322 @unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode. | |
| 2417 | 4323 |
| 4324 Typically this happens when you are trying to compile some Elisp code. | |
| 4325 If you are doing this as part of XEmacs or the XEmacs packages, you | |
| 4326 should automatically get a backtrace, which can help you determine the | |
| 4327 source of the problem. In other cases, you can get equivalent results | |
| 4328 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq | |
| 4329 stack-trace-on-error t load-always-display-messages t | |
| 4330 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages | |
| 4331 t)} (this needs to be all on one line; to set an environment variable, | |
| 4332 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh}, | |
| 4333 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and | |
| 4334 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be | |
| 4335 executed at startup time. | |
| 4336 | |
| 4337 If the backtrace is not sufficiently useful in helping you diagnose | |
| 4338 the problem, you should consider using a debugger such as GDB. | |
| 2559 | 4339 @xref{Q2.4.4, How to debug an XEmacs problem with a debugger}. You |
| 2417 | 4340 probably want to set a breakpoint on @code{signal_1}. Since such |
| 4341 errors often occur during compiling, which is often triggered by a | |
| 4342 complex command run from a make suite, it may be easier to attach to | |
| 4343 the process once it's running. | |
| 4344 | |
| 3018 | 4345 Under Microsoft Windows (and perhaps other operating systems), there is |
| 4346 another useful trick you can do if you have configured with debugging | |
| 4347 support (configure option @samp{--debug} (@samp{--with-debug} in 21.5) | |
| 4348 or setting @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the | |
| 4349 environment variable @samp{XEMACSDEBUG} (as described above) to | |
| 4350 @samp{(setq debug-on-error t)}. Then, when an error occurs | |
| 4351 noninteractively, instead of trying to invoke the Lisp debugger (which | |
| 4352 obviously won't work), XEmacs will break out to a C debugger using | |
| 2417 | 4353 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs |
| 4354 @code{abort()}!!! (As well as and after executing INT 3 under MS | |
| 4355 Windows, which should invoke a debugger if it's active.) This is | |
| 4356 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to | |
| 4357 die anyway, and if no debugger is present, this will usefully dump | |
| 4358 core.) | |
| 4359 | |
| 2559 | 4360 @node Q2.4.8, Q2.4.9, Q2.4.7, Installation |
| 4361 @unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 2417 | 4362 |
| 4363 XEmacs has various facilities for debugging event handling. | |
| 4364 | |
| 4365 First, try setting the variable @code{debug-emacs-events} to non-zero. | |
| 4366 This will output various information showing which events are being | |
| 4367 received and how they are being translated. This may show you, for | |
| 4368 example, that a key command is getting intercepted using | |
| 4369 @code{key-translation-map}; this problem can otherwise be very tricky | |
| 4370 to debug. | |
| 4371 | |
| 4372 Under X, you can see exactly which events are being received from the | |
| 4373 window system by setting @code{x-debug-events} to non-zero. (The value | |
| 4374 @samp{1} gives you regular output, and @samp{2} gives you verbose | |
| 4375 output, including all parameters.) | |
| 4376 | |
| 4377 A similar facility exists under MS Windows: Set | |
| 4378 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives | |
| 4379 you regular output. The value @samp{2} gives you verbose output, | |
| 4380 including all parameters. The value @samp{3} gives you | |
| 4381 super-gorily-detailed output.) | |
| 4382 | |
| 2559 | 4383 @node Q2.4.9, Q2.4.10, Q2.4.8, Installation |
| 4384 @unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me. Is it broken? | |
| 2417 | 4385 |
| 4386 @kbd{C-g} does work for most people in most circumstances. If it | |
| 4387 doesn't, there are two possible explanations: | |
| 4388 | |
| 4389 @enumerate | |
| 4390 @item | |
| 4391 XEmacs is hung in a way that prevents @kbd{C-g} from working. This | |
| 4392 can happen when code is wrapped with a binding of @code{inhibit-quit} | |
| 4393 to @code{t}; you should still be able interrupt XEmacs using "critical | |
| 4394 quit". On the other hand, XEmacs may be seriously wedged. (If you're | |
| 4395 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.) | |
| 2559 | 4396 @xref{Q2.4.6, XEmacs hangs when I try to do something.}. |
| 2417 | 4397 |
| 4398 @item | |
| 4399 @kbd{C-g} is indeed broken on your system. To test, try executing | |
| 4400 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g} | |
| 4401 doesn't interrupt, then it's broken. This used to happen with systems | |
| 4402 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined. | |
| 4403 However, there may not be very many such systems nowadays. | |
| 4404 @end enumerate | |
| 4405 | |
| 2559 | 4406 @node Q2.4.10, Q2.4.11, Q2.4.9, Installation |
| 4407 @unnumberedsubsec Q2.4.10: How do I debug process-related problems? | |
| 2417 | 4408 |
| 4409 Under MS Windows, you can set the variable | |
| 4410 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get | |
| 4411 information on exactly what is getting passed to a process. This can | |
| 4412 be useful in determining problems with quoting. (Under Unix, a process | |
| 4413 receives each argument separately, but under MS Windows a single | |
| 4414 command line is received, and arguments with spaces or other special | |
| 4415 characters in them must be quoted. Unfortunately this means that each | |
| 4416 process, potentially at least, has its own quoting conventions, and | |
| 4417 the code to process quoting conventions in @file{cmd.exe}, the Visual | |
| 4418 C++ startup code and the like is baroque and poorly documented. | |
| 4419 XEmacs uses the variable | |
| 4420 @code{mswindows-construct-process-command-line-alist} to construct a | |
| 4421 command line from a list of arguments based on the command to be run, | |
| 4422 but it is (and cannot be) a perfect solution.) | |
| 4423 | |
| 2559 | 4424 @node Q2.4.11, Q2.4.12, Q2.4.10, Installation |
| 4425 @unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors. | |
| 563 | 4426 |
| 4427 If this is happening, we would very much like to know what's causing | |
| 2559 | 4428 them. To find this out, see @ref{Q2.4.4, How to debug an XEmacs |
| 2417 | 4429 problem with a debugger}. Try to get both a C and Lisp backtrace, and |
| 4430 send them along with the full error output to | |
| 4431 @email{xemacs-beta@@xemacs.org}. | |
| 4432 | |
| 2559 | 4433 @node Q2.4.12, Q2.5.1, Q2.4.11, Installation |
| 4434 @unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more! | |
| 2417 | 4435 |
| 4436 You have been used to doing `foo', but now when you invoke it (or | |
| 4437 click the toolbar button or select the menu item), nothing (or an | |
| 4438 error) happens. The simplest explanation is that you are missing a | |
| 4439 package that is essential to you. You can either track it down and | |
| 4440 install it (there is a list of packages and brief descriptions of | |
| 4441 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball' | |
| 2559 | 4442 (@pxref{Q2.1.2, How do I figure out which packages to install?}). |
| 2417 | 4443 |
| 4444 @c #### should xref to XEmacs manual here | |
| 4445 | |
| 2559 | 4446 @unnumberedsec 2.5: Startup-Related Problems |
| 4447 | |
| 4448 @node Q2.5.1, Q2.5.2, Q2.4.12, Installation | |
| 4449 @unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal! | |
| 2417 | 4450 |
| 4451 Help! I can not get XEmacs to display on my Envizex X-terminal! | |
| 4452 | |
| 4453 Try setting the @code{DISPLAY} variable using the numeric IP address of | |
| 4454 the host you are running XEmacs from. | |
| 4455 | |
| 2559 | 4456 @node Q2.5.2, Q2.5.3, Q2.5.1, Installation |
| 4457 @unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations. | |
| 4458 | |
| 4459 First of all, if XEmacs can't find the packages, check to make sure | |
| 4460 that you put the packages in the right place, or that you told XEmacs | |
| 4461 where to look for the packages when you compiled it. @xref{Q2.1.1}. | |
| 4462 | |
| 4463 If something is still going wrong, or you get a startup warning about | |
| 4464 not being able to deduce some paths, you can get detailed information | |
| 4465 on the path-searching process at startup by setting the environment | |
| 4466 variable @samp{EMACSDEBUGPATHS} to a non-null value. One thing to | |
| 4467 look for if you're having package problems is the value of | |
| 4468 @samp{configure-package-path}. This corresponds to what was compiled | |
| 4469 into XEmacs using the @samp{--package-prefix} or @samp{--package-path} | |
| 4470 parameter (@pxref{Q2.1.1}). If this has the value of @samp{nil}, | |
| 4471 this means that no value was compiled into XEmacs using these parameters. | |
| 4472 | |
| 4473 @node Q2.5.3, Q2.5.4, Q2.5.2, Installation | |
| 4474 @unnumberedsubsec Q2.5.3: XEmacs won't start without network. | |
| 434 | 4475 |
| 4476 If XEmacs starts when you're on the network, but fails when you're not | |
| 4477 on the network, you may be missing a "localhost" entry in your | |
| 4478 @file{/etc/hosts} file. The file should contain an entry like: | |
| 4479 | |
| 4480 @example | |
| 4481 127.0.0.1 localhost | |
| 4482 @end example | |
| 4483 | |
| 4484 Add that line, and XEmacs will be happy. | |
| 4485 | |
| 2559 | 4486 @node Q2.5.4, Q2.5.5, Q2.5.3, Installation |
| 4487 @unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts? | |
| 2417 | 4488 |
| 4489 How can I avoid the startup warnings about deducing proper fonts? | |
| 4490 | |
| 4491 This is highly dependent on your installation, but try with the | |
| 4492 following font as your base font for XEmacs and see what it does: | |
| 4493 | |
| 4494 @format | |
| 4495 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
| 4496 @end format | |
| 4497 | |
| 4498 More precisely, do the following in your resource file: | |
| 4499 | |
| 4500 @format | |
| 4501 Emacs.default.attributeFont: \ | |
| 4502 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
| 4503 @end format | |
| 4504 | |
| 4505 If you just don't want to see the @samp{*Warnings*} buffer at startup | |
| 4506 time, you can set this: | |
| 428 | 4507 |
| 4508 @lisp | |
| 2417 | 4509 (setq display-warning-minimum-level 'error) |
| 428 | 4510 @end lisp |
| 4511 | |
| 2417 | 4512 The buffer still exists; it just isn't in your face. |
| 4513 | |
| 2559 | 4514 @node Q2.5.5, Q2.5.6, Q2.5.4, Installation |
| 4515 @unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers. | |
| 2417 | 4516 |
| 4517 The following information comes from the @file{PROBLEMS} file that comes | |
| 4518 with XEmacs. | |
| 4519 | |
| 4520 If you're having troubles with HP/UX it is because HP/UX defines the | |
| 4521 modifiers wrong in X. Here is a shell script to fix the problem; be | |
| 4522 sure that it is run after VUE configures the X server. | |
| 428 | 4523 |
| 4524 @example | |
| 2417 | 4525 #! /bin/sh |
| 4526 xmodmap 2> /dev/null - << EOF | |
| 4527 keysym Alt_L = Meta_L | |
| 4528 keysym Alt_R = Meta_R | |
| 4529 EOF | |
| 4530 | |
| 4531 xmodmap - << EOF | |
| 4532 clear mod1 | |
| 4533 keysym Mode_switch = NoSymbol | |
| 4534 add mod1 = Meta_L | |
| 4535 keysym Meta_R = Mode_switch | |
| 4536 add mod2 = Mode_switch | |
| 4537 EOF | |
| 428 | 4538 @end example |
| 4539 | |
| 2559 | 4540 @node Q2.5.6, , Q2.5.5, Installation |
| 4541 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? | |
| 2417 | 4542 |
| 4543 Yes. | |
| 4544 | |
| 4545 The console was there because @file{temacs} (and in turn, @file{xemacs}) | |
| 4546 was a console application, and Windows typically creates a new | |
| 4547 console for a console process unless the creating process requests that | |
| 4548 one isn't created. This used to be fixed with @file{runemacs}, a small | |
| 4549 Windows application that existed merely to start @file{xemacs}, stating | |
| 4550 that it didn't want a console. | |
| 4551 | |
| 4552 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI" | |
| 4553 application. The explanation of what that means is included for | |
| 4554 educational value. | |
| 4555 | |
| 4556 When building an application to be run in a Win32 environment, you must | |
| 4557 state which sub-system it is to run in. Valid subsystems include | |
| 4558 "console" and "gui". The subsystem you use affects the run time | |
| 4559 libraries linked into your application, the start up function that is | |
| 4560 run before control is handed over to your application, the entry point | |
| 4561 to your program, and how Windows normally invokes your program. (Console | |
| 4562 programs automatically get a console created for them at startup if | |
| 4563 their stdin/stdout don't point anywhere useful, which is the case when | |
| 4564 run from the GUI. This is a stupid design, of course -- instead, the | |
| 4565 console should get created only when the first I/O actually occurs! | |
| 4566 GUI programs have an equally stupid design: When called from | |
| 4567 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to | |
| 4568 point nowhere useful, even though the command shell has its own | |
| 4569 stdin/stdout. It's as if someone who had learned a bit about stdio but | |
| 4570 had no actual knowledge of interprocess communication designed the | |
| 4571 scheme; unfortunately, the whole process-communication aspect of the | |
| 4572 Win32 API is equally badly designed.) For example, the entry point for a | |
| 4573 console app is "main" (which is what you'd expect for a C/C++ program), | |
| 4574 but the entry point for a "gui" app is "WinMain". This confuses and | |
| 4575 annoys a lot of programmers who've grown up on Unix systems, where the | |
| 4576 kernel doesn't really care whether your application is a gui program or | |
| 4577 not. | |
| 4578 | |
| 4579 For reasons not altogether clear, and are lost in the mists of time and | |
| 4580 tradition, XEmacs on Win32 started out as a console application, and | |
| 4581 therefore a console was automatically created for it. (It may have been | |
| 4582 made a console application partly because a console is needed in some | |
| 4583 circumstances, especially under Win95, to interrupt, terminate, or send | |
| 4584 signals to a child process, and because of the bogosity mentioned above | |
| 4585 with GUI programs and the standard command shell. Currently, XEmacs | |
| 4586 just creates and immediately hides a console when necessary, and | |
| 4587 works around the "no useful stdio" problem by creating its own console | |
| 4588 window as necessary to display messages in.) | |
| 4589 | |
| 2459 | 4590 @node Editing, Display, Installation, Top |
| 4591 @unnumbered 3 Editing Functions | |
| 2417 | 4592 |
| 4593 This is part 3 of the XEmacs Frequently Asked Questions list. This | |
| 2459 | 4594 section is devoted to the editing-related capabilities of XEmacs (the |
| 4595 keyboard, mouse, buffers, text selections, etc.) and how to customize | |
| 4596 them. | |
| 2417 | 4597 |
| 4598 @menu | |
| 4599 3.0: The Keyboard | |
| 2459 | 4600 * Q3.0.1:: How can I customize the keyboard? |
| 4601 * Q3.0.2:: How can I bind complex functions (or macros) to keys? | |
| 4602 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down? | |
| 4603 * Q3.0.4:: Globally binding @kbd{Delete}? | |
| 4604 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 4605 * Q3.0.6:: How can you type in special characters in XEmacs? | |
| 4606 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys? | |
| 4607 * Q3.0.8:: How do I map the arrow keys? | |
| 4608 * Q3.0.9:: HP Alt key as Meta. | |
| 4609 * Q3.0.10:: Why does edt emulation not work? | |
| 4610 * Q3.0.11:: How can I emulate VI and use it as my default mode? | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4611 * Q3.0.12:: Mac Alt/Option key as Meta. |
| 2417 | 4612 |
| 4613 3.1: The Mouse | |
| 4614 * Q3.1.1:: How can I turn off Mouse pasting? | |
| 4615 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons? | |
| 4616 * Q3.1.3:: Clicking the left button does not do anything in buffer list. | |
| 4617 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3? | |
| 2459 | 4618 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is? |
| 4619 | |
| 4620 3.2: Buffers, Text Editing | |
| 4621 * Q3.2.1:: Can I have the end of the buffer delimited in some way? | |
| 4622 * Q3.2.2:: How do I insert today's date into a buffer? | |
| 4623 * Q3.2.3:: How do I get a single minibuffer frame? | |
| 4624 * Q3.2.4:: How can I enable auto-indent and/or Filladapt? | |
| 4625 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 4626 | |
| 4627 3.3: Text Selections | |
| 4628 * Q3.3.1:: How do I select a rectangular region? | |
| 4629 * Q3.3.2:: How can I turn off or change highlighted selections? | |
| 4630 * Q3.3.3:: How do I cause typing on an active region to remove it? | |
| 4631 * Q3.3.4:: Can I turn off the highlight during isearch? | |
| 4632 * Q3.3.5:: Why is killing so slow? | |
| 4633 * Q3.3.6:: Why does @kbd{M-w} take so long? | |
| 4634 | |
| 4635 3.4: Editing Source Code | |
| 4636 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode? | |
| 4637 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly? | |
| 2417 | 4638 @end menu |
| 4639 | |
| 4640 @unnumberedsec 3.0: The Keyboard | |
| 4641 | |
| 2459 | 4642 @node Q3.0.1, Q3.0.2, Editing, Editing |
| 4643 @unnumberedsubsec Q3.0.1: How can I customize the keyboard? | |
| 4644 | |
| 4645 #### Write me. | |
| 4646 | |
| 4647 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing | |
| 4648 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys? | |
| 428 | 4649 |
| 4650 As an example, say you want the @kbd{paste} key on a Sun keyboard to | |
| 4651 insert the current Primary X selection at point. You can accomplish this | |
| 4652 with: | |
| 4653 | |
| 4654 @lisp | |
| 4655 (define-key global-map [f18] 'x-insert-selection) | |
| 4656 @end lisp | |
| 4657 | |
| 4658 However, this only works if there is a current X selection (the | |
| 4659 selection will be highlighted). The functionality I like is for the | |
| 4660 @kbd{paste} key to insert the current X selection if there is one, | |
| 4661 otherwise insert the contents of the clipboard. To do this you need to | |
| 4662 pass arguments to @code{x-insert-selection}. This is done by wrapping | |
| 4663 the call in a 'lambda form: | |
| 4664 | |
| 4665 @lisp | |
| 4666 (global-set-key [f18] | |
| 4667 (lambda () (interactive) (x-insert-selection t nil))) | |
| 4668 @end lisp | |
| 4669 | |
| 4670 This binds the f18 key to a @dfn{generic} functional object. The | |
| 4671 interactive spec is required because only interactive functions can be | |
| 4672 bound to keys. | |
| 4673 | |
| 4674 For the FAQ example you could use: | |
| 4675 | |
| 4676 @lisp | |
| 4677 (global-set-key [(control ?.)] | |
| 4678 (lambda () (interactive) (scroll-up 1))) | |
| 440 | 4679 (global-set-key [(control ?;)] |
| 4680 (lambda () (interactive) (scroll-up -1))) | |
| 428 | 4681 @end lisp |
| 4682 | |
| 4683 This is fine if you only need a few functions within the lambda body. | |
| 2417 | 4684 If you're doing more it's cleaner to define a separate function. |
| 2459 | 4685 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and |
| 2417 | 4686 down?}. |
| 4687 | |
| 2459 | 4688 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing |
| 4689 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down? | |
| 428 | 4690 |
| 4691 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and | |
| 4692 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}: | |
| 4693 | |
| 4694 @lisp | |
| 4695 (defun scroll-up-one-line () | |
| 4696 (interactive) | |
| 4697 (scroll-up 1)) | |
| 4698 | |
| 4699 (defun scroll-down-one-line () | |
| 4700 (interactive) | |
| 4701 (scroll-down 1)) | |
| 4702 | |
| 4703 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-. | |
| 440 | 4704 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-; |
| 428 | 4705 @end lisp |
| 4706 | |
| 4707 The key point is that you can only bind simple functions to keys; you | |
| 2417 | 4708 can not bind a key to a function that you're also passing arguments |
| 2459 | 4709 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to |
| 2417 | 4710 keys?} for a better answer). |
| 4711 | |
| 2459 | 4712 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing |
| 4713 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}? | |
| 428 | 4714 |
| 4715 I cannot manage to globally bind my @kbd{Delete} key to something other | |
| 4716 than the default. How does one do this? | |
| 4717 | |
| 462 | 4718 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To |
| 4719 get around this, try the following: | |
| 4720 | |
| 428 | 4721 @lisp |
| 4722 (defun foo () | |
| 4723 (interactive) | |
| 4724 (message "You hit DELETE")) | |
| 4725 | |
| 462 | 4726 (define-key key-translation-map 'delete 'redirected-delete) |
| 4727 (global-set-key 'redirected-delete 'foo) | |
| 428 | 4728 @end lisp |
| 4729 | |
| 2459 | 4730 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing |
| 4731 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 428 | 4732 |
| 4733 The following works in GNU Emacs 19: | |
| 4734 | |
| 4735 @lisp | |
| 4736 (global-set-key [help] 'help-command);; Help | |
| 4737 @end lisp | |
| 4738 | |
| 462 | 4739 The following works in XEmacs with the addition of shift: |
| 428 | 4740 |
| 4741 @lisp | |
| 4742 (global-set-key [(shift help)] 'help-command);; Help | |
| 4743 @end lisp | |
| 4744 | |
| 4745 But it doesn't work alone. This is in the file @file{PROBLEMS} which | |
| 4746 should have come with your XEmacs installation: @emph{Emacs ignores the | |
| 4747 @kbd{help} key when running OLWM}. | |
| 4748 | |
| 4749 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate | |
| 4750 client using | |
| 4751 @iftex | |
| 4752 @* | |
| 4753 @end iftex | |
| 4754 @code{XSendEvent}. Allowing Emacs to react to synthetic | |
| 4755 events is a security hole, so this is turned off by default. You can | |
| 4756 enable it by setting the variable @code{x-allow-sendevents} to t. You | |
| 4757 can also cause fix this by telling OLWM to not grab the help key, with | |
| 4758 the null binding @code{OpenWindows.KeyboardCommand.Help:}. | |
| 4759 | |
| 2459 | 4760 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing |
| 4761 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs? | |
| 428 | 4762 One way is to use the package @code{x-compose}. Then you can use |
| 4763 sequences like @kbd{Compose " a} to get ä, etc. | |
| 4764 | |
| 462 | 4765 Another way is to use the @code{iso-insert} package. Then you can use |
| 4766 sequences like @kbd{C-x 8 " a} to get ä, etc. | |
| 428 | 4767 |
| 4768 @email{glynn@@sensei.co.uk, Glynn Clements} writes: | |
| 4769 | |
| 4770 @quotation | |
| 4771 It depends upon your X server. | |
| 4772 | |
| 4773 Generally, the simplest way is to define a key as Multi_key with | |
| 4774 xmodmap, e.g. | |
| 4775 @c hey, show some respect, willya -- there's xkeycaps, isn't there? -- | |
| 4776 @c chr ;) | |
| 4777 @example | |
| 440 | 4778 xmodmap -e 'keycode 0xff20 = Multi_key' |
| 428 | 4779 @end example |
| 4780 | |
| 4781 You will need to pick an appropriate keycode. Use xev to find out the | |
| 4782 keycodes for each key. | |
| 4783 | |
| 4784 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically | |
| 4785 define the right `Windows' key as Multi_key'.] | |
| 4786 | |
| 4787 Once you have Multi_key defined, you can use e.g. | |
| 4788 @example | |
| 440 | 4789 Multi a ' => á |
| 4790 Multi e " => ë | |
| 4791 Multi c , => ç | |
| 428 | 4792 @end example |
| 4793 | |
| 4794 etc. | |
| 4795 | |
| 4796 Also, recent versions of XFree86 define various AltGr-<key> | |
| 4797 combinations as dead keys, i.e. | |
| 4798 @example | |
| 440 | 4799 AltGr [ => dead_diaeresis |
| 4800 AltGr ] => dead_tilde | |
| 4801 AltGr ; => dead_acute | |
| 428 | 4802 @end example |
| 4803 etc. | |
| 4804 | |
| 4805 Running @samp{xmodmap -pk} will list all of the defined keysyms. | |
| 4806 @end quotation | |
| 4807 | |
| 1135 | 4808 For the related problem of @emph{displaying} non-ASCII characters in a |
| 2459 | 4809 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}. |
| 4810 | |
| 4811 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing | |
| 4812 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys? | |
| 428 | 4813 |
| 4814 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the | |
| 4815 effect of being able to press and release Shift and have the next | |
| 4816 character typed come out in upper case. This will affect all the other | |
| 4817 modifier keys like Control and Meta as well. | |
| 4818 | |
| 4819 @email{ben@@xemacs.org, Ben Wing} writes: | |
| 4820 | |
| 4821 @quotation | |
| 4822 One thing about the sticky modifiers is that if you move the mouse out | |
| 4823 of the frame and back in, it cancels all currently ``stuck'' modifiers. | |
| 4824 @end quotation | |
| 4825 | |
| 2459 | 4826 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing |
| 4827 @unnumberedsubsec Q3.0.8: How do I map the arrow keys? | |
| 428 | 4828 @c New |
| 4829 Say you want to map @kbd{C-@key{right}} to forward-word: | |
| 4830 | |
| 4831 @email{sds@@usa.net, Sam Steingold} writes: | |
| 4832 | |
| 4833 @quotation | |
| 4834 @lisp | |
| 4835 ; both XEmacs and Emacs | |
| 4836 (define-key global-map [(control right)] 'forward-word) | |
| 4837 @end lisp | |
| 4838 or | |
| 4839 @lisp | |
| 4840 ; Emacs only | |
| 4841 (define-key global-map [C-right] 'forward-word) | |
| 4842 @end lisp | |
| 4843 or | |
| 4844 @lisp | |
| 4845 ; ver > 20, both | |
| 4846 (define-key global-map (kbd "C-<right>") 'forward-word) | |
| 4847 @end lisp | |
| 4848 @end quotation | |
| 4849 | |
| 2459 | 4850 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing |
| 4851 @unnumberedsubsec Q3.0.9: HP Alt key as Meta. | |
| 2417 | 4852 |
| 4853 How can I make XEmacs recognize the Alt key of my HP workstation as a | |
| 4854 Meta key? | |
| 4855 | |
| 4856 Put the following line into a file and load it with xmodmap(1) before | |
| 4857 starting XEmacs: | |
| 428 | 4858 |
| 4859 @example | |
| 2417 | 4860 remove Mod1 = Mode_switch |
| 428 | 4861 @end example |
| 4862 | |
| 2459 | 4863 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing |
| 4864 @unnumberedsubsec Q3.0.10: Why does edt emulation not work? | |
| 2417 | 4865 |
| 4866 We don't know, but you can use tpu-edt emulation instead, which works | |
| 4867 fine and is a little fancier than the standard edt emulation. To do | |
| 4868 this, add the following line to your @file{init.el}: | |
| 4869 | |
| 4870 @lisp | |
| 4871 (tpu-edt) | |
| 4872 @end lisp | |
| 4873 | |
| 4874 If you don't want it to replace @kbd{C-h} with an edt-style help menu | |
| 4875 add this as well: | |
| 428 | 4876 |
| 4877 @lisp | |
| 2417 | 4878 (global-set-key [(control h)] 'help-for-help) |
| 428 | 4879 @end lisp |
| 4880 | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4881 @node Q3.0.11, Q3.0.12, Q3.0.10, Editing |
| 2459 | 4882 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode? |
| 2417 | 4883 |
| 4884 Our recommended VI emulator is viper. To make viper-mode the default, | |
| 4885 add this to your @file{init.el}: | |
| 428 | 4886 |
| 4887 @lisp | |
| 2417 | 4888 (viper-mode) |
| 428 | 4889 @end lisp |
| 4890 | |
| 2417 | 4891 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes: |
| 4892 | |
| 4893 @quotation | |
| 4894 This should be added as close to the top of @file{init.el} as you can get | |
| 4895 it, otherwise some minor modes may not get viper-ized. | |
| 4896 @end quotation | |
| 4897 | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4898 @node Q3.0.12, Q3.1.1, Q3.0.11, Editing |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4899 @unnumberedsubsec Q3.0.12: Mac Alt/Option key as Meta. |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4900 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4901 Due to the Apple Command key being Meta, I can't use XEmacs on OS X. |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4902 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4903 Didier Verna suggests: |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4904 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4905 I use an X version of XEmacs on a Mac every day. You have to tweak the |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4906 keyboard configuration a bit but that's all. |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4907 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4908 Here's my Xmodmap file on Darwin: |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4909 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4910 @example |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4911 clear mod1 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4912 clear mod2 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4913 keycode 66 = Meta_L |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4914 keycode 63 = Mode_switch |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4915 add mod1 = Meta_L |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4916 @end example |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4917 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4918 This leaves the command key alone and uses alt/option for Meta. |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4919 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4920 |
| 2417 | 4921 @unnumberedsec 3.1: The Mouse |
| 4922 | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4923 @node Q3.1.1, Q3.1.2, Q3.0.12, Editing |
| 2417 | 4924 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting? |
| 428 | 4925 |
| 4926 I keep hitting the middle mouse button by accident and getting stuff | |
| 4927 pasted into my buffer so how can I turn this off? | |
| 4928 | |
| 4929 Here is an alternative binding, whereby the middle mouse button selects | |
| 4930 (but does not cut) the expression under the mouse. Clicking middle on a | |
| 4931 left or right paren will select to the matching one. Note that you can | |
| 4932 use @code{define-key} or @code{global-set-key}. | |
| 4933 | |
| 4934 @lisp | |
| 4935 (defun mouse-set-point-and-select (event) | |
| 4936 "Sets the point at the mouse location, then marks following form" | |
| 4937 (interactive "@@e") | |
| 4938 (mouse-set-point event) | |
| 4939 (mark-sexp 1)) | |
| 4940 (define-key global-map [button2] 'mouse-set-point-and-select) | |
| 4941 @end lisp | |
| 4942 | |
| 2459 | 4943 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing |
| 2417 | 4944 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons? |
| 428 | 4945 |
| 4946 Use, for instance, @code{[(meta button1)]}. For example, here is a common | |
| 4947 setting for Common Lisp programmers who use the bundled @code{ilisp} | |
| 4948 package, whereby meta-button1 on a function name will find the file where | |
| 4949 the function name was defined, and put you at that location in the source | |
| 4950 file. | |
| 4951 | |
| 4952 [Inside a function that gets called by the lisp-mode-hook and | |
| 4953 ilisp-mode-hook] | |
| 4954 | |
| 4955 @lisp | |
| 4956 (local-set-key [(meta button1)] 'edit-definitions-lisp) | |
| 4957 @end lisp | |
| 4958 | |
| 2459 | 4959 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing |
| 2417 | 4960 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list. |
| 428 | 4961 |
| 4962 I do @kbd{C-x C-b} to get a list of buffers and the entries get | |
| 4963 highlighted when I move the mouse over them but clicking the left mouse | |
| 4964 does not do anything. | |
| 4965 | |
| 4966 Use the middle mouse button. | |
| 4967 | |
| 2459 | 4968 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing |
| 2417 | 4969 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3? |
| 428 | 4970 |
| 4971 The following code will replace the default popup on button3: | |
| 4972 | |
| 4973 @lisp | |
| 4974 (global-set-key [button3] 'popup-buffer-menu) | |
| 4975 @end lisp | |
| 4976 | |
| 2459 | 4977 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing |
| 4978 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is? | |
| 428 | 4979 |
| 4980 By default XEmacs pastes X selections where the mouse pointer is. How | |
| 4981 do I disable this? | |
| 4982 | |
| 4983 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank | |
| 4984 @key{RET}}. | |
| 4985 | |
| 2417 | 4986 To get XEmacs to paste at the text cursor, add this your @file{init.el}: |
| 428 | 4987 |
| 4988 @lisp | |
| 4989 (setq mouse-yank-at-point t) | |
| 4990 @end lisp | |
| 4991 | |
| 2459 | 4992 You can also change this with Customize. Select from the |
| 4993 @code{Options} menu @code{Advanced | |
| 4994 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x | |
| 4995 customize @key{RET} mouse @key{RET}}. | |
| 4996 | |
| 4997 @unnumberedsec 3.2: Buffers, Text Editing | |
| 4998 | |
| 4999 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing | |
| 5000 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way? | |
| 5001 | |
| 5002 Say, with: @samp{[END]}? | |
| 5003 | |
| 5004 Try this: | |
| 5005 | |
| 5006 @lisp | |
| 5007 (let ((ext (make-extent (point-min) (point-max)))) | |
| 5008 (set-extent-property ext 'start-closed t) | |
| 5009 (set-extent-property ext 'end-closed t) | |
| 5010 (set-extent-property ext 'detachable nil) | |
| 5011 (set-extent-end-glyph ext (make-glyph [string :data "[END]"]))) | |
| 5012 @end lisp | |
| 5013 | |
| 5014 Since this is XEmacs, you can specify an icon to be shown on | |
| 5015 window-system devices. To do so, change the @code{make-glyph} call to | |
| 5016 something like this: | |
| 5017 | |
| 5018 @lisp | |
| 5019 (make-glyph '([xpm :file "~/something.xpm"] | |
| 5020 [string :data "[END]"])) | |
| 5021 @end lisp | |
| 5022 | |
| 5023 You can inline the @sc{xpm} definition yourself by specifying | |
| 5024 @code{:data} instead of @code{:file}. Here is such a full-featured | |
| 5025 version that works on both X and TTY devices: | |
| 5026 | |
| 5027 @lisp | |
| 5028 (let ((ext (make-extent (point-min) (point-max)))) | |
| 5029 (set-extent-property ext 'start-closed t) | |
| 5030 (set-extent-property ext 'end-closed t) | |
| 5031 (set-extent-property ext 'detachable nil) | |
| 5032 (set-extent-end-glyph ext (make-glyph '([xpm :data "\ | |
| 5033 /* XPM */ | |
| 5034 static char* eye = @{ | |
| 5035 \"20 11 7 2\", | |
| 5036 \"__ c None\" | |
| 5037 \"_` c #7f7f7f\", | |
| 5038 \"_a c #fefefe\", | |
| 5039 \"_b c #7f0000\", | |
| 5040 \"_c c #fefe00\", | |
| 5041 \"_d c #fe0000\", | |
| 5042 \"_e c #bfbfbf\", | |
| 5043 \"___________`_`_`___b_b_b_b_________`____\", | |
| 5044 \"_________`_`_`___b_c_c_c_b_b____________\", | |
| 5045 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\", | |
| 5046 \"___`_`_e_a___b_b_d___b___b___b___b______\", | |
| 5047 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\", | |
| 5048 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\", | |
| 5049 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\", | |
| 5050 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\", | |
| 5051 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\", | |
| 5052 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\", | |
| 5053 \"___`_____`_`_`_`___b_b_b_b_b_b__________\", | |
| 5054 @} ;"] | |
| 5055 [string :data "[END]"])))) | |
| 5056 @end lisp | |
| 5057 | |
| 5058 Note that you might want to make this a function, and put it to a hook. | |
| 5059 We leave that as an exercise for the reader. | |
| 5060 | |
| 5061 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing | |
| 5062 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer? | |
| 2417 | 5063 |
| 5064 Like this: | |
| 428 | 5065 |
| 5066 @lisp | |
| 2459 | 5067 (insert (current-time-string)) |
| 2417 | 5068 @end lisp |
| 5069 | |
| 2459 | 5070 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing |
| 5071 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame? | |
| 5072 | |
| 5073 @email{acs@@acm.org, Vin Shelton} writes: | |
| 2417 | 5074 |
| 5075 @lisp | |
| 2459 | 5076 (setq initial-frame-plist '(minibuffer nil)) |
| 5077 (setq default-frame-plist '(minibuffer nil)) | |
| 5078 (setq default-minibuffer-frame | |
| 5079 (make-frame | |
| 5080 '(minibuffer only | |
| 5081 width 86 | |
| 5082 height 1 | |
| 5083 menubar-visible-p nil | |
| 5084 default-toolbar-visible-p nil | |
| 5085 name "minibuffer" | |
| 5086 top -2 | |
| 5087 left -2 | |
| 5088 has-modeline-p nil))) | |
| 5089 (frame-notice-user-settings) | |
| 2417 | 5090 @end lisp |
| 5091 | |
| 2459 | 5092 @strong{Please note:} The single minibuffer frame may not be to everyone's |
| 5093 taste, and there any number of other XEmacs options settings that may | |
| 5094 make it difficult or inconvenient to use. | |
| 5095 | |
| 5096 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing | |
| 5097 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt? | |
| 5098 | |
| 5099 Put the following line in your @file{init.el}: | |
| 428 | 5100 |
| 5101 @lisp | |
| 2459 | 5102 (setq indent-line-function 'indent-relative-maybe) |
| 428 | 5103 @end lisp |
| 5104 | |
| 2459 | 5105 If you want to get fancy, try the @code{filladapt} package available |
| 5106 standard with XEmacs. Put this into your @file{init.el}: | |
| 428 | 5107 |
| 5108 @lisp | |
| 2459 | 5109 (require 'filladapt) |
| 5110 (setq-default filladapt-mode t) | |
| 5111 (add-hook 'c-mode-hook 'turn-off-filladapt-mode) | |
| 428 | 5112 @end lisp |
| 5113 | |
| 2459 | 5114 This will enable Filladapt for all modes except C mode, where it doesn't |
| 5115 work well. To turn Filladapt on only in particular major modes, remove | |
| 5116 the @code{(setq-default ...)} line and use | |
| 5117 @code{turn-on-filladapt-mode}, like this: | |
| 428 | 5118 |
| 5119 @lisp | |
| 2459 | 5120 (add-hook 'text-mode-hook 'turn-on-filladapt-mode) |
| 428 | 5121 @end lisp |
| 2417 | 5122 |
| 2459 | 5123 You can customize filling and adaptive filling with Customize. |
| 5124 Select from the @code{Options} menu | |
| 5125 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...} | |
| 5126 or type @kbd{M-x customize @key{RET} fill @key{RET}}. | |
| 5127 | |
| 5128 Note that well-behaving text-lookalike modes will run | |
| 5129 @code{text-mode-hook} by default (e.g. that's what Message does). For | |
| 5130 the nasty ones, you'll have to provide the @code{add-hook}s yourself. | |
| 5131 | |
| 5132 Please note that the @code{fa-extras} package is no longer useful. | |
| 5133 | |
| 5134 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing | |
| 5135 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 5136 | |
| 5137 Try the following lisp in your @file{init.el}: | |
| 2417 | 5138 |
| 5139 @lisp | |
| 2459 | 5140 (setq default-major-mode 'text-mode) |
| 2769 | 5141 (add-hook 'text-mode-hook 'turn-on-auto-fill) |
| 2417 | 5142 @end lisp |
| 5143 | |
| 2459 | 5144 @strong{WARNING}: note that changing the value of |
| 5145 @code{default-major-mode} from @code{fundamental-mode} can break a large | |
| 5146 amount of built-in code that expects newly created buffers to be in | |
| 5147 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to | |
| 5148 @code{text-mode} might not wreak too much havoc, but changing to | |
| 5149 something more exotic like a lisp-mode would break many Emacs packages). | |
| 5150 | |
| 5151 Note that Emacs by default starts up in buffer @code{*scratch*} in | |
| 5152 @code{initial-major-mode}, which defaults to | |
| 5153 @code{lisp-interaction-mode}. Thus adding the following form to your | |
| 5154 Emacs init file will cause the initial @code{*scratch*} buffer to be put | |
| 5155 into auto-fill'ed @code{text-mode}: | |
| 2417 | 5156 |
| 5157 @lisp | |
| 2459 | 5158 (setq initial-major-mode |
| 5159 (lambda () | |
| 5160 (text-mode) | |
| 5161 (turn-on-auto-fill))) | |
| 2417 | 5162 @end lisp |
| 5163 | |
| 2459 | 5164 Note that after your init file is loaded, if |
| 5165 @code{inhibit-startup-message} is @code{nil} (the default) and the | |
| 5166 startup buffer is @code{*scratch*} then the startup message will be | |
| 5167 inserted into @code{*scratch*}; it will be removed after a timeout by | |
| 5168 erasing the entire @code{*scratch*} buffer. Keep in mind this default | |
| 5169 usage of @code{*scratch*} if you desire any prior manipulation of | |
| 5170 @code{*scratch*} from within your Emacs init file. In particular, | |
| 5171 anything you insert into @code{*scratch*} from your init file will be | |
| 5172 later erased. Also, if you change the mode of the @code{*scratch*} | |
| 5173 buffer, be sure that this will not interfere with possible later | |
| 5174 insertion of the startup message (e.g. if you put @code{*scratch*} into | |
| 5175 a nonstandard mode that has automatic font lock rules, then the startup | |
| 5176 message might get fontified in a strange foreign manner, e.g. as code in | |
| 5177 some programming language). | |
| 5178 | |
| 5179 @unnumberedsec 3.3: Text Selections | |
| 5180 | |
| 5181 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing | |
| 5182 @unnumberedsubsec Q3.3.1: How do I select a rectangular region? | |
| 2417 | 5183 |
| 5184 Just select the region normally, then use the rectangle commands (e.g. | |
| 5185 @code{kill-rectangle} on it. The region does not highlight as a | |
| 5186 rectangle, but the commands work just fine. | |
| 5187 | |
| 5188 To actually sweep out rectangular regions with the mouse you can use | |
| 5189 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}. | |
| 5190 Then use rectangle commands. | |
| 5191 | |
| 5192 You can also do the following to change default behavior to sweep out | |
| 5193 rectangular regions: | |
| 5194 | |
| 5195 @lisp | |
| 5196 (setq mouse-track-rectangle-p t) | |
| 5197 @end lisp | |
| 5198 | |
| 2459 | 5199 You can also change this with Customize. |
| 2417 | 5200 Select from the @code{Options} menu |
| 5201 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type | |
| 5202 @kbd{M-x customize @key{RET} mouse @key{RET}}. | |
| 5203 | |
| 5204 | |
| 5205 @example | |
| 5206 mouse-track-do-rectangle: (event) | |
| 5207 -- an interactive compiled Lisp function. | |
| 5208 Like `mouse-track' but selects rectangles instead of regions. | |
| 5209 @end example | |
| 5210 | |
| 2459 | 5211 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing |
| 5212 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections? | |
| 428 | 5213 |
| 5214 The @code{zmacs} mode allows for what some might call gratuitous | |
| 5215 highlighting for selected regions (either by setting mark or by using | |
| 5216 the mouse). This is the default behavior. To turn off, add the | |
| 2417 | 5217 following line to your @file{init.el} file: |
| 428 | 5218 |
| 5219 @lisp | |
| 5220 (setq zmacs-regions nil) | |
| 5221 @end lisp | |
| 5222 | |
| 2417 | 5223 You can also change this with Customize. Select from the |
| 5224 @code{Options} menu | |
| 5225 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions} | |
| 5226 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}. | |
| 5227 | |
| 5228 To change the face for selection, look at @code{Options->Advanced (Customize)} | |
| 5229 on the menubar. | |
| 5230 | |
| 2459 | 5231 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing |
| 5232 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it? | |
| 428 | 5233 |
| 5234 I want to change things so that if I select some text and start typing, | |
| 5235 the typed text replaces the selected text, similar to Motif. | |
| 5236 | |
| 5237 You want to use something called @dfn{pending delete}. Pending delete | |
| 5238 is what happens when you select a region (with the mouse or keyboard) | |
| 5239 and you press a key to replace the selected region by the key you typed. | |
| 5240 Usually backspace kills the selected region. | |
| 5241 | |
| 2164 | 5242 To get this behavior, ensure that you have the @file{pc} package |
| 5243 installed, and add the following lines to your | |
| 2417 | 5244 @file{init.el}: |
| 428 | 5245 |
| 5246 @lisp | |
| 438 | 5247 (cond |
| 5248 ((fboundp 'turn-on-pending-delete) | |
| 5249 (turn-on-pending-delete)) | |
| 5250 ((fboundp 'pending-delete-on) | |
| 5251 (pending-delete-on t))) | |
| 428 | 5252 @end lisp |
| 5253 | |
| 1138 | 5254 Note that this will work with both Backspace and Delete. This code is a |
| 438 | 5255 tad more complicated than it has to be for XEmacs in order to make it |
| 5256 more portable. | |
| 428 | 5257 |
| 2459 | 5258 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing |
| 5259 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch? | |
| 428 | 5260 |
| 5261 I do not like my text highlighted while I am doing isearch as I am not | |
| 5262 able to see what's underneath. How do I turn it off? | |
| 5263 | |
| 2417 | 5264 Put the following in your @file{init.el}: |
| 428 | 5265 |
| 5266 @lisp | |
| 5267 (setq isearch-highlight nil) | |
| 5268 @end lisp | |
| 5269 | |
| 2459 | 5270 You can also change this with Customize. Type |
| 428 | 5271 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}. |
| 5272 | |
| 5273 Note also that isearch-highlight affects query-replace and ispell. | |
| 5274 Instead of disabling isearch-highlight you may find that a better | |
| 5275 solution consists of customizing the @code{isearch} face. | |
| 5276 | |
| 2459 | 5277 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing |
| 5278 @unnumberedsubsec Q3.3.5: Why is killing so slow? | |
| 892 | 5279 |
| 5280 This actually is an X Windows question, although you'll notice it with | |
| 5281 keyboard operations as well as while using the GUI. Basically, there | |
| 5282 are four ways to communicate interprogram via the X server: | |
| 5283 | |
| 5284 @table @strong | |
| 5285 @item Primary selection | |
| 5286 a transient selection that gets replaced every time a new selection is made | |
| 5287 | |
| 5288 @item Secondary selection | |
| 5289 for "exchanging" with the primary selection | |
| 5290 | |
| 5291 @item Cut buffers | |
| 5292 a clipboard internal to the X server (deprecated) | |
| 5293 | |
| 5294 @item Clipboard selection | |
| 5295 a selection with a notification protocol that allows a separate app to | |
| 5296 manage the clipboard | |
| 5297 @end table | |
| 5298 | |
| 5299 The cut buffers are deprecated because managing them is even more | |
| 5300 inefficient than the clipboard notification protocol. The primary | |
| 5301 selection works fine for many users and applications, but is not very | |
| 5302 robust under intensive or sophisticated use. | |
| 5303 | |
| 5304 In Motif and MS Windows, a clipboard has become the primary means for | |
| 5305 managing cut and paste. These means that "modern" applications tend to | |
| 5306 be oriented toward a true clipboard, rather than the primary selection. | |
| 5307 (On Windows, there is nothing equivalent to the primary selection.) | |
| 5308 It's not that XEmacs doesn't support the simple primary selection | |
| 5309 method, it's that more and more other applications don't. | |
| 5310 | |
| 5311 So the slowdown occurs because XEmacs now engages in the clipboard | |
| 5312 notification protocol on @emph{every} kill. This is especially slow on | |
| 5313 Motif. | |
| 5314 | |
| 5315 With most people running most clients and server on the same host, and | |
| 5316 many of the rest working over very fast communication, you may expect | |
| 5317 that the situation is not going to improve. | |
| 5318 | |
| 5319 There are a number of workarounds. The most effective is to use a | |
| 5320 special command to do selection ownership only when you intend to paste | |
| 5321 to another application. Useful commands are @code{kill-primary-selection} | |
| 5322 and @code{copy-primary-selection}. These work only on text selected | |
| 5323 with the mouse (probably; experiment), and are bound by default to the | |
| 5324 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar. | |
| 5325 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can | |
| 5326 yank the clipboard contents with @code{yank-primary-selection}, bound to | |
| 5327 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}. | |
| 5328 | |
| 5329 If you are communicating by cut and paste with applications that use the | |
| 5330 primary selection, then you can customize | |
| 5331 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs | |
| 5332 version 20 behavior. How can you tell if a program will support this? | |
| 5333 Motifly-correct programs require the clipboard; you lose. For others, | |
| 5334 only by trying it. You also need to customize the complementary | |
| 5335 @code{interprogram-paste-function} to @code{nil}. (Otherwise | |
| 5336 XEmacs-to-XEmacs pastes will not work correctly.) | |
| 5337 | |
| 5338 You may get some relief on Motif by setting | |
| 5339 @code{x-selection-strict-motif-ownership} to nil, but this means you will | |
| 5340 only intermittently be able to paste XEmacs kills to Motif applications. | |
| 5341 | |
| 5342 Thanks to Jeff Mincy and Glynn Clements for corrections. | |
| 5343 | |
| 2459 | 5344 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing |
| 5345 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long? | |
| 2417 | 5346 |
| 5347 It actually doesn't. It leaves the region visible for a second so that | |
| 5348 you can see what area is being yanked. If you start working, though, it | |
| 5349 will immediately complete its operation. In other words, it will only | |
| 5350 delay for a second if you let it. | |
| 5351 | |
| 2459 | 5352 @unnumberedsec 3.4: Editing Source Code |
| 5353 | |
| 5354 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing | |
| 5355 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode? | |
| 2417 | 5356 |
| 5357 Well, first off, consider if you really want to do this. cc-mode is | |
| 5358 much more powerful than the old c-mode. If you're having trouble | |
| 5359 getting your old offsets to work, try using @code{c-set-offset} instead. | |
| 5360 You might also consider using the package @code{cc-compat}. | |
| 5361 | |
| 5362 But, if you still insist, add the following lines to your @file{init.el}: | |
| 5363 | |
| 5364 @lisp | |
| 5365 (fmakunbound 'c-mode) | |
| 5366 (makunbound 'c-mode-map) | |
| 5367 (fmakunbound 'c++-mode) | |
| 5368 (makunbound 'c++-mode-map) | |
| 5369 (makunbound 'c-style-alist) | |
| 5370 (load-library "old-c-mode") | |
| 5371 (load-library "old-c++-mode") | |
| 5372 @end lisp | |
| 5373 | |
| 5374 This must be done before any other reference is made to either c-mode or | |
| 5375 c++-mode. | |
| 5376 | |
| 2459 | 5377 @node Q3.4.2, , Q3.4.1, Editing |
| 5378 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly? | |
| 2417 | 5379 |
| 5380 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the | |
| 5381 same amount instead of indenting the 3rd clause differently from the | |
| 5382 first two. | |
| 5383 | |
| 2459 | 5384 The package @code{cl-indent} that comes with XEmacs sets up this kind |
| 5385 of indentation by default. @code{cl-indent} also knows about many | |
| 5386 other CL-specific forms. To use @code{cl-indent}, one can do this: | |
| 2417 | 5387 |
| 5388 @lisp | |
| 2459 | 5389 (setq lisp-indent-function 'common-lisp-indent-function) |
| 2417 | 5390 @end lisp |
| 5391 | |
| 5392 One can also customize @file{cl-indent.el} so it mimics the default | |
| 5393 @code{if} indentation @code{then} indented more than the @code{else}. | |
| 5394 Here's how: | |
| 5395 | |
| 5396 @lisp | |
| 5397 (put 'if 'common-lisp-indent-function '(nil nil &body)) | |
| 5398 @end lisp | |
| 5399 | |
| 2459 | 5400 @node Display, External Subsystems, Editing, Top |
| 5401 @unnumbered 4 Display Functions | |
| 428 | 5402 |
| 5403 This is part 4 of the XEmacs Frequently Asked Questions list. This | |
| 2459 | 5404 section is devoted to the display-related capabilities of XEmacs |
| 5405 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how | |
| 5406 to customize them. | |
| 5407 | |
| 5408 @menu | |
| 5409 4.0: Textual Fonts and Colors | |
| 5410 * Q4.0.1:: How do I specify a font? | |
| 5411 * Q4.0.2:: How do I set the text, menu and modeline fonts? | |
| 5412 * Q4.0.3:: How can I set color options from @file{init.el}? | |
| 5413 * Q4.0.4:: How can I set the colors when highlighting a region? | |
| 5414 * Q4.0.5:: How can I limit color map usage? | |
| 5415 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them. | |
| 5416 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs? | |
| 5417 * Q4.0.8:: How do I display non-ASCII characters? | |
| 5418 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}. | |
| 5419 | |
| 5420 4.1: Syntax Highlighting (Font Lock) | |
| 5421 * Q4.1.1:: How can I do source code highlighting using font-lock? | |
| 5422 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default? | |
| 5423 | |
| 5424 4.2: The Modeline | |
| 5425 * Q4.2.1:: How can I make the modeline go away? | |
| 5426 * Q4.2.2:: How do you have XEmacs display the line number in the modeline? | |
| 5427 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline? | |
| 5428 * Q4.2.4:: How can I change the modeline color based on the mode used? | |
| 5429 | |
| 5430 4.3: The Cursor | |
| 5431 * Q4.3.1:: Is there a way to make the bar cursor thicker? | |
| 5432 * Q4.3.2:: Is there a way to get back the block cursor? | |
| 5433 * Q4.3.3:: Can I make the cursor blink? | |
| 5434 | |
| 5435 4.4: The Menubar | |
| 5436 * Q4.4.1:: How do I get rid of the menubar? | |
| 5437 * Q4.4.2:: How can I customize the menubar? | |
| 5438 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 5439 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 5440 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working? | |
| 5441 | |
| 5442 4.5: The Toolbar | |
| 5443 * Q4.5.1:: How do I get rid of the toolbar? | |
| 5444 * Q4.5.2:: How can I customize the toolbar? | |
| 5445 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar? | |
| 5446 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar | |
| 5447 | |
| 5448 4.6: Scrollbars and Scrolling | |
| 5449 * Q4.6.1:: How can I disable the scrollbar? | |
| 5450 * Q4.6.2:: How can I change the scrollbar width? | |
| 5451 * Q4.6.3:: How can I use resources to change scrollbar colors? | |
| 5452 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this? | |
| 5453 * Q4.6.5:: Scrolling one line at a time. | |
| 5454 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes? | |
| 5455 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off? | |
| 5456 | |
| 5457 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 5458 * Q4.7.1:: How can I disable the gutter tabs? | |
| 5459 * Q4.7.2:: How can I disable the progress bar? | |
| 5460 * Q4.7.3:: There are bugs in the gutter or widgets. | |
| 5461 * Q4.7.4:: How can I customize the gutter or gutter tabs? | |
| 5462 @end menu | |
| 5463 | |
| 5464 @unnumberedsec 4.0: Textual Fonts and Colors | |
| 5465 | |
| 5466 @node Q4.0.1, Q4.0.2, Display, Display | |
| 5467 @unnumberedsubsec Q4.0.1: How do I specify a font? | |
| 5468 | |
| 5469 #### Update me. | |
| 5470 | |
| 5471 In 21.4 and above, you can use the @samp{Options} menu to change the font. | |
| 5472 You can also do it in your init file, e.g. like this (for MS Windows): | |
| 5473 | |
| 5474 @display | |
| 5475 (set-face-font 'default "Lucida Console:Regular:10") | |
| 5476 (set-face-font 'modeline "MS Sans Serif:Regular:10") | |
| 5477 @end display | |
| 5478 | |
| 5479 @node Q4.0.2, Q4.0.3, Q4.0.1, Display | |
| 5480 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts? | |
| 5481 | |
| 5482 #### Update me. | |
| 5483 | |
| 5484 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when | |
| 5485 setting face values. | |
| 5486 | |
| 5487 In @file{.Xresources}: | |
| 5488 | |
| 5489 @example | |
| 5490 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-* | |
| 5491 Emacs*menubar*font: fixed | |
| 5492 Emacs.modeline.attributeFont: fixed | |
| 5493 @end example | |
| 5494 | |
| 5495 This is confusing because @samp{default} and @samp{modeline} are face | |
| 5496 names, and can be found listed with all faces in the current mode by | |
| 5497 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific | |
| 5498 resource @samp{attributeFont}. | |
| 5499 | |
| 5500 On the other hand, @samp{menubar} is a normal X thing that uses the | |
| 5501 resource @samp{font}. With Motif it @emph{may be} necessary to use | |
| 5502 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif} | |
| 5503 configurations with Mule it @emph{is} necessary to use @samp{fontSet} | |
| 5504 instead of @samp{font}. (Sorry, there just is no simple recipe here.) | |
| 5505 | |
| 5506 @node Q4.0.3, Q4.0.4, Q4.0.2, Display | |
| 5507 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}? | |
| 5508 | |
| 5509 How can I set the most commonly used color options from my | |
| 5510 @file{init.el} instead of from my @file{.Xresources}? | |
| 5511 | |
| 5512 Like this: | |
| 5513 | |
| 5514 @lisp | |
| 5515 (set-face-background 'default "bisque") ; frame background | |
| 5516 (set-face-foreground 'default "black") ; normal text | |
| 5517 (set-face-background 'zmacs-region "red") ; When selecting w/ | |
| 5518 ; mouse | |
| 5519 (set-face-foreground 'zmacs-region "yellow") | |
| 5520 (set-face-font 'default "*courier-bold-r*120-100-100*") | |
| 5521 (set-face-background 'highlight "blue") ; Ie when selecting | |
| 5522 ; buffers | |
| 5523 (set-face-foreground 'highlight "yellow") | |
| 5524 (set-face-background 'modeline "blue") ; Line at bottom | |
| 5525 ; of buffer | |
| 5526 (set-face-foreground 'modeline "white") | |
| 5527 (set-face-font 'modeline "*bold-r-normal*140-100-100*") | |
| 5528 (set-face-background 'isearch "yellow") ; When highlighting | |
| 5529 ; while searching | |
| 5530 (set-face-foreground 'isearch "red") | |
| 5531 (setq x-pointer-foreground-color "black") ; Adds to bg color, | |
| 5532 ; so keep black | |
| 5533 (setq x-pointer-background-color "blue") ; This is color | |
| 5534 ; you really | |
| 5535 ; want ptr/crsr | |
| 5536 @end lisp | |
| 5537 | |
| 5538 @node Q4.0.4, Q4.0.5, Q4.0.3, Display | |
| 5539 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region? | |
| 5540 | |
| 5541 How can I set the background/foreground colors when highlighting a | |
| 5542 region? | |
| 5543 | |
| 5544 You can change the face @code{zmacs-region} either in your | |
| 5545 @file{.Xresources}: | |
| 5546 | |
| 5547 @example | |
| 5548 Emacs.zmacs-region.attributeForeground: firebrick | |
| 5549 Emacs.zmacs-region.attributeBackground: lightseagreen | |
| 5550 @end example | |
| 5551 | |
| 5552 or in your @file{init.el}: | |
| 5553 | |
| 5554 @lisp | |
| 5555 (set-face-background 'zmacs-region "red") | |
| 5556 (set-face-foreground 'zmacs-region "yellow") | |
| 5557 @end lisp | |
| 5558 | |
| 5559 @node Q4.0.5, Q4.0.6, Q4.0.4, Display | |
| 5560 @unnumberedsubsec Q4.0.5: How can I limit color map usage? | |
| 5561 | |
| 5562 I'm using Netscape (or another color grabber like XEmacs); | |
| 5563 is there any way to limit the number of available colors in the color map? | |
| 5564 | |
| 5565 Answer: No, but you can start Netscape before XEmacs, and it will use | |
| 5566 the closest available color if the colormap is full. You can also limit | |
| 5567 the number of colors Netscape uses, using the flags -mono, -ncols <#> or | |
| 5568 -install (for mono, limiting to <#> colors, or for using a private color | |
| 5569 map). | |
| 5570 | |
| 5571 If you have the money, another solution would be to use a truecolor or | |
| 5572 direct color video. | |
| 5573 | |
| 5574 @node Q4.0.6, Q4.0.7, Q4.0.5, Display | |
| 5575 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them. | |
| 5576 | |
| 5577 XEmacs tries to automatically determine whether your tty supports color, | |
| 5578 but sometimes guesses wrong. In that case, you can make XEmacs Do The | |
| 5579 Right Thing using this Lisp code: | |
| 5580 | |
| 5581 @lisp | |
| 5582 (if (eq 'tty (device-type)) | |
| 5583 (set-device-class nil 'color)) | |
| 5584 @end lisp | |
| 5585 | |
| 5586 @node Q4.0.7, Q4.0.8, Q4.0.6, Display | |
| 5587 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs? | |
| 5588 @c New | |
| 5589 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes: | |
| 5590 | |
| 5591 @quotation | |
| 5592 There are several ways to do it. For example, you could specify a | |
| 5593 default pixmap image to use in your @file{~/.Xresources}, e.g., | |
| 5594 | |
| 5595 | |
| 5596 @example | |
| 5597 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm | |
| 5598 @end example | |
| 5599 | |
| 5600 | |
| 5601 and then reload ~/.Xresources and restart XEmacs. Alternatively, | |
| 5602 since each face can have its own pixmap background, a better way | |
| 5603 would be to set a face's pixmap within your XEmacs init file, e.g., | |
| 5604 | |
| 5605 @lisp | |
| 5606 (set-face-background-pixmap 'default "/path/to/image.xpm") | |
| 5607 (set-face-background-pixmap 'bold "/path/to/another_image.xpm") | |
| 5608 @end lisp | |
| 5609 | |
| 5610 and so on. You can also do this interactively via @kbd{M-x edit-faces}. | |
| 5611 | |
| 5612 @end quotation | |
| 5613 | |
| 5614 @node Q4.0.8, Q4.0.9, Q4.0.7, Display | |
| 5615 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters? | |
| 5616 @c New | |
| 5617 | |
| 5618 If you're using a Mule-enabled XEmacs, then display is automatic. If | |
| 5619 you're not seeing the characters you expect, either (1) you don't have | |
| 5620 appropriate fonts available or (2) XEmacs did not correctly detect the | |
| 5621 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1), | |
| 5622 install fonts as is customary for your platform. In case (2), you | |
| 5623 need to tell XEmacs explicitly what coding systems you're using. | |
| 5624 @ref{Specify Coding, , , xemacs}. | |
| 5625 | |
| 5626 If your XEmacs is not Mule-enabled, and for some reason getting a | |
| 5627 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost. | |
| 5628 You can arrange it by brute force. In @file{event-Xt.c} (suppress the | |
| 5629 urge to look in this file---play Doom instead, because you'll survive | |
| 5630 longer), it is written: | |
| 5631 | |
| 5632 @quotation | |
| 5633 In a non-Mule world, a user can still have a multi-lingual editor, by | |
| 5634 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all | |
| 5635 their Latin-2 buffers, etc. | |
| 5636 @end quotation | |
| 5637 | |
| 5638 For the related problem of @emph{inputting} non-ASCII characters in a | |
| 5639 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters | |
| 5640 in XEmacs?}. | |
| 5641 | |
| 5642 @node Q4.0.9, Q4.1.1, Q4.0.8, Display | |
| 5643 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}. | |
| 5644 | |
| 5645 @email{mannj@@ll.mit.edu, John Mann} writes: | |
| 5646 | |
| 5647 @quotation | |
| 5648 You have to go to @samp{Options->Menubars} and unselect | |
| 5649 @samp{Frame-Local Font Menu}. If this option is selected, font changes | |
| 5650 are only applied to the @emph{current} frame and do @emph{not} get saved | |
| 5651 when you save options. | |
| 5652 @end quotation | |
| 5653 | |
| 5654 Also, set the following in your @file{init.el}: | |
| 5655 | |
| 5656 @lisp | |
| 5657 (setq options-save-faces t) | |
| 5658 @end lisp | |
| 5659 | |
| 5660 @unnumberedsec 4.1: Syntax Highlighting (Font Lock) | |
| 5661 | |
| 5662 @node Q4.1.1, Q4.1.2, Q4.0.9, Display | |
| 5663 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock? | |
| 5664 | |
| 5665 For most modes, font-lock is already set up and just needs to be turned | |
| 5666 on. This can be done by adding the line: | |
| 5667 | |
| 5668 @lisp | |
| 5669 (require 'font-lock) | |
| 5670 @end lisp | |
| 5671 | |
| 5672 to your @file{init.el}. (You can turn it on for the | |
| 5673 current buffer and session only by @kbd{M-x font-lock-mode}.) See the | |
| 5674 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs | |
| 5675 versions prior to 21.4) for more information. | |
| 5676 | |
| 5677 @c the old way: | |
| 5678 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock) | |
| 5679 @c (add-hook 'dired-mode-hook 'turn-on-font-lock) | |
| 5680 | |
| 5681 See also @code{Syntax Highlighting} from the @code{Options} menu. | |
| 5682 Remember to save options. | |
| 5683 | |
| 5684 @node Q4.1.2, Q4.2.1, Q4.1.1, Display | |
| 5685 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default? | |
| 5686 | |
| 5687 Use the following code in your @file{init.el}: | |
| 5688 | |
| 5689 @lisp | |
| 5690 (setq-default font-lock-maximum-decoration t) | |
| 5691 @end lisp | |
| 5692 | |
| 5693 See also @code{Syntax Highlighting} from the @code{Options} menu. | |
| 5694 Remember to save options. | |
| 5695 | |
| 5696 @unnumberedsec 4.2: The Modeline | |
| 5697 | |
| 5698 @node Q4.2.1, Q4.2.2, Q4.1.2, Display | |
| 5699 @unnumberedsubsec Q4.2.1: How can I make the modeline go away? | |
| 5700 | |
| 5701 @lisp | |
| 5702 (set-specifier has-modeline-p nil) | |
| 5703 @end lisp | |
| 5704 | |
| 5705 @node Q4.2.2, Q4.2.3, Q4.2.1, Display | |
| 5706 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline? | |
| 5707 | |
| 5708 Add the following line to your @file{init.el} file to | |
| 5709 display the line number: | |
| 5710 | |
| 5711 @lisp | |
| 5712 (line-number-mode 1) | |
| 5713 @end lisp | |
| 5714 | |
| 5715 Use the following to display the column number: | |
| 5716 | |
| 5717 @lisp | |
| 5718 (column-number-mode 1) | |
| 5719 @end lisp | |
| 5720 | |
| 5721 Or select from the @code{Options} menu | |
| 5722 @iftex | |
| 5723 @* | |
| 5724 @end iftex | |
| 5725 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode} | |
| 5726 and/or | |
| 5727 @iftex | |
| 5728 @* | |
| 5729 @end iftex | |
| 5730 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode} | |
| 5731 | |
| 5732 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}. | |
| 5733 | |
| 5734 @node Q4.2.3, Q4.2.4, Q4.2.2, Display | |
| 5735 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline? | |
| 5736 | |
| 5737 Add the following line to your @file{init.el} file to | |
| 5738 display the time: | |
| 5739 | |
| 5740 @lisp | |
| 5741 (display-time) | |
| 5742 @end lisp | |
| 5743 | |
| 5744 See @code{Customize} from the @code{Options} menu for customization. | |
| 5745 | |
| 5746 @node Q4.2.4, Q4.3.1, Q4.2.3, Display | |
| 5747 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used? | |
| 5748 | |
| 5749 You can use something like the following: | |
| 5750 | |
| 5751 @lisp | |
| 5752 (add-hook 'lisp-mode-hook | |
| 5753 (lambda () | |
| 5754 (set-face-background 'modeline "red" (current-buffer)))) | |
| 5755 @end lisp | |
| 5756 | |
| 5757 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline | |
| 5758 colors change from the default set in your @file{init.el}. | |
| 5759 The change will only be made in the buffer you just entered (which | |
| 5760 contains the Lisp file you are editing) and will not affect the modeline | |
| 5761 colors anywhere else. | |
| 5762 | |
| 5763 Notes: | |
| 5764 | |
| 5765 @itemize @bullet | |
| 5766 | |
| 5767 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook, | |
| 5768 c++-mode-hook, emacs-lisp-mode-hook (used for your | |
| 5769 @file{init.el} or a @file{xx.el} file), | |
| 5770 lisp-interaction-mode-hook (the @samp{*scratch*} buffer), | |
| 5771 text-mode-hook, etc. | |
| 5772 | |
| 5773 @item | |
| 5774 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)}, | |
| 5775 otherwise you will erase anything that anybody has already put on the | |
| 5776 hook. | |
| 5777 | |
| 5778 @item | |
| 5779 You can also do @code{(set-face-font 'modeline @var{font})}, | |
| 5780 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*" | |
| 5781 (current-buffer))} if you wish the modeline font to vary based on the | |
| 5782 current mode. | |
| 5783 @end itemize | |
| 5784 | |
| 5785 There are additional modeline faces, @code{modeline-buffer-id}, | |
| 5786 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which | |
| 5787 you may want to customize. | |
| 5788 | |
| 5789 @unnumberedsec 4.3: The Cursor | |
| 5790 | |
| 5791 @node Q4.3.1, Q4.3.2, Q4.2.4, Display | |
| 5792 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker? | |
| 5793 | |
| 5794 I'd like to have the bar cursor a little thicker, as I tend to "lose" it | |
| 5795 often. | |
| 5796 | |
| 5797 For a 1 pixel bar cursor, use: | |
| 5798 | |
| 5799 @lisp | |
| 5800 (setq bar-cursor t) | |
| 5801 @end lisp | |
| 5802 | |
| 5803 For a 2 pixel bar cursor, use: | |
| 5804 | |
| 5805 @lisp | |
| 5806 (setq bar-cursor 'anything-else) | |
| 5807 @end lisp | |
| 5808 | |
| 5809 You can also change these with Customize. | |
| 5810 Select from the @code{Options} menu | |
| 5811 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type | |
| 5812 @kbd{M-x customize @key{RET} display @key{RET}}. | |
| 5813 | |
| 5814 You can use a color to make it stand out better: | |
| 5815 | |
| 5816 @example | |
| 5817 Emacs*cursorColor: Red | |
| 5818 @end example | |
| 5819 | |
| 5820 @node Q4.3.2, Q4.3.3, Q4.3.1, Display | |
| 5821 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor? | |
| 5822 | |
| 5823 @lisp | |
| 5824 (setq bar-cursor nil) | |
| 5825 @end lisp | |
| 5826 | |
| 5827 You can also change this with Customize. | |
| 5828 Select from the @code{Options} menu | |
| 5829 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type | |
| 5830 @kbd{M-x customize @key{RET} display @key{RET}}. | |
| 5831 | |
| 5832 @node Q4.3.3, Q4.4.1, Q4.3.2, Display | |
| 5833 @unnumberedsubsec Q4.3.3: Can I make the cursor blink? | |
| 5834 | |
| 5835 Yes, like this: | |
| 5836 | |
| 5837 @lisp | |
| 5838 (blink-cursor-mode) | |
| 5839 @end lisp | |
| 5840 | |
| 5841 This function toggles between a steady cursor and a blinking cursor. | |
| 5842 You may also set this mode from the menu bar by selecting | |
| 5843 @samp{Options->Display->Blinking Cursor}. Remember to save options. | |
| 5844 | |
| 5845 @unnumberedsec 4.4: The Menubar | |
| 5846 | |
| 5847 @node Q4.4.1, Q4.4.2, Q4.3.3, Display | |
| 5848 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar? | |
| 5849 | |
| 5850 @lisp | |
| 5851 (set-specifier menubar-visible-p nil) | |
| 5852 @end lisp | |
| 5853 | |
| 5854 @node Q4.4.2, Q4.4.3, Q4.4.1, Display | |
| 5855 @unnumberedsubsec Q4.4.2: How can I customize the menubar? | |
| 5856 | |
| 5857 For an extensive menubar, add this line to your @file{init.el}: | |
| 5858 | |
| 5859 @lisp | |
| 5860 (load "big-menubar") | |
| 5861 @end lisp | |
| 5862 | |
| 5863 If you'd like to write your own, this file provides as good a set of | |
| 5864 examples as any to start from. The file is located in edit-utils | |
| 5865 package. | |
| 5866 | |
| 5867 @node Q4.4.3, Q4.4.4, Q4.4.2, Display | |
| 5868 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 5869 | |
| 5870 #### Write me. | |
| 5871 | |
| 5872 @node Q4.4.4, Q4.4.5, Q4.4.3, Display | |
| 5873 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 5874 | |
| 5875 Add the following to your @file{init.el} (suit to fit): | |
| 5876 | |
| 5877 @lisp | |
| 5878 (setq buffers-menu-max-size 20) | |
| 5879 @end lisp | |
| 5880 | |
| 5881 For no limit, use an argument of @samp{nil}. | |
| 5882 | |
| 5883 You can also change this with Customize. Select from the | |
| 5884 @code{Options} menu | |
| 5885 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...} | |
| 5886 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}. | |
| 5887 | |
| 5888 @node Q4.4.5, Q4.5.1, Q4.4.4, Display | |
| 5889 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working? | |
| 5890 | |
| 5891 I am trying to use a resource like @code{Emacs*menubar*font} to set the | |
| 5892 font of the menubar but it's not working. | |
| 5893 | |
| 5894 In Motif, the use of @samp{font} resources is obsoleted in order to | |
| 5895 support internationalization. If you are using the real Motif menubar, | |
| 5896 this resource is not recognized at all; you have to say: | |
| 5897 | |
| 5898 @example | |
| 5899 Emacs*menubar*fontList: FONT | |
| 5900 @end example | |
| 5901 | |
| 5902 If you are using the Lucid menubar, for backward compatibility with | |
| 5903 existing user configurations, the @samp{font} resource is recognized. | |
| 5904 Since this is not supported by Motif itself, the code is a kludge and | |
| 5905 the @samp{font} resource will be recognized only if the @samp{fontList} | |
| 5906 resource resource is unset. This means that the resource | |
| 5907 | |
| 5908 @example | |
| 5909 *fontList: FONT | |
| 5910 @end example | |
| 5911 | |
| 5912 will override | |
| 5913 | |
| 5914 @example | |
| 5915 Emacs*menubar*font: FONT | |
| 5916 @end example | |
| 5917 | |
| 5918 even though the latter is more specific. | |
| 5919 | |
| 5920 In non-Motif configurations using @samp{--with-mule} and | |
| 5921 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet} | |
| 5922 resource @emph{instead of} the @code{font} resource. The backward | |
| 5923 compatibility kludge was never implemented for non-Motif builds. | |
| 5924 Example: | |
| 5925 | |
| 5926 @example | |
| 5927 *fontSet: FONT | |
| 5928 @end example | |
| 5929 | |
| 5930 @unnumberedsec 4.5: The Toolbar | |
| 5931 | |
| 5932 @node Q4.5.1, Q4.5.2, Q4.4.5, Display | |
| 5933 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar? | |
| 5934 | |
| 5935 #### Write me. | |
| 5936 | |
| 5937 @node Q4.5.2, Q4.5.3, Q4.5.1, Display | |
| 5938 @unnumberedsubsec Q4.5.2: How can I customize the toolbar? | |
| 5939 | |
| 5940 #### Write me. | |
| 5941 | |
| 5942 @node Q4.5.3, Q4.5.4, Q4.5.2, Display | |
| 5943 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar? | |
| 5944 | |
| 5945 Try something like: | |
| 5946 | |
| 5947 @lisp | |
| 5948 (defun my-toggle-toolbar () | |
| 5949 (interactive) | |
| 5950 (set-specifier default-toolbar-visible-p | |
| 5951 (not (specifier-instance default-toolbar-visible-p)))) | |
| 5952 (global-set-key "\C-xT" 'my-toggle-toolbar) | |
| 5953 @end lisp | |
| 5954 | |
| 5955 @ignore | |
| 5956 @c Probably not relevant any more | |
| 5957 There are redisplay bugs in 19.14 that may make the preceding result in | |
| 5958 a messed-up display, especially for frames with multiple windows. You | |
| 5959 may need to resize the frame before XEmacs completely realizes the | |
| 5960 toolbar is really gone. | |
| 5961 @end ignore | |
| 5962 | |
| 5963 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct | |
| 5964 code. | |
| 5965 | |
| 5966 @node Q4.5.4, Q4.6.1, Q4.5.3, Display | |
| 5967 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar | |
| 5968 | |
| 5969 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes: | |
| 5970 | |
| 5971 I just installed the XEmacs (20.4-2) RPMS that I downloaded from | |
| 5972 @uref{http://www.xemacs.org/}. Everything works fine, except that when | |
| 5973 I place my mouse over the toolbar, it beeps and gives me this message: | |
| 5974 | |
| 5975 @example | |
| 5976 Can't instantiate image (probably cached): | |
| 5977 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data | |
| 5978 (16 16 <strange control characters> ... | |
| 5979 @end example | |
| 5980 | |
| 5981 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes: | |
| 5982 @quotation | |
| 5983 This is problem specific to some Chips and Technologies video | |
| 5984 chips, when running XFree86. Putting | |
| 5985 | |
| 5986 @code{Option "sw_cursor"} | |
| 5987 | |
| 5988 in @file{XF86Config} gets rid of the problem. | |
| 5989 @end quotation | |
| 5990 | |
| 5991 @unnumberedsec 4.6: Scrollbars and Scrolling | |
| 5992 | |
| 5993 @node Q4.6.1, Q4.6.2, Q4.5.4, Display | |
| 5994 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar? | |
| 5995 | |
| 5996 To disable them for all frames, add the following line to | |
| 5997 your @file{.Xresources}: | |
| 5998 | |
| 5999 @example | |
| 6000 Emacs.scrollBarWidth: 0 | |
| 6001 @end example | |
| 6002 | |
| 6003 Or select @samp{Options->Display->Scrollbars}. | |
| 6004 Remember to save options. | |
| 6005 | |
| 6006 To turn the scrollbar off on a per-frame basis, use the following | |
| 6007 function: | |
| 6008 | |
| 6009 @lisp | |
| 6010 (set-specifier scrollbar-width 0 (selected-frame)) | |
| 6011 @end lisp | |
| 6012 | |
| 6013 You can actually turn the scrollbars on at any level you want by | |
| 6014 substituting for (selected-frame) in the above command. For example, to | |
| 6015 turn the scrollbars off only in a single buffer: | |
| 6016 | |
| 6017 @lisp | |
| 6018 (set-specifier scrollbar-width 0 (current-buffer)) | |
| 6019 @end lisp | |
| 6020 | |
| 6021 @node Q4.6.2, Q4.6.3, Q4.6.1, Display | |
| 6022 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width? | |
| 6023 | |
| 6024 #### Write me. | |
| 6025 | |
| 6026 @node Q4.6.3, Q4.6.4, Q4.6.2, Display | |
| 6027 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors? | |
| 6028 | |
| 6029 Here's a recap of how to use resources to change your scrollbar colors: | |
| 6030 | |
| 6031 @example | |
| 6032 ! Motif scrollbars | |
| 6033 | |
| 6034 Emacs*XmScrollBar.Background: skyblue | |
| 6035 Emacs*XmScrollBar.troughColor: lightgray | |
| 6036 | |
| 6037 ! Athena scrollbars | |
| 6038 | |
| 6039 Emacs*Scrollbar.Foreground: skyblue | |
| 6040 Emacs*Scrollbar.Background: lightgray | |
| 6041 @end example | |
| 6042 | |
| 6043 Note the capitalization of @code{Scrollbar} for the Athena widget. | |
| 6044 | |
| 6045 @node Q4.6.4, Q4.6.5, Q4.6.3, Display | |
| 6046 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this? | |
| 6047 | |
| 6048 When I move the scrollbar in an XEmacs window, it moves the point as | |
| 6049 well, which should not be the default behavior. Is this a bug or a | |
| 6050 feature? Can I disable it? | |
| 6051 | |
| 6052 The current behavior is a feature, not a bug. Point remains at the same | |
| 6053 buffer position as long as that position does not scroll off the screen. | |
| 6054 In that event, point will end up in either the upper-left or lower-left | |
| 6055 hand corner. | |
| 6056 | |
| 6057 This cannot be changed. | |
| 6058 | |
| 6059 @node Q4.6.5, Q4.6.6, Q4.6.4, Display | |
| 6060 @unnumberedsubsec Q4.6.5: Scrolling one line at a time. | |
| 6061 | |
| 6062 Can the cursor keys scroll the screen a line at a time, rather than the | |
| 6063 default half page jump? I tend it to find it disorienting. | |
| 6064 | |
| 6065 Use the following: | |
| 6066 | |
| 6067 @lisp | |
| 6068 (setq scroll-step 1) | |
| 6069 @end lisp | |
| 6070 | |
| 6071 You can also change this with Customize. Select from the | |
| 6072 @code{Options} menu | |
| 6073 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...} | |
| 6074 or type @kbd{M-x customize @key{RET} windows @key{RET}}. | |
| 6075 | |
| 6076 @node Q4.6.6, Q4.6.7, Q4.6.5, Display | |
| 6077 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes? | |
| 6078 | |
| 6079 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes | |
| 6080 in which you want lines truncated. | |
| 6081 | |
| 6082 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars | |
| 6083 will never appear. Otherwise, they will appear only if the value of | |
| 6084 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you | |
| 6085 do | |
| 6086 | |
| 6087 @lisp | |
| 6088 (set-specifier scrollbar-height 0) | |
| 6089 @end lisp | |
| 6090 | |
| 6091 then horizontal scrollbars will not appear in truncated buffers unless | |
| 6092 the package specifically asked for them. | |
| 6093 | |
| 6094 @node Q4.6.7, Q4.7.1, Q4.6.6, Display | |
| 6095 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off? | |
| 6096 | |
| 6097 @code{auto-show-mode} controls whether or not a horizontal scrollbar | |
| 6098 magically appears when a line is too long to be displayed. This is | |
| 6099 enabled by default. To turn it off, put the following in your | |
| 6100 @file{init.el}: | |
| 6101 | |
| 6102 @lisp | |
| 6103 (setq auto-show-mode nil) | |
| 6104 (setq-default auto-show-mode nil) | |
| 6105 @end lisp | |
| 6106 | |
| 6107 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 6108 | |
| 6109 @node Q4.7.1, Q4.7.2, Q4.6.7, Display | |
| 6110 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs? | |
| 6111 | |
| 6112 #### Write me. | |
| 6113 | |
| 6114 @node Q4.7.2, Q4.7.3, Q4.7.1, Display | |
| 6115 @unnumberedsubsec Q4.7.2: How can I disable the progress bar? | |
| 6116 | |
| 6117 #### Write me. | |
| 6118 | |
| 6119 @node Q4.7.3, Q4.7.4, Q4.7.2, Display | |
| 6120 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets. | |
| 6121 | |
| 6122 #### Write me. | |
| 6123 | |
| 6124 @node Q4.7.4, , Q4.7.3, Display | |
| 6125 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs? | |
| 6126 | |
| 6127 #### Write me. | |
| 6128 | |
| 6129 @node External Subsystems, Internet, Display, Top | |
| 6130 @unnumbered 5 Interfacing with the Operating System and External Devices | |
| 6131 | |
| 6132 This is part 5 of the XEmacs Frequently Asked Questions list. This | |
| 2417 | 6133 section is devoted to the various ways that XEmacs interfaces with the |
| 6134 operating system, with other processes and with external devices such | |
| 6135 as speakers and the printer. | |
| 428 | 6136 |
| 6137 @menu | |
| 2459 | 6138 5.0: X Window System and Resources |
| 6139 * Q5.0.1:: Where is a list of X resources? | |
| 6140 * Q5.0.2:: How can I detect a color display? | |
| 6141 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}? | |
| 6142 * Q5.0.4:: How can I have the window title area display the full path? | |
| 6143 * Q5.0.5:: @samp{xemacs -name junk} doesn't work? | |
| 6144 * 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
|
6145 * Q5.0.7:: How can I use antialiased fonts under X11? |
| 2459 | 6146 |
| 6147 5.1: Microsoft Windows | |
| 6148 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? | |
| 6149 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 6150 | |
| 6151 5.2: Printing | |
| 6152 * Q5.2.1:: What do I need to change to make printing work? | |
| 6153 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer? | |
| 6154 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 6155 * Q5.2.4:: Can you print under MS Windows? | |
| 6156 | |
| 6157 5.3: Sound | |
| 6158 * Q5.3.1:: How do I turn off the sound? | |
| 6159 * Q5.3.2:: How do I get funky sounds instead of a boring beep? | |
| 6160 * Q5.3.3:: What are NAS and ESD (EsounD)? | |
| 6161 * Q5.3.4:: Sunsite sounds don't play. | |
| 6162 | |
| 6163 5.4: Running an Interior Shell, Invoking Subprocesses | |
| 6164 * Q5.4.1:: What is an interior shell? | |
| 6165 * Q5.4.2:: How do I start up a second shell buffer? | |
| 6166 * Q5.4.3:: Telnet from shell filters too much | |
| 6167 * Q5.4.4:: Strange things are happening in Shell Mode. | |
| 6168 * Q5.4.5:: XEmacs complains "No such file or directory, diff" | |
| 2995 | 6169 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed" |
| 2459 | 6170 |
| 6171 5.5: Multiple Device Support | |
| 6172 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display? | |
| 6173 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 6174 * Q5.5.3:: How do I disable gnuserv from opening a new frame? | |
| 6175 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 6176 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 428 | 6177 @end menu |
| 6178 | |
| 2459 | 6179 @unnumberedsec 5.0: X Window System and Resources |
| 6180 | |
| 6181 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems | |
| 6182 @unnumberedsubsec Q5.0.1: Where is a list of X resources? | |
| 2417 | 6183 |
| 6184 Search through the @file{NEWS} file for @samp{X Resources}. A fairly | |
| 6185 comprehensive list is given after it. | |
| 6186 | |
| 6187 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is | |
| 6188 supplied, listing the defaults. The file @file{etc/sample.Xresources} | |
| 6189 gives a different set of defaults that you might consider for | |
| 6190 installation in your @file{~/.Xresources} file. It is nearly the same | |
| 6191 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about | |
| 6192 installing the contents of this file into your @file{.Xresources} (or | |
| 6193 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well. | |
| 6194 | |
| 2459 | 6195 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems |
| 6196 @unnumberedsubsec Q5.0.2: How can I detect a color display? | |
| 2417 | 6197 |
| 6198 You can test the return value of the function @code{(device-class)}, as | |
| 6199 in: | |
| 6200 | |
| 6201 @lisp | |
| 6202 (when (eq (device-class) 'color) | |
| 6203 (set-face-foreground 'font-lock-comment-face "Grey") | |
| 6204 (set-face-foreground 'font-lock-string-face "Red") | |
| 6205 .... | |
| 6206 ) | |
| 6207 @end lisp | |
| 6208 | |
| 2459 | 6209 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems |
| 6210 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}? | |
| 2417 | 6211 |
| 6212 I'd like the icon to just say @samp{XEmacs}, and not include the name of | |
| 6213 the current file in it. | |
| 6214 | |
| 6215 Add the following line to your @file{init.el}: | |
| 6216 | |
| 6217 @lisp | |
| 6218 (setq frame-icon-title-format "XEmacs") | |
| 6219 @end lisp | |
| 6220 | |
| 2459 | 6221 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems |
| 6222 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path? | |
| 2417 | 6223 |
| 6224 I'd like to have the window title area display the full directory/name | |
| 6225 of the current buffer file and not just the name. | |
| 6226 | |
| 6227 Add the following line to your @file{init.el}: | |
| 6228 | |
| 6229 @lisp | |
| 6230 (setq frame-title-format "%S: %f") | |
| 6231 @end lisp | |
| 6232 | |
| 6233 A more sophisticated title might be: | |
| 6234 | |
| 6235 @lisp | |
| 6236 (setq frame-title-format | |
| 6237 '("%S: " (buffer-file-name "%f" | |
| 6238 (dired-directory dired-directory "%b")))) | |
| 6239 @end lisp | |
| 6240 | |
| 6241 That is, use the file name, or the dired-directory, or the buffer name. | |
| 6242 | |
| 2459 | 6243 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems |
| 6244 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work? | |
| 2417 | 6245 |
| 6246 When I run @samp{xterm -name junk}, I get an xterm whose class name | |
| 6247 according to xprop, is @samp{junk}. This is the way it's supposed to | |
| 6248 work, I think. When I run @samp{xemacs -name junk} the class name is | |
| 6249 not set to @samp{junk}. It's still @samp{emacs}. What does | |
| 6250 @samp{xemacs -name} really do? The reason I ask is that my window | |
| 6251 manager (fvwm) will make a window sticky and I use XEmacs to read my | |
| 6252 mail. I want that XEmacs window to be sticky, without having to use the | |
| 6253 window manager's function to set the window sticky. What gives? | |
| 6254 | |
| 6255 @samp{xemacs -name} sets the application name for the program (that is, | |
| 6256 the thing which normally comes from @samp{argv[0]}). Using @samp{-name} | |
| 6257 is the same as making a copy of the executable with that new name. The | |
| 6258 @code{WM_CLASS} property on each frame is set to the frame-name, and the | |
| 6259 application-class. So, if you did @samp{xemacs -name FOO} and then | |
| 6260 created a frame named @var{BAR}, you'd get an X window with WM_CLASS = | |
| 6261 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this | |
| 6262 widget would be: | |
| 6263 | |
| 6264 @example | |
| 6265 Name: FOO .shell .container .BAR | |
| 6266 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame | |
| 6267 @end example | |
| 6268 | |
| 6269 instead of the default | |
| 6270 | |
| 6271 @example | |
| 6272 Name: xemacs.shell .container .emacs | |
| 6273 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame | |
| 6274 @end example | |
| 6275 | |
| 6276 | |
| 6277 It is arguable that the first element of WM_CLASS should be set to the | |
| 6278 application-name instead of the frame-name, but I think that's less | |
| 6279 flexible, since it does not give you the ability to have multiple frames | |
| 6280 with different WM_CLASS properties. Another possibility would be for | |
| 6281 the default frame name to come from the application name instead of | |
| 6282 simply being @samp{emacs}. However, at this point, making that change | |
| 6283 would be troublesome: it would mean that many users would have to make | |
| 6284 yet another change to their resource files (since the default frame name | |
| 6285 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever | |
| 6286 the executable happened to be named), so we'd rather avoid it. | |
| 6287 | |
| 6288 To make a frame with a particular name use: | |
| 6289 | |
| 6290 @lisp | |
| 6291 (make-frame '((name . "the-name"))) | |
| 6292 @end lisp | |
| 6293 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6294 @node Q5.0.6, Q5.0.7, Q5.0.5, External Subsystems |
| 2459 | 6295 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work. |
| 2417 | 6296 |
| 6297 When I start up XEmacs using @samp{-iconic} it doesn't work right. | |
| 6298 Using @samp{-unmapped} on the command line, and setting the | |
| 6299 @code{initiallyUnmapped} X Resource don't seem to help much either... | |
| 6300 | |
| 6301 @email{ben@@xemacs.org, Ben Wing} writes: | |
| 6302 | |
| 6303 @quotation | |
| 6304 Ugh, this stuff is such an incredible mess that I've about given up | |
| 6305 getting it to work. The principal problem is numerous window-manager | |
| 6306 bugs... | |
| 6307 @end quotation | |
| 6308 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6309 @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
|
6310 @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
|
6311 |
|
4509
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6312 The X11 version of XEmacs can use antialiased fonts via the Xft, |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6313 fontconfig, and freetype libraries. To configure this you need a recent |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6314 beta version (at least 21.5.24); the more recent, the better. This is |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6315 beta software, the usual caveats apply. Rebuild xemacs using the |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6316 following configure options, plus any others you normally use: |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6317 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6318 @samp{--enable-mule --with-xft=emacs,menubars} |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6319 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6320 Xft @emph{may} work without Mule but the developers working on the Xft |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6321 code invariably build with Mule. The tab control also supports Xft, and |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6322 at some date the progress gauge will as well. If they are configured in |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6323 to XEmacs, you may add @samp{tabs} and @samp{gauges} to the value of the |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6324 @samp{--with-xft} option (with a comma separating each value from the |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6325 previous ones). For further details on the XEmacs widgets that support |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6326 XFT, see the output of @code{./configure --help}. If you use a package |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6327 manager from your OS distribution, you may need to install development |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6328 packages for @file{fontconfig} and @file{Xft}, and possibly for their |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6329 prequisites. |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6330 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6331 To specify a particular antialiased font, put something like the |
|
4509
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6332 following lines in your @file{~/.Xdefaults} or @file{~/.Xresources}: |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6333 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6334 @example |
|
4509
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6335 XEmacs.default.attributeFont: monospace-12 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6336 XEmacs.bold.attributeFont: monospace-12:style=Bold |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6337 XEmacs.italic.attributeFont: monospace-12:style=Oblique |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6338 XEmacs.bold-italic.attributeFont: monospace-12:style=Bold Oblique |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6339 XEmacs.modeline.attributeFont: sans-serif-11 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6340 XEmacs.menubar.xftFont: sans-serif-11 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6341 XEmacs*XftFont: sans-serif-11 |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6342 @end example |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6343 |
|
4509
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6344 @strong{Warning}: These resource naming conventions are just hacks to |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6345 get the code running; you should expect them to change. (Sorry about |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6346 that, but this @emph{is} beta software!) |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6347 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6348 Then run @code{xrdb -merge} before starting the new, XFT-enabled |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6349 xemacs. You can choose the available fonts from the list given by |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6350 @code{fc-list}; try @code{xfd -fa FONTNAME-SIZE} to preview a given |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6351 font. Note that ``monospace'' and ``sans-serif'' are generic aliases |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6352 defined by fontconfig which may correspond to any of many real fonts |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6353 based on local configuration and availability of the aliased fonts, |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6354 and so are likely to give good results in a well-set-up system. |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6355 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6356 Although Customize does not yet handle fontconfig fontspecs, you can |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6357 pass them as strings directly to @samp{set-face-font} to set fonts from |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6358 Lisp. |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6359 |
| 2459 | 6360 @unnumberedsec 5.1: Microsoft Windows |
| 6361 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6362 @node Q5.1.1, Q5.1.2, Q5.0.7, External Subsystems |
| 2459 | 6363 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? |
| 2417 | 6364 |
| 6365 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*} | |
| 6366 symbols to @samp{w32-*}. Does XEmacs do the same? | |
| 6367 | |
| 6368 We consider such a move counter-productive, thus we do not use the | |
| 6369 @samp{w32} prefix. (His rather questionable justification was that he | |
| 6370 did not consider Windows to be a "winning" platform.) However, the name | |
| 6371 @samp{Win32} is not particularly descriptive outside the Windows world, | |
| 6372 and using just @samp{windows-} would be too generic. So we chose a | |
| 6373 compromise, the prefix @samp{mswindows-} for Windows-related variables | |
| 6374 and functions. | |
| 6375 | |
| 6376 Thus all the XEmacs variables and functions directly related to either | |
| 6377 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a | |
| 6378 couple of debugging variables, prefixed @samp{debug-mswindows-}). From | |
| 6379 an architectural perspective, however, we believe that this is mostly a | |
| 6380 non-issue because there should be a very small number of | |
| 6381 window-systems-specific variables anyway. Whenever possible, we try to | |
| 6382 provide generic interfaces that apply to all window systems. | |
| 6383 | |
| 6384 @c not true: | |
| 6385 @c The user variables | |
| 6386 @c that share functionality with existing NT Emacs variables are be named | |
| 6387 @c with our convention, but we provide the GNU Emacs names as | |
| 6388 @c compatibility aliases. | |
| 6389 | |
| 2459 | 6390 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems |
| 6391 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 2417 | 6392 |
| 6393 @unnumberedsubsubsec Associating a new file type with XEmacs. | |
| 6394 | |
| 6395 In Explorer select @samp{View->Options->File Types}, press @samp{[New | |
| 6396 Type...]} and fill in the dialog box, e.g.: | |
| 6397 | |
| 6398 @example | |
| 6399 Description of type: Emacs Lisp source | |
| 6400 Associated extension: el | |
| 6401 Content Type (MIME): text/plain | |
| 6402 @end example | |
| 6403 | |
| 6404 then press @samp{[New...]} and fill in the @samp{Action} dialog box as | |
| 6405 follows: | |
| 6406 | |
| 6407 @example | |
| 6408 Action: | |
| 6409 Open | |
| 6410 | |
| 6411 Application used to perform action: | |
| 6412 D:\Full\path\for\xemacs.exe "%1" | |
| 6413 | |
| 6414 [x] Use DDE | |
| 6415 | |
| 6416 DDE Message: | |
| 6417 open("%1") | |
| 6418 | |
| 6419 Application: | |
| 6420 <leave blank> | |
| 6421 | |
| 6422 DDE Application Not Running: | |
| 6423 <leave blank> | |
| 6424 | |
| 6425 Topic: | |
| 6426 <leave blank> | |
| 6427 @end example | |
| 6428 | |
| 6429 @unnumberedsubsubsec Associating an existing file type with XEmacs. | |
| 6430 | |
| 6431 In Explorer select @samp{View->Options->File Types}. Click on the file | |
| 6432 type in the list and press @samp{[Edit...]}. If the file type already | |
| 6433 has an @samp{Open} action, double click on it and fill in the | |
| 6434 @samp{Action} dialog box as described above; otherwise create a new | |
| 6435 action. | |
| 6436 | |
| 6437 If the file type has more than one action listed, you probably want to | |
| 6438 make the @samp{Open} action that you just edited the default by clicking on | |
| 6439 it and pressing @samp{Set Default}. | |
| 6440 | |
| 6441 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types} | |
| 6442 using @samp{Control Panel->Folder Options->File Types}. | |
| 6443 | |
| 2459 | 6444 @unnumberedsec 5.2: Printing |
| 6445 | |
| 6446 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems | |
| 6447 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work? | |
| 2417 | 6448 |
| 6449 For regular printing there are two variables that can be customized. | |
| 6450 | |
| 6451 @table @code | |
| 6452 @item lpr-command | |
| 6453 This should be set to a command that takes standard input and sends | |
| 6454 it to a printer. Something like: | |
| 6455 | |
| 6456 @lisp | |
| 6457 (setq lpr-command "lp") | |
| 6458 @end lisp | |
| 6459 | |
| 6460 @item lpr-switches | |
| 6461 This should be set to a list that contains whatever the print command | |
| 6462 requires to do its job. Something like: | |
| 6463 | |
| 6464 @lisp | |
| 6465 (setq lpr-switches '("-depson")) | |
| 6466 @end lisp | |
| 6467 @end table | |
| 6468 | |
| 6469 For postscript printing there are three analogous variables to | |
| 6470 customize. | |
| 6471 | |
| 6472 @table @code | |
| 6473 @item ps-lpr-command | |
| 6474 This should be set to a command that takes postscript on standard input | |
| 6475 and directs it to a postscript printer. | |
| 6476 | |
| 6477 @item ps-lpr-switches | |
| 6478 This should be set to a list of switches required for | |
| 6479 @code{ps-lpr-command} to do its job. | |
| 6480 | |
| 6481 @item ps-print-color-p | |
| 6482 This boolean variable should be set @code{t} if printing will be done in | |
| 6483 color, otherwise it should be set to @code{nil}. | |
| 6484 @end table | |
| 6485 | |
| 6486 NOTE: It is an undocumented limitation in XEmacs that postscript | |
| 6487 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a | |
| 6488 window system environment. It cannot be used outside of X11. | |
| 6489 | |
| 2459 | 6490 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems |
| 6491 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer? | |
| 2417 | 6492 |
| 6493 Font-lock looks nice. How can I print (WYSIWYG) the highlighted | |
| 6494 document? | |
| 6495 | |
| 6496 The package @code{ps-print}, which is now included with XEmacs, provides | |
| 6497 the ability to do this. The source code contains complete instructions | |
| 6498 on its use, in | |
| 6499 @file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el}, | |
| 6500 being the default location of an installed ps-print package. | |
| 6501 | |
| 2459 | 6502 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems |
| 6503 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 2417 | 6504 |
| 6505 My printer is a Postscript printer and @code{lpr} only works for | |
| 6506 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x | |
| 6507 lpr-buffer} to work? | |
| 6508 | |
| 6509 Put something like this in your @file{init.el}: | |
| 428 | 6510 |
| 6511 @lisp | |
| 2417 | 6512 (setq lpr-command "a2ps") |
| 6513 (setq lpr-switches '("-p" "-1")) | |
| 6514 @end lisp | |
| 6515 | |
| 6516 If you don't use a2ps to convert ASCII to postscript (why not, it's | |
| 6517 free?), replace with the command you do use. Note also that some | |
| 6518 versions of a2ps require a @samp{-Pprinter} to ensure spooling. | |
| 6519 | |
| 2459 | 6520 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems |
| 6521 @unnumberedsubsec Q5.2.4: Can you print under MS Windows? | |
| 2417 | 6522 |
| 6523 As of 21.4, printing works on Windows, using simply | |
| 6524 @samp{File->Print BUFFER...}, and can be configured with | |
| 6525 @samp{File->Page Setup...}. | |
| 6526 | |
| 6527 Prior to 21.4, there is no built-in support, but there are some clever | |
| 6528 hacks out there. If you know how, please let us know and we'll put it | |
| 6529 here. | |
| 6530 | |
| 2459 | 6531 @unnumberedsec 5.3: Sound |
| 6532 | |
| 6533 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems | |
| 6534 @unnumberedsubsec Q5.3.1: How do I turn off the sound? | |
| 2417 | 6535 |
| 6536 Add the following line to your @file{init.el}: | |
| 6537 | |
| 6538 @lisp | |
| 6539 (setq bell-volume 0) | |
| 6540 (setq sound-alist nil) | |
| 6541 @end lisp | |
| 6542 | |
| 6543 That will make your XEmacs totally silent---even the default ding sound | |
| 6544 (TTY beep on TTY-s) will be gone. | |
| 6545 | |
| 6546 You can also change these with Customize. Select from the | |
| 6547 @code{Options} menu @code{Advanced | |
| 6548 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x | |
| 6549 customize @key{RET} sound @key{RET}}. | |
| 6550 | |
| 6551 | |
| 2459 | 6552 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems |
| 6553 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep? | |
| 2417 | 6554 |
| 6555 Make sure your XEmacs was compiled with sound support, and then put this | |
| 6556 in your @file{init.el}: | |
| 6557 | |
| 6558 @lisp | |
| 6559 (load-default-sounds) | |
| 6560 @end lisp | |
| 6561 | |
| 2459 | 6562 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems |
| 6563 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)? | |
| 6564 | |
| 6565 @dfn{Network Audio System} (NAS) is a client-server sound library for X. | |
| 6566 | |
| 6567 @uref{http://radscan.com/nas.html}. | |
| 6568 | |
| 3018 | 6569 To build XEmacs with it, use the @file{configure} flag |
| 6570 @samp{--with-sound=nas} (@samp{--enable-sound=nas} in 21.5 or later). | |
| 2459 | 6571 |
| 6572 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system. | |
| 6573 | |
| 6574 @uref{http://www.tux.org/~ricdude/EsounD.html}. | |
| 6575 | |
| 3018 | 6576 To build XEmacs with it, use the @file{configure} flag |
| 6577 @samp{--with-sound=esd} (@samp{--enable-sound=esd} in 21.5 or later). | |
| 6578 | |
| 6579 You can specify support for both with a flag like | |
| 6580 @samp{--with-sound=nas,esd} (@samp{--enable-sound=nas,esd} in 21.5 or | |
| 6581 later). | |
| 2459 | 6582 |
| 6583 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems | |
| 6584 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play. | |
| 2417 | 6585 |
| 6586 I'm having some trouble with sounds I've downloaded from sunsite. They | |
| 6587 play when I run them through @code{showaudio} or cat them directly to | |
| 6588 @file{/dev/audio}, but XEmacs refuses to play them. | |
| 6589 | |
| 6590 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes: | |
| 6591 | |
| 6592 @quotation | |
| 6593 [Many of] These files have an (erroneous) 24byte header that tells about | |
| 6594 the format that they have been recorded in. If you cat them to | |
| 6595 @file{/dev/audio}, the header will be ignored and the default behavior | |
| 6596 for /dev/audio will be used. This happens to be 8kHz uLaw. It is | |
| 6597 probably possible to fix the header by piping through @code{sox} and | |
| 6598 passing explicit parameters for specifying the sampling format; you then | |
| 6599 need to perform a 'null' conversion from SunAudio to SunAudio. | |
| 6600 @end quotation | |
| 6601 | |
| 2459 | 6602 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses |
| 6603 | |
| 6604 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems | |
| 6605 @unnumberedsubsec Q5.4.1: What is an interior shell? | |
| 2417 | 6606 |
| 6607 #### Write me. | |
| 6608 | |
| 2459 | 6609 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems |
| 6610 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer? | |
| 2417 | 6611 |
| 6612 In the @code{*shell*} buffer: | |
| 6613 | |
| 6614 @lisp | |
| 6615 M-x rename-buffer @key{RET} *shell-1* @key{RET} | |
| 6616 M-x shell RET | |
| 6617 @end lisp | |
| 6618 | |
| 6619 This will then start a second shell. The key is that no buffer named | |
| 6620 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x | |
| 6621 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x | |
| 6622 rename-buffer}. | |
| 6623 | |
| 6624 Alternately, you can set the variable @code{shell-multiple-shells}. | |
| 6625 If the value of this variable is non-nil, each time shell mode is invoked, | |
| 6626 a new shell is made | |
| 6627 | |
| 2459 | 6628 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems |
| 6629 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much | |
| 2417 | 6630 |
| 6631 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke | |
| 6632 and use a telnet session within it. Everything works fine except that | |
| 6633 now all @samp{^M}'s are filtered out by Emacs. Fixes? | |
| 6634 | |
| 6635 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather | |
| 6636 than doing rsh or telnet within the local shell buffer. You can also | |
| 6637 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh} | |
| 6638 installed. | |
| 6639 | |
| 2459 | 6640 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems |
| 6641 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode. | |
| 2417 | 6642 |
| 6643 Sometimes (i.e. it's not repeatable, and I can't work out why it | |
| 6644 happens) when I'm typing into shell mode, I hit return and only a | |
| 6645 portion of the command is given to the shell, and a blank prompt is | |
| 6646 returned. If I hit return again, the rest of the previous command is | |
| 6647 given to the shell. | |
| 6648 | |
| 6649 @email{martin@@xemacs.org, Martin Buchholz} writes: | |
| 6650 | |
| 6651 @quotation | |
| 6652 There is a known problem with interaction between @code{csh} and the | |
| 6653 @code{filec} option and XEmacs. You should add the following to your | |
| 6654 @file{.cshrc}: | |
| 6655 | |
| 6656 @example | |
| 6657 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec | |
| 6658 @end example | |
| 6659 @end quotation | |
| 6660 | |
| 2995 | 6661 @node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems |
| 2459 | 6662 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff" |
| 2417 | 6663 |
| 6664 or "ispell" or other commands that seem related to whatever you just | |
| 6665 tried to do (M-x ediff or M-$, for example). | |
| 6666 | |
| 6667 There are a large number of common (in the sense that "everyone has | |
| 6668 these, they really do") Unix utilities that are not provided with | |
| 6669 XEmacs. The GNU Project's implementations are available for Windows in | |
| 6670 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also | |
| 6671 provides a complete Unix emulation environment (and thus makes ports of | |
| 6672 Unix utilities nearly trivial). Another implementation is that from | |
| 6673 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others, | |
| 6674 please let us know! | |
| 6675 | |
| 2995 | 6676 @node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems |
| 6677 @unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed" | |
| 6678 | |
| 6679 If you are getting an error like | |
| 6680 | |
| 6681 @example | |
| 6682 17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed, | |
| 6683 0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487 | |
| 6684 bash: fork: resource temporarily unavailable | |
| 6685 @end example | |
| 6686 | |
| 6687 when trying to run bash using @kbd{M-x shell}, then you need to rebase | |
| 6688 your Cygwin DLL's. This is a known problem with Cygwin. To fix: | |
| 6689 | |
| 6690 @enumerate | |
| 6691 @item | |
| 6692 Download the @file{rebase} utility from Cygwin setup (it's under | |
| 6693 @samp{System}). | |
| 6694 @item | |
| 6695 Kill @strong{all} of your Cygwin processes, including all of your | |
| 6696 shells and all background processes. Use @code{ps -a} to list all the | |
| 6697 processes you need to kill. | |
| 6698 @item | |
| 6699 From a DOS prompt, run @file{ash} (@strong{not} @file{bash}, | |
| 6700 @file{tcsh} or @file{zsh}). Do not try to be clever and @code{exec | |
| 6701 /bin/ash} from your last shell; it won't work. | |
| 6702 @item | |
| 6703 Type @code{/bin/rebaseall -v}. | |
| 6704 @end enumerate | |
| 6705 | |
| 6706 The problem should now be fixed -- at least, until you install another | |
| 6707 Cygwin package with DLL's, in which case you may have to repeat the | |
| 6708 procedure. | |
| 6709 | |
| 2459 | 6710 @unnumberedsec 5.5: Multiple Device Support |
| 6711 | |
| 2995 | 6712 @node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems |
| 2459 | 6713 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display? |
| 2417 | 6714 |
| 6715 Use the command @kbd{M-x make-frame-on-display}. This command is also | |
| 6716 on the File menu in the menubar. | |
| 6717 | |
| 6718 The command @code{make-frame-on-tty} also exists, which will establish a | |
| 6719 connection to any tty-like device. Opening the TTY devices should be | |
| 6720 left to @code{gnuclient}, though. | |
| 6721 | |
| 2459 | 6722 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems |
| 6723 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 6724 | |
| 6725 Yes. Use @code{gnuclient -nw}. | |
| 6726 | |
| 6727 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}. | |
| 6728 | |
| 6729 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems | |
| 6730 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame? | |
| 2417 | 6731 |
| 6732 If you set the @code{gnuserv-frame} variable to the frame that should be | |
| 6733 used to display buffers that are pulled up, a new frame will not be | |
| 6734 created. For example, you could put | |
| 6735 | |
| 6736 @lisp | |
| 6737 (setq gnuserv-frame (selected-frame)) | |
| 428 | 6738 @end lisp |
| 6739 | |
| 2417 | 6740 early on in your @file{init.el}, to ensure that the first frame created |
| 6741 is the one used for your gnuserv buffers. | |
| 6742 | |
| 6743 There is an option to set the gnuserv target to the current frame. See | |
| 6744 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target} | |
| 6745 | |
| 6746 You can also change this with Customize. Select from the | |
| 6747 @code{Options} menu @code{Advanced | |
| 6748 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type | |
| 6749 @kbd{M-x customize @key{RET} gnuserv @key{RET}}. | |
| 6750 | |
| 6751 | |
| 2459 | 6752 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems |
| 6753 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 2417 | 6754 |
| 6755 Put the following in your @file{init.el} file to start the server: | |
| 6756 | |
| 6757 @lisp | |
| 6758 (gnuserv-start) | |
| 6759 @end lisp | |
| 6760 | |
| 6761 Start your first XEmacs as usual. After that, you can do: | |
| 6762 | |
| 6763 @example | |
| 6764 gnuclient randomfilename | |
| 6765 @end example | |
| 6766 | |
| 6767 from the command line to get your existing XEmacs process to open a new | |
| 6768 frame and visit randomfilename in that window. When you're done editing | |
| 6769 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the | |
| 6770 frame. | |
| 6771 | |
| 6772 See also man page of gnuclient. | |
| 6773 | |
| 2459 | 6774 @node Q5.5.5, , Q5.5.4, External Subsystems |
| 6775 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 2417 | 6776 |
| 6777 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes: | |
| 6778 @quotation | |
| 6779 Here is one of the solutions, we have this in a script called | |
| 6780 @file{etc/editclient.sh}. | |
| 6781 @example | |
| 6782 #!/bin/sh | |
| 6783 if gnuclient -batch -eval t >/dev/null 2>&1 | |
| 6784 then | |
| 6785 exec gnuclient $@{1+"$@@"@} | |
| 6786 else | |
| 6787 xemacs -unmapped -f gnuserv-start & | |
| 6788 until gnuclient -batch -eval t >/dev/null 2>&1 | |
| 6789 do | |
| 6790 sleep 1 | |
| 6791 done | |
| 6792 exec gnuclient $@{1+"$@@"@} | |
| 6793 fi | |
| 6794 @end example | |
| 6795 | |
| 6796 Note that there is a known problem when running XEmacs and 'gnuclient | |
| 6797 -nw' on the same TTY. | |
| 6798 @end quotation | |
| 6799 | |
| 2459 | 6800 @node Internet, Advanced, External Subsystems, Top |
| 6801 @unnumbered 6 Connecting to the Internet | |
| 6802 | |
| 6803 This is part 6 of the XEmacs Frequently Asked Questions list. This | |
| 6804 section is devoted connecting to the Internet. | |
| 6805 | |
| 6806 @menu | |
| 6807 6.0: General Mail and News | |
| 6808 * Q6.0.1:: What are the various packages for reading mail? | |
| 6809 * Q6.0.2:: How can I send mail? | |
| 6810 * Q6.0.3:: How do I get my outgoing mail archived? | |
| 6811 * Q6.0.4:: How can I read and/or compose MIME messages? | |
| 6812 * Q6.0.5:: How do I customize the From line? | |
| 6813 * Q6.0.6:: How do I get my MUA to filter mail for me? | |
| 6814 * Q6.0.7:: Remote mail reading with an MUA. | |
| 6815 * Q6.0.8:: An MUA gets an error incorporating new mail. | |
| 6816 * Q6.0.9:: Why isn't @file{movemail} working? | |
| 6817 * Q6.0.10:: How do I make my MUA display graphical smilies? | |
| 6818 * Q6.0.11:: How can I get those oh-so-neat X-Face lines? | |
| 6819 | |
| 6820 6.1: Reading Mail with VM | |
| 6821 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP? | |
| 6822 * Q6.1.2:: How can I get VM to automatically check for new mail? | |
| 6823 * 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"? | |
| 6824 * Q6.1.4:: Is there a mailing list or FAQ for VM? | |
| 6825 * Q6.1.5:: How do I make VM stay in a single frame? | |
| 6826 * Q6.1.6:: Customization of VM not covered in the manual, or here. | |
| 6827 | |
| 6828 6.2: Reading Netnews and Mail with Gnus | |
| 6829 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 6830 * Q6.2.2:: How do I make Gnus stay within a single frame? | |
| 6831 | |
| 6832 6.3: FTP Access | |
| 6833 * Q6.3.1:: Can I edit files on other hosts? | |
| 6834 * Q6.3.2:: What is EFS? | |
| 6835 | |
| 6836 6.4: Web Browsing with W3 | |
| 6837 * Q6.4.1:: What is W3? | |
| 6838 * Q6.4.2:: How do I run W3 from behind a firewall? | |
| 6839 * Q6.4.3:: Is it true that W3 supports style sheets and tables? | |
| 6840 @end menu | |
| 6841 | |
| 6842 @unnumberedsec 6.0: General Mail and News | |
| 6843 | |
| 6844 @node Q6.0.1, Q6.0.2, Internet, Internet | |
| 6845 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail? | |
| 6846 | |
| 6847 #### Write me. | |
| 6848 | |
| 6849 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet | |
| 6850 @unnumberedsubsec Q6.0.2: How can I send mail? | |
| 6851 | |
| 6852 Under Unix and Mac OS X, the @samp{sendmail} package is normally used | |
| 6853 for this. | |
| 6854 #### Write me. | |
| 6855 | |
| 6856 Under Windows, you need to use @samp{smtpmail}, which communicates | |
| 6857 directly with the mail server, as there is no @file{sendmail} program | |
| 6858 running. To get it working, use code like the following in your | |
| 6859 @file{init.el} file: | |
| 6860 | |
| 6861 @lisp | |
| 6862 ;; Get mail working under Windows. | |
| 6863 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus | |
| 6864 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc. | |
| 6865 ;; the following ensures that mail problems can be debugged: it logs a trace | |
| 6866 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*. | |
| 6867 (setq smtpmail-debug-info t) | |
| 6868 ;; Substitute your info here. | |
| 6869 ;(setq user-mail-address "ben@@xemacs.org") | |
| 6870 ;(setq user-full-name "Ben Wing") | |
| 6871 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com") | |
| 6872 ;; The following two aren't completely necessary but may help. | |
| 6873 ;(setq smtpmail-local-domain "666.com") | |
| 6874 ;(setq smtpmail-sendto-domain "666.com") | |
| 6875 ;; If your SMTP server requires a username/password to authenticate, as | |
| 6876 ;; many do nowadays, set them like this: | |
| 6877 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo | |
| 6878 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD"))) | |
| 6879 | |
| 6880 ;; Other possibilities for getting smtpmail to work: | |
| 6881 ;; | |
| 6882 ;; If for some reason you need to authenticate using the STARTTLS protocol | |
| 6883 ;; (don't look into this unless you know what it is), use | |
| 6884 ;; (setq smtpmail-starttls-credentials | |
| 6885 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert"))) | |
| 6886 ;; Requires external program | |
| 6887 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz. | |
| 6888 ;; See http://www.ietf.org/rfc/rfc2246.txt, | |
| 6889 ;; http://www.ietf.org/rfc/rfc2487.txt | |
| 6890 @end lisp | |
| 6891 | |
| 6892 The lines you need to care about are those that set | |
| 6893 @code{user-mail-address}, @code{user-full-name}, | |
| 6894 @code{smtpmail-default-smtp-server}, and | |
| 6895 @code{smtpmail-auth-credentials}. You need to set these with, | |
| 6896 respectively, your email address, your full name, the SMTP server you | |
| 6897 use for outgoing mail, and the username and password you need to log | |
| 6898 in to your SMTP server. (If for some reason your SMTP server doesn't | |
| 6899 require logging in to send mail, don't uncomment this last line.) | |
| 6900 | |
| 6901 The other settings may be useful in specific cases, but you should know what | |
| 6902 you're doing before enabling them. | |
| 6903 | |
| 6904 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet | |
| 6905 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived? | |
| 6906 | |
| 6907 @lisp | |
| 6908 (setq mail-archive-file-name "~/outbox") | |
| 6909 @end lisp | |
| 6910 | |
| 6911 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet | |
| 6912 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages? | |
| 6913 | |
| 6914 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not | |
| 6915 have MIME support; refer to their documentation and other resources, | |
| 6916 such as web pages and mailing lists. Packages like SEMI/WEMI may be | |
| 6917 useful in connection with MUAs like mew and Wanderlust. | |
| 6918 | |
| 6919 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet | |
| 6920 @unnumberedsubsec Q6.0.5: How do I customize the From line? | |
| 6921 | |
| 6922 How do I change the @samp{From:} line? I have set gnus-user-from-line | |
| 6923 to | |
| 6924 @example | |
| 6925 Gail Gurman <gail.gurman@@sybase.com> | |
| 6926 @end example | |
| 6927 @noindent , but XEmacs Gnus doesn't use | |
| 6928 it. [This should apply to all MUA's. --ed] Instead it uses | |
| 6929 @example | |
| 6930 Gail Mara Gurman @email{gailg@@deall} | |
| 6931 @end example | |
| 6932 @noindent and then complains | |
| 6933 that it's incorrect. Also, as you perhaps can see, my Message-ID is | |
| 6934 screwy. How can I change that? | |
| 6935 | |
| 6936 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes: | |
| 6937 | |
| 6938 @quotation | |
| 6939 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or | |
| 6940 @code{mail-host-address} to @samp{sybase.com}. | |
| 6941 @end quotation | |
| 6942 | |
| 6943 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet | |
| 6944 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me? | |
| 6945 | |
| 6946 One possibility is to use procmail to split your mail before it gets to | |
| 6947 the MUA. I prefer this personally, since there are many strange and | |
| 6948 wonderful things one can do with procmail. Procmail may be found at | |
| 6949 @uref{http://www.procmail.org/}. | |
| 6950 | |
| 6951 Also see the Mail Filtering FAQ at: | |
| 6952 @iftex | |
| 6953 @* | |
| 6954 @end iftex | |
| 6955 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}. | |
| 6956 | |
| 6957 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet | |
| 6958 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA. | |
| 6959 | |
| 6960 My mailbox lives at the office on a big honkin server. My regular INBOX | |
| 6961 lives on my honkin desktop machine. I now can PPP to the office from | |
| 6962 home which is far from honking... I'd like to be able to read mail at | |
| 6963 home without storing it here and I'd like to use xemacs and the MUA at | |
| 6964 home... Is there a recommended setup? | |
| 6965 | |
| 6966 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes: | |
| 6967 | |
| 6968 @quotation | |
| 6969 There are several ways to do this. | |
| 6970 | |
| 6971 @enumerate | |
| 6972 @item | |
| 6973 Set your display to your home machine and run dxpc or one of the other X | |
| 6974 compressors. | |
| 6975 | |
| 6976 @item | |
| 6977 NFS mount your desktop machine on your home machine and modify your pop | |
| 6978 command on your home machine to rsh to your desktop machine and actually | |
| 6979 do the pop get's. | |
| 6980 | |
| 6981 @item | |
| 6982 Run a POP server on your desktop machine as well and do a sort of two | |
| 6983 tiered POP get. | |
| 6984 @end enumerate | |
| 6985 @end quotation | |
| 6986 | |
| 6987 @email{wmperry@@monolith.spry.com, William Perry} adds: | |
| 6988 | |
| 6989 @quotation | |
| 6990 Or you could run a pop script periodically on your desktop machine, and | |
| 6991 just use ange-ftp or NFS to get to your mailbox. I used to do this all | |
| 6992 the time back at IU. | |
| 6993 @end quotation | |
| 6994 | |
| 6995 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet | |
| 6996 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail. | |
| 6997 | |
| 6998 rmail and VM, and probably other MUA's as well, get new mail from | |
| 6999 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER} | |
| 7000 or something similar) using a program called @code{movemail}. | |
| 7001 This program interlocks with @code{/bin/mail} using the protocol | |
| 7002 defined by @code{/bin/mail}. | |
| 7003 | |
| 7004 There are various different protocols in general use, which you need to | |
| 3018 | 7005 specify using the @samp{--mail-locking} option |
| 7006 (@samp{--with-mail-locking} in 21.5 or later) to @file{configure}: | |
| 2459 | 7007 |
| 7008 @table @samp | |
| 7009 @item lockf | |
| 7010 POSIX file locking with @code{lockf()} | |
| 7011 @item flock | |
| 7012 BSD file locking with @code{flock()} | |
| 7013 @item dot | |
| 7014 To manipulate mail file @file{foo}, first create file @file{foo.lock} | |
| 7015 @item locking | |
| 7016 Use @code{locking()}, Microsoft's renamed @code{flock()} | |
| 7017 @item mmdf | |
| 7018 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel | |
| 7019 Memo Distribution Facility | |
| 7020 @item pop | |
| 7021 Retrieve mail using POP (the Post Office Protocol). This is the | |
| 7022 default for Cygwin/MinGW. | |
| 7023 @end table | |
| 7024 | |
| 7025 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR | |
| 7026 SYSTEM, YOU CAN LOSE MAIL!} | |
| 7027 | |
| 7028 Usually the value is correctly determined automatically: | |
| 7029 @file{configure} tries to detect the method in use, and defaults exist | |
| 7030 on systems for which this doesn't work. | |
| 7031 | |
| 7032 However, if you run into problems incorporating new mail, it may be | |
| 7033 because an incorrect method is being used. | |
| 7034 | |
| 7035 If your system uses the lock file protocol, and permissions are set | |
| 7036 so that ordinary users cannot write lock files in the mail spool | |
| 7037 directory, you may need to make @file{movemail} setgid to a | |
| 7038 suitable group such as @samp{mail}. You can use these commands (as | |
| 7039 root): | |
| 7040 | |
| 7041 @example | |
| 7042 chgrp mail movemail | |
| 7043 chmod 2755 movemail | |
| 7044 @end example | |
| 7045 | |
| 7046 If you are using the @samp{pop} locking method, @file{movemail} must | |
| 7047 be setuid root. | |
| 7048 | |
| 7049 Installation normally copies movemail from the build directory to an | |
| 7050 installation directory which is usually under @file{/usr/local/lib}. | |
| 7051 The installed copy of @file{movemail} is usually in the directory | |
| 7052 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example, | |
| 7053 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change | |
| 7054 the group and mode of the installed copy; changing the group and mode | |
| 7055 of the build directory copy is ineffective. | |
| 7056 | |
| 7057 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet | |
| 7058 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working? | |
| 7059 | |
| 7060 @xref{Q6.0.8}. | |
| 7061 | |
| 7062 Note also that older versions of Mozilla came with a @file{movemail} | |
| 7063 program that is @strong{not} compatible with XEmacs. Do not use it. | |
| 7064 Always use the @file{movemail} installed with your XEmacs. Failure to | |
| 7065 do so can result in lost mail. | |
| 7066 | |
| 7067 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet | |
| 7068 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies? | |
| 7069 For mh-e use the following: | |
| 7070 | |
| 7071 @lisp | |
| 7072 (add-hook 'mh-show-mode-hook '(lambda () | |
| 7073 (smiley-region (point-min) | |
| 7074 (point-max)))) | |
| 7075 @end lisp | |
| 7076 | |
| 7077 @email{bill@@carpenter.ORG, WJCarpenter} writes: | |
| 7078 For VM use the following: | |
| 7079 @lisp | |
| 7080 (autoload 'smiley-region "smiley" nil t) | |
| 7081 (add-hook 'vm-select-message-hook | |
| 7082 '(lambda () | |
| 7083 (smiley-region (point-min) | |
| 7084 (point-max)))) | |
| 7085 @end lisp | |
| 7086 | |
| 7087 For tm use the following: | |
| 7088 @lisp | |
| 7089 (autoload 'smiley-buffer "smiley" nil t) | |
| 7090 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer) | |
| 7091 @end lisp | |
| 7092 | |
| 7093 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet | |
| 7094 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines? | |
| 7095 | |
| 7096 Firstly there is an ftp site which describes X-faces and has the | |
| 7097 associated tools mentioned below, at | |
| 7098 @uref{http://ftp.cs.indiana.edu/pub/faces/}. | |
| 7099 | |
| 7100 Then the steps are | |
| 7101 | |
| 7102 @enumerate | |
| 7103 @item | |
| 7104 Create 48x48x1 bitmap with your favorite tool | |
| 7105 | |
| 7106 @item | |
| 7107 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc., | |
| 7108 and then compile the face. | |
| 7109 | |
| 7110 @item | |
| 7111 @example | |
| 7112 cat file.xbm | xbm2ikon |compface > file.face | |
| 7113 @end example | |
| 7114 | |
| 7115 @item | |
| 7116 Then be sure to quote things that are necessary for emacs strings: | |
| 7117 | |
| 7118 @example | |
| 7119 cat ./file.face | sed 's/\\/\\\\/g' | |
| 7120 @iftex | |
| 7121 \ @* | |
| 7122 @end iftex | |
| 7123 | sed 's/\"/\\\"/g' > ./file.face.quoted | |
| 7124 @end example | |
| 7125 | |
| 7126 @item | |
| 7127 Then set up emacs to include the file as a mail header - there were a | |
| 7128 couple of suggestions here---either something like: | |
| 7129 | |
| 7130 @lisp | |
| 7131 (setq mail-default-headers | |
| 7132 "X-Face: @email{Ugly looking text string here}") | |
| 7133 @end lisp | |
| 7134 | |
| 7135 Or, alternatively, as: | |
| 7136 | |
| 7137 @lisp | |
| 7138 (defun mail-insert-x-face () | |
| 7139 (save-excursion | |
| 7140 (goto-char (point-min)) | |
| 7141 (search-forward mail-header-separator) | |
| 7142 (beginning-of-line) | |
| 7143 (insert "X-Face:") | |
| 7144 (insert-file-contents "~/.face"))) | |
| 7145 | |
| 7146 (add-hook 'mail-setup-hook 'mail-insert-x-face) | |
| 7147 @end lisp | |
| 7148 @end enumerate | |
| 7149 | |
| 7150 However, 2 things might be wrong: | |
| 7151 | |
| 7152 Some versions of pbmtoicon produces some header lines that is not | |
| 7153 expected by the version of compface that I grabbed. So I found I had to | |
| 7154 include a @code{tail +3} in the pipeline like this: | |
| 7155 | |
| 7156 @example | |
| 7157 cat file.xbm | xbm2ikon | tail +3 |compface > file.face | |
| 7158 @end example | |
| 7159 | |
| 7160 Some people have also found that if one uses the @code{(insert-file)} | |
| 7161 method, one should NOT quote the face string using the sed script . | |
| 7162 | |
| 7163 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script | |
| 7164 xbm2face (included in the compface distribution at XEmacs.org) to do the | |
| 7165 conversion. | |
| 7166 | |
| 7167 Contributors for this item: | |
| 7168 | |
| 7169 Paul Emsley, | |
| 7170 Ricardo Marek, | |
| 7171 Amir J. Katz, | |
| 7172 Glen McCort, | |
| 7173 Heinz Uphoff, | |
| 7174 Peter Arius, | |
| 7175 Paul Harrison, and | |
| 7176 Vegard Vesterheim | |
| 7177 | |
| 7178 @unnumberedsec 6.1: Reading Mail with VM | |
| 7179 | |
| 7180 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet | |
| 7181 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP? | |
| 7182 | |
| 7183 Use @code{vm-spool-files}, like this for example: | |
| 7184 | |
| 7185 @lisp | |
| 7186 (setq vm-spool-files '("/var/spool/mail/wing" | |
| 7187 "netcom23.netcom.com:110:pass:wing:MYPASS")) | |
| 7188 @end lisp | |
| 7189 | |
| 7190 Of course substitute your actual password for MYPASS. | |
| 7191 | |
| 7192 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet | |
| 7193 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail? | |
| 7194 | |
| 7195 @email{turner@@lanl.gov, John Turner} writes: | |
| 7196 | |
| 7197 @quotation | |
| 7198 Use the following: | |
| 7199 | |
| 7200 @lisp | |
| 7201 (setq vm-auto-get-new-mail 60) | |
| 7202 @end lisp | |
| 7203 @end quotation | |
| 7204 | |
| 7205 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet | |
| 7206 @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"? | |
| 7207 | |
| 7208 Set @code{vm-reply-ignored-addresses} to a list, like | |
| 7209 | |
| 7210 @lisp | |
| 7211 (setq vm-reply-ignored-addresses | |
| 7212 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com" | |
| 7213 "wing@@netcom.com" "wing@@xemacs.org")) | |
| 7214 @end lisp | |
| 7215 | |
| 7216 Note that each string is a regular expression. | |
| 7217 | |
| 7218 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet | |
| 7219 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM? | |
| 7220 | |
| 7221 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}. | |
| 7222 | |
| 7223 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug. | |
| 7224 | |
| 7225 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet | |
| 7226 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame? | |
| 7227 | |
| 7228 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes: | |
| 7229 | |
| 7230 @quotation | |
| 7231 @lisp | |
| 7232 ; Don't use multiple frames | |
| 7233 (setq vm-frame-per-composition nil) | |
| 7234 (setq vm-frame-per-folder nil) | |
| 7235 (setq vm-frame-per-edit nil) | |
| 7236 (setq vm-frame-per-summary nil) | |
| 7237 @end lisp | |
| 7238 @end quotation | |
| 7239 | |
| 7240 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet | |
| 7241 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here. | |
| 7242 | |
| 4311 | 7243 @email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} writes: |
| 2459 | 7244 |
| 7245 @quotation | |
| 7246 The meta-answer is to look into the file @file{vm-vars.el}, in the vm | |
| 7247 directory of the lisp library. | |
| 7248 | |
| 7249 @file{vm-vars.el} contains, initializes and carefully describes, with | |
| 7250 examples of usage, the plethora of user options that @emph{fully} | |
| 7251 control VM's behavior. | |
| 7252 | |
| 7253 Enter vm-vars, @code{forward-search} for toolbar, find the variables | |
| 7254 that control the toolbar placement, appearance, existence, copy to your | |
| 7255 @file{init.el} or @file{.vm} and modify according to the | |
| 7256 detailed instructions. | |
| 7257 | |
| 7258 The above also applies to all the various features of VM: search for | |
| 7259 some keywords, maybe the first you conjure isn't appropriate, find the | |
| 7260 appropriate variables, copy and experiment. | |
| 7261 @end quotation | |
| 7262 | |
| 7263 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus | |
| 7264 | |
| 7265 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet | |
| 7266 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 7267 | |
| 7268 The Gnus numbering issues are not meant for mere mortals to know them. | |
| 7269 If you feel you @emph{must} enter the muddy waters of Gnus, visit the | |
| 7270 excellent FAQ, maintained by Justin Sheehy, at: | |
| 7271 | |
| 7272 @example | |
| 7273 @uref{http://my.gnus.org/FAQ/} | |
| 7274 @end example | |
| 7275 | |
| 7276 See also Gnus home page | |
| 7277 @example | |
| 7278 @uref{http://www.gnus.org/} | |
| 7279 @end example | |
| 7280 | |
| 7281 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet | |
| 7282 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame? | |
| 7283 | |
| 7284 The toolbar code to start Gnus opens the new frame---and it's a feature | |
| 7285 rather than a bug. If you don't like it, but would still like to click | |
| 7286 on the seemly icon, use the following code: | |
| 7287 | |
| 7288 @lisp | |
| 7289 (defun toolbar-news () | |
| 7290 (gnus)) | |
| 7291 @end lisp | |
| 7292 | |
| 7293 It will redefine the callback function of the icon to just call | |
| 7294 @code{gnus}, without all the fancy frame stuff. | |
| 7295 | |
| 7296 @unnumberedsec 6.3: FTP Access | |
| 7297 | |
| 7298 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet | |
| 7299 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts? | |
| 7300 | |
| 7301 Yes. Of course XEmacs can use any network file system (such as NFS or | |
| 7302 Windows file sharing) you have available, and includes some | |
| 7303 optimizations and safety features appropriate to those environments. | |
| 7304 | |
| 7305 It is also possible to transparently edit files via FTP, ssh, or rsh. That | |
| 7306 is, XEmacs makes a local copy using the transport in the background, and | |
| 7307 automatically refreshes the remote original from that copy when you save | |
| 7308 it. XEmacs also is capable of doing file system manipulations like | |
| 7309 creating and removing directories and files. The FTP interface is | |
| 7310 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The | |
| 7311 ssh/rsh interface is provided by the optional @samp{tramp} package | |
| 7312 @ref{Top, TRAMP, , tramp}. | |
| 7313 | |
| 7314 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet | |
| 7315 @unnumberedsubsec Q6.3.2: What is EFS? | |
| 7316 | |
| 7317 #### Write me. | |
| 7318 | |
| 7319 @unnumberedsec 6.4: Web Browsing with W3 | |
| 7320 | |
| 7321 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet | |
| 7322 @unnumberedsubsec Q6.4.1: What is W3? | |
| 7323 | |
| 7324 W3 is an advanced graphical browser written in Emacs lisp that runs on | |
| 7325 XEmacs. It has full support for cascaded style sheets, and more... | |
| 7326 | |
| 7327 It has a home web page at | |
| 7328 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}. | |
| 7329 | |
| 7330 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet | |
| 7331 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall? | |
| 7332 | |
| 7333 There is a long, well-written, detailed section in the W3 manual that | |
| 7334 describes how to do this. Look in the section entitled "Firewalls". | |
| 7335 | |
| 7336 @node Q6.4.3, , Q6.4.2, Internet | |
| 7337 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables? | |
| 7338 | |
| 7339 Yes, and much more. W3, as distributed with the latest XEmacs is a | |
| 7340 full-featured web browser. | |
| 7341 | |
| 7342 @node Advanced, Other Packages, Internet, Top | |
| 7343 @unnumbered 7 Advanced Customization Using XEmacs Lisp | |
| 7344 | |
| 7345 This is part 7 of the XEmacs Frequently Asked Questions list. This | |
| 7346 section is devoted to advanced customization using XEmacs Lisp. | |
| 7347 | |
| 7348 @menu | |
| 2537 | 7349 7.0: Emacs Lisp and @file{init.el} |
| 7350 * Q7.0.1:: What version of Emacs am I running? | |
| 7351 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions? | |
| 7352 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. | |
| 7353 * Q7.0.4:: How can I add directories to the @code{load-path}? | |
| 7354 * Q7.0.5:: How to check if a lisp function is defined? | |
| 7355 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? | |
| 7356 | |
| 7357 7.1: Emacs Lisp Programming Techniques | |
| 7358 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 7359 * Q7.1.2:: Can I generate "fake" keyboard events? | |
| 7360 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? | |
| 7361 * Q7.1.4:: What is the performance hit of @code{let}? | |
| 7362 * Q7.1.5:: What is the recommended use of @code{setq}? | |
| 7363 * Q7.1.6:: What is the typical misuse of @code{setq}? | |
| 7364 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down? | |
| 7365 * Q7.1.8:: I like recursion, does it slow things down? | |
| 7366 * Q7.1.9:: How do I put a glyph as annotation in a buffer? | |
| 7367 * Q7.1.10:: @code{map-extents} won't traverse all of my extents! | |
| 7368 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 7369 | |
| 7370 7.2: Mathematics | |
| 7371 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp? | |
| 7372 * Q7.2.2:: XEmacs segfaults when I use very big numbers! | |
| 7373 * Q7.2.3:: Bignums are really slow! | |
| 7374 * Q7.2.4:: Equal bignums don't compare as equal! What gives? | |
| 2459 | 7375 @end menu |
| 7376 | |
| 2537 | 7377 @unnumberedsec 7.0: Emacs Lisp and @file{init.el} |
| 2459 | 7378 |
| 7379 @node Q7.0.1, Q7.0.2, Advanced, Advanced | |
| 2537 | 7380 @unnumberedsubsec Q7.0.1: What version of Emacs am I running? |
| 2459 | 7381 |
| 7382 How can @file{init.el} determine which of the family of | |
| 7383 Emacsen I am using? | |
| 7384 | |
| 7385 To determine if you are currently running GNU Emacs 18, GNU Emacs 19, | |
| 7386 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the | |
| 7387 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in | |
| 7388 XEmacs versions prior to 21.4). There are other nifty things in there | |
| 7389 as well! | |
| 7390 | |
| 7391 For all new code, all you really need to do is: | |
| 7392 | |
| 7393 @lisp | |
| 7394 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version)) | |
| 7395 @end lisp | |
| 7396 | |
| 2537 | 7397 @node Q7.0.2, Q7.0.3, Q7.0.1, Advanced |
| 7398 @unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions? | |
| 2459 | 7399 |
| 7400 I know I can evaluate Elisp expressions from @code{*scratch*} buffer | |
| 7401 with @kbd{C-j} after the expression. How do I do it from another | |
| 7402 buffer? | |
| 7403 | |
| 7404 Press @kbd{M-:} (the default binding of @code{eval-expression}), and | |
| 7405 enter the expression to the minibuffer. | |
| 7406 | |
| 2537 | 7407 @node Q7.0.3, Q7.0.4, Q7.0.2, Advanced |
| 7408 @unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly. | |
| 2459 | 7409 |
| 7410 If you put @code{(setq tab-width 6)} in your | |
| 7411 @file{init.el} file it does not work! Is there a reason | |
| 7412 for this? If you do it at the EVAL prompt it works fine!! How strange. | |
| 7413 | |
| 7414 Use @code{setq-default} instead, since @code{tab-width} is | |
| 7415 all-buffer-local. | |
| 7416 | |
| 2537 | 7417 @node Q7.0.4, Q7.0.5, Q7.0.3, Advanced |
| 7418 @unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}? | |
| 2459 | 7419 |
| 7420 Here are two ways to do that, one that puts your directories at the | |
| 7421 front of the load-path, the other at the end: | |
| 7422 | |
| 7423 @lisp | |
| 7424 ;;; Add things at the beginning of the load-path, do not add | |
| 7425 ;;; duplicate directories: | |
| 7426 (pushnew "bar" load-path :test 'equal) | |
| 7427 | |
| 7428 (pushnew "foo" load-path :test 'equal) | |
| 7429 | |
| 7430 ;;; Add things at the end, unconditionally | |
| 7431 (setq load-path (nconc load-path '("foo" "bar"))) | |
| 7432 @end lisp | |
| 7433 | |
| 4311 | 7434 @email{keithh@@nortel.ca, Keith (k.p.) Hanlan} writes: |
| 2459 | 7435 |
| 7436 @quotation | |
| 7437 To add directories using Unix shell metacharacters use | |
| 7438 @file{expand-file-name} like this: | |
| 7439 | |
| 7440 @lisp | |
| 7441 (push (expand-file-name "~keithh/.emacsdir") load-path) | |
| 7442 @end lisp | |
| 7443 @end quotation | |
| 7444 | |
| 2537 | 7445 @node Q7.0.5, Q7.0.6, Q7.0.4, Advanced |
| 7446 @unnumberedsubsec Q7.0.5: How to check if a lisp function is defined? | |
| 2459 | 7447 |
| 7448 Use the following elisp: | |
| 7449 | |
| 7450 @lisp | |
| 7451 (fboundp 'foo) | |
| 7452 @end lisp | |
| 7453 | |
| 7454 It's almost always a mistake to test @code{emacs-version} or any similar | |
| 7455 variables. | |
| 7456 | |
| 7457 Instead, use feature-tests, such as @code{featurep}, @code{boundp}, | |
| 7458 @code{fboundp}, or even simple behavioral tests, eg.: | |
| 7459 | |
| 7460 @lisp | |
| 7461 (defvar foo-old-losing-code-p | |
| 7462 (condition-case nil (progn (losing-code t) nil) | |
| 7463 (wrong-number-of-arguments t))) | |
| 7464 @end lisp | |
| 7465 | |
| 7466 There is an incredible amount of broken code out there which could work | |
| 7467 much better more often in more places if it did the above instead of | |
| 7468 trying to divine its environment from the value of one variable. | |
| 7469 | |
| 2537 | 7470 @node Q7.0.6, Q7.1.1, Q7.0.5, Advanced |
| 7471 @unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer? | |
| 2459 | 7472 |
| 7473 It would be good having it in a buffer, as the output of | |
| 7474 @code{(face-list)} is too wide to fit to a minibuffer. | |
| 7475 | |
| 7476 Evaluate the expression in the @samp{*scratch*} buffer with point after | |
| 7477 the rightmost paren and typing @kbd{C-j}. | |
| 7478 | |
| 7479 If the minibuffer smallness is the only problem you encounter, you can | |
| 7480 simply press @kbd{C-h l} to get the former minibuffer contents in a | |
| 7481 buffer. | |
| 7482 | |
| 2537 | 7483 @unnumberedsec 7.1: Emacs Lisp Programming Techniques |
| 7484 | |
| 7485 @node Q7.1.1, Q7.1.2, Q7.0.6, Advanced | |
| 7486 @unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 2459 | 7487 |
| 7488 @email{clerik@@naggum.no, Erik Naggum} writes; | |
| 7489 | |
| 7490 @quotation | |
| 7491 Emacs has a legacy of keyboards that produced characters with modifier | |
| 7492 bits, and therefore map a variety of input systems into this scheme even | |
| 7493 today. XEmacs is instead optimized for X events. This causes an | |
| 7494 incompatibility in the way key sequences are specified, but both Emacs | |
| 7495 and XEmacs will accept a key sequence as a vector of lists of modifiers | |
| 7496 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say | |
| 7497 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated | |
| 7498 form for a single key, just (meta control a). Emacs has an abbreviated | |
| 7499 form for the Control and the Meta modifiers to string-characters (the | |
| 7500 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware | |
| 7501 that the abbreviated form works only for one-character key sequences, | |
| 7502 while Emacs users need to be aware that the string-character is rather | |
| 7503 limited. Specifically, the string-character can accommodate only 256 | |
| 7504 different values, 128 of which have the Meta modifier and 128 of which | |
| 7505 have not. In each of these blocks, only 32 characters have the Control | |
| 7506 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta | |
| 7507 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A} | |
| 7508 do not. Programmers are advised to use the full common form, both | |
| 7509 because it is more readable and less error-prone, and because it is | |
| 7510 supported by both Emacsen. | |
| 7511 @end quotation | |
| 7512 | |
| 7513 Another (even safer) way to be sure of the key-sequences is to use the | |
| 7514 @code{read-kbd-macro} function, which takes a string like @samp{C-c | |
| 7515 <up>}, and converts it to the internal key representation of the Emacs | |
| 7516 you use. The function is available both on XEmacs and GNU Emacs. | |
| 7517 | |
| 2537 | 7518 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced |
| 7519 @unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events? | |
| 2459 | 7520 |
| 7521 I wonder if there is an interactive function that can generate | |
| 7522 @dfn{fake} keyboard events. This way, I could simply map them inside | |
| 7523 XEmacs. | |
| 7524 | |
| 7525 This seems to work: | |
| 7526 | |
| 7527 @lisp | |
| 7528 (defun cg--generate-char-event (ch) | |
| 7529 "Generate an event, as if ch has been typed" | |
| 7530 (dispatch-event (character-to-event ch))) | |
| 7531 | |
| 7532 ;; Backspace and Delete stuff | |
| 7533 (global-set-key [backspace] | |
| 7534 (lambda () (interactive) (cg--generate-char-event 127))) | |
| 7535 (global-set-key [unknown_keysym_0x4] | |
| 7536 (lambda () (interactive) (cg--generate-char-event 4))) | |
| 7537 @end lisp | |
| 7538 | |
| 2537 | 7539 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced |
| 7540 @unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail? | |
| 2459 | 7541 |
| 7542 The @code{read-kbd-macro} function returns the internal Emacs | |
| 7543 representation of a human-readable string (which is its argument). | |
| 7544 Thus: | |
| 7545 | |
| 7546 @lisp | |
| 7547 (read-kbd-macro "C-c C-a") | |
| 7548 @result{} [(control ?c) (control ?a)] | |
| 7549 | |
| 7550 (read-kbd-macro "C-c C-. <up>") | |
| 7551 @result{} [(control ?c) (control ?.) up] | |
| 7552 @end lisp | |
| 7553 | |
| 7554 In GNU Emacs the same forms will be evaluated to what GNU Emacs | |
| 7555 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3 | |
| 7556 67108910 up]}, respectively. | |
| 7557 | |
| 7558 The exact @dfn{human-readable} syntax is defined in the docstring of | |
| 7559 @code{edmacro-mode}. I'll repeat it here, for completeness. | |
| 7560 | |
| 7561 @quotation | |
| 7562 Format of keyboard macros during editing: | |
| 7563 | |
| 7564 Text is divided into @dfn{words} separated by whitespace. Except for | |
| 7565 the words described below, the characters of each word go directly as | |
| 7566 characters of the macro. The whitespace that separates words is | |
| 7567 ignored. Whitespace in the macro must be written explicitly, as in | |
| 7568 @kbd{foo @key{SPC} bar @key{RET}}. | |
| 7569 | |
| 7570 @itemize @bullet | |
| 7571 @item | |
| 7572 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD}, | |
| 7573 @kbd{ESC}, and @kbd{NUL} represent special control characters. The | |
| 7574 words must be written in uppercase. | |
| 7575 | |
| 7576 @item | |
| 7577 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or | |
| 7578 @code{<f1>}, represents a function key. (Note that in the standard | |
| 7579 configuration, the function key @code{<return>} and the control key | |
| 7580 @key{RET} are synonymous.) You can use angle brackets on the words | |
| 7581 @key{RET}, @key{SPC}, etc., but they are not required there. | |
| 7582 | |
| 7583 @item | |
| 7584 Keys can be written by their @sc{ascii} code, using a backslash followed | |
| 7585 by up to six octal digits. This is the only way to represent keys with | |
| 7586 codes above \377. | |
| 7587 | |
| 7588 @item | |
| 7589 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-} | |
| 7590 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may | |
| 7591 precede a character or key notation. For function keys, the prefixes | |
| 7592 may go inside or outside of the brackets: @code{C-<down>} @equiv{} | |
| 7593 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x} | |
| 7594 @equiv{} @kbd{C-M-x}. | |
| 7595 | |
| 7596 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except | |
| 7597 that the Meta prefix is allowed on a sequence of digits and optional | |
| 7598 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}. | |
| 7599 | |
| 7600 @item | |
| 7601 The @code{^} notation for control characters also works: @kbd{^M} | |
| 7602 @equiv{} @kbd{C-m}. | |
| 7603 | |
| 7604 @item | |
| 7605 Double angle brackets enclose command names: @code{<<next-line>>} is | |
| 7606 shorthand for @kbd{M-x next-line @key{RET}}. | |
| 7607 | |
| 7608 @item | |
| 7609 Finally, @code{REM} or @code{;;} causes the rest of the line to be | |
| 7610 ignored as a comment. | |
| 7611 @end itemize | |
| 7612 | |
| 7613 Any word may be prefixed by a multiplier in the form of a decimal number | |
| 7614 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>}, | |
| 7615 and @code{10*foo} @equiv{} | |
| 7616 @iftex | |
| 7617 @* | |
| 7618 @end iftex | |
| 7619 @code{foofoofoofoofoofoofoofoofoofoo}. | |
| 7620 | |
| 7621 Multiple text keys can normally be strung together to form a word, but | |
| 7622 you may need to add whitespace if the word would look like one of the | |
| 7623 above notations: @code{; ; ;} is a keyboard macro with three semicolons, | |
| 7624 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but | |
| 7625 @code{\123} is a single key written in octal, and @code{< right >} is | |
| 7626 seven keys but @code{<right>} is a single function key. When in doubt, | |
| 7627 use whitespace. | |
| 7628 @end quotation | |
| 7629 | |
| 2537 | 7630 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced |
| 7631 @unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}? | |
| 2459 | 7632 |
| 7633 In most cases, not noticeable. Besides, there's no avoiding | |
| 7634 @code{let}---you have to bind your local variables, after all. Some | |
| 7635 pose a question whether to nest @code{let}s, or use one @code{let} per | |
| 7636 function. I think because of clarity and maintenance (and possible | |
| 7637 future implementation), @code{let}-s should be used (nested) in a way to | |
| 7638 provide the clearest code. | |
| 7639 | |
| 2537 | 7640 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced |
| 7641 @unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}? | |
| 2459 | 7642 |
| 7643 @itemize @bullet | |
| 7644 @item Global variables | |
| 7645 | |
| 7646 You will typically @code{defvar} your global variable to a default | |
| 7647 value, and use @code{setq} to set it later. | |
| 7648 | |
| 7649 It is never a good practice to @code{setq} user variables (like | |
| 7650 @code{case-fold-search}, etc.), as it ignores the user's choice | |
| 7651 unconditionally. Note that @code{defvar} doesn't change the value of a | |
| 7652 variable if it was bound previously. If you wish to change a | |
| 7653 user-variable temporarily, use @code{let}: | |
| 7654 | |
| 7655 @lisp | |
| 7656 (let ((case-fold-search nil)) | |
| 7657 ... ; code with searches that must be case-sensitive | |
| 7658 ...) | |
| 7659 @end lisp | |
| 7660 | |
| 7661 You will notice the user-variables by their docstrings beginning with an | |
| 7662 asterisk (a convention). | |
| 7663 | |
| 7664 @item Local variables | |
| 7665 | |
| 7666 Bind them with @code{let}, which will unbind them (or restore their | |
| 7667 previous value, if they were bound) after exiting from the @code{let} | |
| 7668 form. Change the value of local variables with @code{setq} or whatever | |
| 7669 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form | |
| 7670 can even return one of its local variables. | |
| 7671 | |
| 7672 Typical usage: | |
| 7673 | |
| 7674 @lisp | |
| 7675 ;; iterate through the elements of the list returned by | |
| 7676 ;; `hairy-function-that-returns-list' | |
| 7677 (let ((l (hairy-function-that-returns-list))) | |
| 7678 (while l | |
| 7679 ... do something with (car l) ... | |
| 7680 (setq l (cdr l)))) | |
| 7681 @end lisp | |
| 7682 | |
| 7683 Another typical usage includes building a value simply to work with it. | |
| 7684 | |
| 7685 @lisp | |
| 7686 ;; Build the mode keymap out of the key-translation-alist | |
| 7687 (let ((inbox (file-truename (expand-file-name box))) | |
| 7688 (i 0)) | |
| 7689 ... code dealing with inbox ... | |
| 7690 inbox) | |
| 7691 @end lisp | |
| 7692 | |
| 7693 This piece of code uses the local variable @code{inbox}, which becomes | |
| 7694 unbound (or regains old value) after exiting the form. The form also | |
| 7695 returns the value of @code{inbox}, which can be reused, for instance: | |
| 7696 | |
| 7697 @lisp | |
| 7698 (setq foo-processed-inbox | |
| 7699 (let .....)) | |
| 7700 @end lisp | |
| 7701 @end itemize | |
| 7702 | |
| 2537 | 7703 @node Q7.1.6, Q7.1.7, Q7.1.5, Advanced |
| 7704 @unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}? | |
| 2459 | 7705 |
| 7706 A typical misuse is probably @code{setq}ing a variable that was meant to | |
| 7707 be local. Such a variable will remain bound forever, never to be | |
| 7708 garbage-collected. For example, the code doing: | |
| 7709 | |
| 7710 @lisp | |
| 7711 (defun my-function (whatever) | |
| 7712 (setq a nil) | |
| 7713 ... build a large list ... | |
| 7714 ... and exit ...) | |
| 7715 @end lisp | |
| 7716 | |
| 7717 does a bad thing, as @code{a} will keep consuming memory, never to be | |
| 7718 unbound. The correct thing is to do it like this: | |
| 7719 | |
| 7720 @lisp | |
| 7721 (defun my-function (whatever) | |
| 7722 (let (a) ; default initialization is to nil | |
| 7723 ... build a large list ... | |
| 7724 ... and exit, unbinding `a' in the process ...) | |
| 7725 @end lisp | |
| 7726 | |
| 7727 Not only is this prettier syntactically, but it makes it possible for | |
| 7728 Emacs to garbage-collect the objects which @code{a} used to reference. | |
| 7729 | |
| 7730 Note that even global variables should not be @code{setq}ed without | |
| 7731 @code{defvar}ing them first, because the byte-compiler issues warnings. | |
| 7732 The reason for the warning is the following: | |
| 7733 | |
| 7734 @lisp | |
| 7735 (defun flurgoze nil) ; ok, global internal variable | |
| 7736 ... | |
| 7737 | |
| 7738 (setq flurghoze t) ; ops! a typo, but semantically correct. | |
| 7739 ; however, the byte-compiler warns. | |
| 7740 | |
| 7741 While compiling toplevel forms: | |
| 7742 ** assignment to free variable flurghoze | |
| 7743 @end lisp | |
| 7744 | |
| 2537 | 7745 @node Q7.1.7, Q7.1.8, Q7.1.6, Advanced |
| 7746 @unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down? | |
| 2459 | 7747 |
| 7748 It shouldn't. Here is what Dave Gillespie has to say about cl.el | |
| 7749 performance: | |
| 7750 | |
| 7751 @quotation | |
| 7752 Many of the advanced features of this package, such as @code{defun*}, | |
| 7753 @code{loop}, and @code{setf}, are implemented as Lisp macros. In | |
| 7754 byte-compiled code, these complex notations will be expanded into | |
| 7755 equivalent Lisp code which is simple and efficient. For example, the | |
| 7756 forms | |
| 7757 | |
| 7758 @lisp | |
| 7759 (incf i n) | |
| 7760 (push x (car p)) | |
| 7761 @end lisp | |
| 7762 | |
| 7763 are expanded at compile-time to the Lisp forms | |
| 7764 | |
| 7765 @lisp | |
| 7766 (setq i (+ i n)) | |
| 7767 (setcar p (cons x (car p))) | |
| 7768 @end lisp | |
| 7769 | |
| 7770 which are the most efficient ways of doing these respective operations | |
| 7771 in Lisp. Thus, there is no performance penalty for using the more | |
| 7772 readable @code{incf} and @code{push} forms in your compiled code. | |
| 7773 | |
| 7774 @emph{Interpreted} code, on the other hand, must expand these macros | |
| 7775 every time they are executed. For this reason it is strongly | |
| 7776 recommended that code making heavy use of macros be compiled. (The | |
| 7777 features labelled @dfn{Special Form} instead of @dfn{Function} in this | |
| 7778 manual are macros.) A loop using @code{incf} a hundred times will | |
| 7779 execute considerably faster if compiled, and will also garbage-collect | |
| 7780 less because the macro expansion will not have to be generated, used, | |
| 7781 and thrown away a hundred times. | |
| 7782 | |
| 7783 You can find out how a macro expands by using the @code{cl-prettyexpand} | |
| 7784 function. | |
| 7785 @end quotation | |
| 7786 | |
| 2537 | 7787 @node Q7.1.8, Q7.1.9, Q7.1.7, Advanced |
| 7788 @unnumberedsubsec Q7.1.8: I like recursion, does it slow things down? | |
| 2459 | 7789 |
| 7790 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But | |
| 7791 think well whether this is a real concern in Emacs. Much of the Emacs | |
| 7792 slowness comes from internal mechanisms such as redisplay, or from the | |
| 7793 fact that it is an interpreter. | |
| 7794 | |
| 7795 Please try not to make your code much uglier to gain a very small speed | |
| 7796 gain. It's not usually worth it. | |
| 7797 | |
| 2537 | 7798 @node Q7.1.9, Q7.1.10, Q7.1.8, Advanced |
| 7799 @unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer? | |
| 2459 | 7800 |
| 7801 Here is a solution that will insert the glyph annotation at the | |
| 7802 beginning of buffer: | |
| 7803 | |
| 7804 @lisp | |
| 7805 (make-annotation (make-glyph '([FORMAT :file FILE] | |
| 7806 [string :data "fallback-text"])) | |
| 7807 (point-min) | |
| 7808 'text | |
| 7809 (current-buffer)) | |
| 7810 @end lisp | |
| 7811 | |
| 7812 Replace @samp{FORMAT} with an unquoted symbol representing the format of | |
| 7813 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.) | |
| 7814 Instead of @samp{FILE}, use the image file name | |
| 7815 (e.g. | |
| 7816 @iftex | |
| 7817 @* | |
| 7818 @end iftex | |
| 7819 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}). | |
| 7820 | |
| 7821 You can turn this to a function (that optionally prompts you for a file | |
| 7822 name), and inserts the glyph at @code{(point)} instead of | |
| 7823 @code{(point-min)}. | |
| 7824 | |
| 2537 | 7825 @node Q7.1.10, Q7.1.11, Q7.1.9, Advanced |
| 7826 @unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents! | |
| 2459 | 7827 |
| 7828 I tried to use @code{map-extents} to do an operation on all the extents | |
| 7829 in a region. However, it seems to quit after processing a random number | |
| 7830 of extents. Is it buggy? | |
| 7831 | |
| 7832 No. The documentation of @code{map-extents} states that it will iterate | |
| 7833 across the extents as long as @var{function} returns @code{nil}. | |
| 7834 Unexperienced programmers often forget to return @code{nil} explicitly, | |
| 7835 which results in buggy code. For instance, the following code is | |
| 7836 supposed to delete all the extents in a buffer, and issue as many | |
| 7837 @samp{fubar!} messages. | |
| 7838 | |
| 7839 @lisp | |
| 7840 (map-extents (lambda (ext ignore) | |
| 7841 (delete-extent ext) | |
| 7842 (message "fubar!"))) | |
| 7843 @end lisp | |
| 7844 | |
| 7845 Instead, it will delete only the first extent, and stop right there -- | |
| 7846 because @code{message} will return a non-nil value. The correct code | |
| 7847 is: | |
| 7848 | |
| 7849 @lisp | |
| 7850 (map-extents (lambda (ext ignore) | |
| 7851 (delete-extent ext) | |
| 7852 (message "fubar!") | |
| 7853 nil)) | |
| 7854 @end lisp | |
| 7855 | |
| 2537 | 7856 @node Q7.1.11, Q7.2.1, Q7.1.10, Advanced |
| 7857 @unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 2459 | 7858 @c New |
| 7859 | |
| 7860 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes: | |
| 7861 @quotation | |
| 7862 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence}, | |
| 7863 press a key (say @key{RET} in the Gnus Group buffer), and get the | |
| 7864 results using @kbd{M-x profile-results}. It should give you an idea of | |
| 7865 where the time is being spent. | |
| 7866 @end quotation | |
| 7867 | |
| 2537 | 7868 @unnumberedsec 7.2: Mathematics |
| 7869 | |
| 7870 @node Q7.2.1, Q7.2.2, Q7.1.11, Advanced | |
| 7871 @unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp? | |
| 2459 | 7872 |
| 7873 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and | |
| 7874 later can use the capabilities of multiple-precision libraries that may | |
| 7875 be available for your platform. The GNU Multiple Precision (GMP) and | |
| 7876 BSD Multiple Precision (MP) libraries are partially supported. GMP | |
| 7877 gives you @dfn{bignums} (arbitrary precision integers), @dfn{ratios} | |
| 7878 (arbitrary precision fractions), and @dfn{bigfloats} (arbitrary | |
| 7879 precision floating point numbers). GNU MP is better-supported by XEmacs | |
| 7880 at the time of writing (2004-04-06). BSD MP support does not include | |
| 7881 ratios or bigfloats, and it throws errors that aren't understood. | |
| 7882 | |
| 7883 In most cases, bignum support should be transparent to users and Lisp | |
| 7884 programmers. A bignum-enabled XEmacs will automatically convert from | |
| 7885 fixnums to bignums and back in pure integer arithmetic, and for GNU MP, | |
| 7886 from floats to bigfloats. (Bigfloats must be explicitly coerced to | |
| 7887 other types, even if they are exactly representable by less precise | |
| 7888 types.) The Lisp reader and printer have been enhanced to handle | |
| 7889 bignums, as have the mathematical functions. Rationals (fixnums, | |
| 7890 bignums, and ratios) are printed using the @samp{%d}, @samp{%o}, | |
| 7891 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios | |
| 7892 is @samp{3/5}. | |
| 7893 | |
| 7894 User-visible changes in behavior include (in probable order of annoyance) | |
| 7895 | |
| 7896 @itemize | |
| 7897 @item | |
| 7898 Arithmetic can cause a segfault, depending on your MP library | |
| 2537 | 7899 @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. |
| 2459 | 7900 |
| 7901 @item | |
| 7902 Terminology is not Common-Lisp-conforming. For example, ``integer'' for | |
| 7903 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being | |
| 7904 investigated, but the use of ``integer'' for fixnum is pervasive and may | |
| 7905 cause backward-compatibility and GNU-Emacs-compatibility problems. | |
| 7906 | |
| 7907 @item | |
| 7908 Many operations that used to cause a range error now succeed, with | |
| 7909 intermediate results and return values coerced to bignums as needed. | |
| 7910 | |
| 7911 @item | |
| 7912 An atom with ratio read syntax now returns a number, not a symbol. | |
| 7913 | |
| 7914 @item | |
| 7915 The @samp{%u} format conversion will now give an error if its argument | |
| 7916 is negative. (Without MP, it prints a number which Lisp can't read.) | |
| 7917 @end itemize | |
| 7918 | |
| 7919 @emph{Surgeon General's Warning}: The automatic conversions cannot be | |
| 7920 disabled at runtime. New functions have been added which produce | |
| 7921 ratios, so there should be few surprises with type conflicts, but they | |
| 7922 can't be ruled out. ``Arbitrary'' precision means precisely what it | |
| 7923 says. If you work with extremely large numbers, your machine may | |
| 7924 arbitrarily decide to hand you an unpleasant surprise rather than a | |
| 2537 | 7925 bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. |
| 2459 | 7926 |
| 3018 | 7927 To configure with GNU MP, add @samp{--use-number-lib=gmp} |
| 7928 (@samp{--enable-bignum=gmp} in 21.5 or later) to your invocation of | |
| 7929 @file{configure}. For BSD MP, use @samp{--use-number-lib=mp} | |
| 7930 (@samp{--enable-bignum=mp} for 21.5). | |
| 2459 | 7931 |
| 7932 If you would like to help with bignum support, especially on BSD MP, | |
| 7933 please subscribe to the @uref{http://www.xemacs.org/Lists/#xemacs-beta, | |
| 7934 XEmacs Beta mailing list}, and book up on @file{number-gmp.h} and | |
| 7935 @file{number-mp.h}. Jerry has promised to write internals documentation | |
| 7936 eventually, but if your skills run more to analysis and documentation | |
| 7937 than to writing new code, feel free to fill in the gap! | |
| 7938 | |
| 7939 | |
| 2537 | 7940 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced |
| 7941 @unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers! | |
| 2459 | 7942 |
| 7943 GMP by default allocates temporaries on the stack. If you run out of | |
| 7944 stack space, you're dead; there is no way that we know of to reliably | |
| 7945 detect this condition, because @samp{alloca} is typically implemented to | |
| 7946 be @emph{fast} rather than robust. If you just need a little more | |
| 7947 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in | |
| 7948 bash(1)). If you want robustness at the cost of speed, configure GMP | |
| 7949 with @samp{--disable-alloca} and rebuild the GMP library. | |
| 7950 | |
| 7951 We do not know whether BSD MP uses @samp{alloca} or not. Please send | |
| 7952 any information you have as a bug report (@kbd{M-x report-xemacs-bug | |
| 7953 @key{RET}}), which will give us platform information. (We do know that | |
| 7954 BSD MP implementations vary across vendors, but how much, we do not know | |
| 7955 yet.) | |
| 7956 | |
| 7957 | |
| 2537 | 7958 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced |
| 7959 @unnumberedsubsec Q7.2.3: Bignums are really slow! | |
| 2459 | 7960 |
| 7961 Many Linux distributions compile all their packages for the i386, and | |
| 7962 this is costly. An optimized version can give you two or three orders | |
| 7963 of magnitude better performance for a Pentium III or IV. (Yes, really. | |
| 7964 See @uref{http://www.swox.com/gmp/gmp-speed.html}.) | |
| 7965 | |
| 7966 | |
| 2537 | 7967 @node Q7.2.4, , Q7.2.3, Advanced |
| 7968 @unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives? | |
| 2459 | 7969 |
| 7970 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva | |
| 7971 CLTL2 warned of the illusion that equal numbers would be @samp{eq}! | |
| 7972 Meditate on the deeper truths of @samp{eql}, in which numbers of the same | |
| 7973 type which have equal values compare equal, and @samp{=}, which does any | |
| 7974 necessary type coercions before comparing for equality. | |
| 7975 | |
| 7976 Yeah, yeah, it has always worked for integer types, because fixnums and | |
| 7977 characters have an immediate representation. Sorry about that; | |
| 7978 arbitrary precision obviously requires consing new objects because the | |
| 7979 objects are ``large'' and of variable size, and the definition of | |
| 7980 @samp{eq} does not permit different objects to compare as equal. | |
| 7981 | |
| 7982 @node Other Packages, Current Events, Advanced, Top | |
| 7983 @unnumbered 8 Other External Packages | |
| 7984 | |
| 7985 This is part 8 of the XEmacs Frequently Asked Questions list. This | |
| 7986 section is devoted to miscellaneous external packages not covered | |
| 7987 elsewhere in XEmacs. | |
| 7988 | |
| 7989 @menu | |
| 2537 | 7990 8.0: TeX |
| 2459 | 7991 * Q8.0.1:: Is there something better than LaTeX mode? |
| 7992 * Q8.0.2:: What is AUCTeX? Where do you get it? | |
| 7993 * Q8.0.3:: Problems installing AUCTeX. | |
| 7994 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline? | |
| 7995 | |
| 7996 8.1: Other Unbundled Packages | |
| 7997 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 7998 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets? | |
| 7999 * Q8.1.3:: Is there a MatLab mode? | |
| 8000 | |
| 8001 8.2: Environments Built Around XEmacs | |
| 8002 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop? | |
| 8003 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21? | |
| 8004 * Q8.2.3:: What is/was Energize? | |
| 8005 * Q8.2.4:: What is Infodock? | |
| 8006 @end menu | |
| 8007 | |
| 8008 @unnumberedsec 8.0: TeX | |
| 8009 | |
| 8010 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages | |
| 8011 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode? | |
| 2417 | 8012 |
| 8013 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes: | |
| 8014 | |
| 8015 @quotation | |
| 8016 The standard TeX modes leave much to be desired, and are somewhat | |
| 2459 | 8017 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2, |
| 2417 | 8018 What is AUCTeX? Where do you get it?}). |
| 8019 @end quotation | |
| 8020 | |
| 2459 | 8021 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages |
| 8022 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it? | |
| 2417 | 8023 |
| 8024 AUCTeX is a complex and sophisticated editing package dedicated to TeX | |
| 8025 and related text formatting languages, including LaTeX and Texinfo. | |
| 8026 It provides support for running TeX on a file or part of a file, | |
| 8027 include files, and of course shortcuts for entering common TeX macros, | |
| 8028 LaTeX environments, etc, and for fontlock. | |
| 8029 | |
| 8030 AUCTeX is a standard package provided by XEmacs. You can get it as | |
| 8031 usual through the @kbd{M-x list-packages} interface. It is also | |
| 8032 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is | |
| 8033 maintained by Uwe Brauer <GET MAIL ADDRESS>. | |
| 8034 | |
| 8035 AUCTeX is extremely complicated, and its developers primarily | |
| 8036 use GNU Emacs. Not all features of the bleeding edge version | |
| 8037 of AUCTeX are immediately ported to XEmacs; if you need | |
| 8038 these, you may be better off getting the most recent versions | |
| 8039 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}. | |
| 8040 | |
| 2459 | 8041 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages |
| 8042 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX. | |
| 2417 | 8043 |
| 8044 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes: | |
| 8045 | |
| 8046 @quotation | |
| 8047 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for | |
| 8048 a very very long time. This is mostly due to the work of | |
| 8049 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu} | |
| 8050 package. Which leads to what is probably the problem... | |
| 8051 @end quotation | |
| 8052 | |
| 8053 Most problems with AUCTeX are one of two things: | |
| 8054 | |
| 8055 @itemize @bullet | |
| 8056 @item | |
| 8057 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't | |
| 8058 match. | |
| 8059 | |
| 8060 Fix: make sure you configure AUCTeX properly @strong{before} installing. | |
| 8061 | |
| 8062 @item | |
| 8063 You have an old version of easymenu.el in your path. | |
| 8064 | |
| 8065 Fix: use @code{locate-library} and remove old versions to make sure it | |
| 8066 @strong{only} finds the one that came with XEmacs. | |
| 8067 @end itemize | |
| 8068 | |
| 2459 | 8069 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages |
| 8070 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline? | |
| 2417 | 8071 |
| 8072 With AUCTeX, fast typing is hard because the current chapter, section | |
| 8073 etc. are given in the modeline. How can I turn this off? | |
| 8074 | |
| 8075 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}. | |
| 8076 | |
| 8077 @c Add this code to your @file{init.el} to turn it off: | |
| 8078 @c | |
| 8079 @c @lisp | |
| 8080 @c (setq fume-display-in-modeline-p nil) | |
| 8081 @c @end lisp | |
| 8082 @c | |
| 8083 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX | |
| 8084 @c mode: | |
| 8085 @c | |
| 8086 @c @lisp | |
| 8087 @c (add-hook 'TeX-mode-hook | |
| 8088 @c '(lambda () (setq fume-display-in-modeline-p nil))) | |
| 8089 @c @end lisp | |
| 8090 @c | |
| 8091 @email{dhughes@@origin-at.co.uk, David Hughes} writes: | |
| 8092 | |
| 8093 @quotation | |
| 8094 Try this; you'll still get the function name displayed in the modeline, | |
| 8095 but it won't attempt to keep track when you modify the file. To refresh | |
| 8096 when it gets out of synch, you simply need click on the @samp{Rescan | |
| 8097 Buffer} option in the function-menu. | |
| 8098 | |
| 8099 @lisp | |
| 8100 (setq-default fume-auto-rescan-buffer-p nil) | |
| 8101 @end lisp | |
| 8102 @end quotation | |
| 8103 | |
| 2459 | 8104 @unnumberedsec 8.1: Other Unbundled Packages |
| 8105 | |
| 8106 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages | |
| 8107 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 2417 | 8108 |
| 8109 The reason for an Emacs package not to be included in XEmacs is | |
| 8110 usually one or more of the following: | |
| 8111 | |
| 8112 @enumerate | |
| 8113 @item | |
| 8114 The package has not been ported to XEmacs. This will typically happen | |
| 8115 when it uses GNU-Emacs-specific features, which make it fail under | |
| 8116 XEmacs. | |
| 8117 | |
| 8118 Porting a package to XEmacs can range from a trivial amount of change to | |
| 8119 a partial or full rewrite. Fortunately, the authors of modern packages | |
| 8120 usually choose to support both Emacsen themselves. | |
| 8121 | |
| 8122 @item | |
| 8123 The package has been decided not to be appropriate for XEmacs. It may | |
| 8124 have an equivalent or better replacement within XEmacs, in which case | |
| 8125 the developers may choose not to burden themselves with supporting an | |
| 8126 additional package. | |
| 8127 | |
| 8128 Each package bundled with XEmacs means more work for the maintainers, | |
| 8129 whether they want it or not. If you are ready to take over the | |
| 8130 maintenance responsibilities for the package you port, be sure to say | |
| 8131 so---we will more likely include it. | |
| 8132 | |
| 8133 @item | |
| 8134 The package simply hasn't been noted by the XEmacs development. If | |
| 8135 that's the case, the messages like yours are very useful for attracting | |
| 8136 our attention. | |
| 8137 | |
| 8138 @item | |
| 8139 The package was noted by the developers, but they simply haven't yet | |
| 8140 gotten around to including/porting it. Wait for the next release or, | |
| 8141 even better, offer your help. It will be gladly accepted and | |
| 8142 appreciated. | |
| 8143 @end enumerate | |
| 8144 | |
| 2459 | 8145 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages |
| 8146 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets? | |
| 2417 | 8147 |
| 8148 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at | |
| 428 | 8149 @iftex |
| 8150 @* | |
| 8151 @end iftex | |
| 2459 | 8152 @uref{http://acs.ist.psu.edu/dismal/dismal.html}. |
| 8153 | |
| 8154 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages | |
| 8155 @unnumberedsubsec Q8.1.3: Is there a MatLab mode? | |
| 2417 | 8156 |
| 8157 Yes, a matlab mode and other items are available at the | |
| 2459 | 8158 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}. |
| 8159 | |
| 8160 @unnumberedsec 8.2: Environments Built Around XEmacs | |
| 8161 | |
| 8162 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages | |
| 8163 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop? | |
| 2417 | 8164 |
| 8165 SPARCworks was a development environment from Sun (circa 1993-1996) | |
| 8166 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and | |
| 8167 Pascal), a debugger, and other tools such as TeamWare (for | |
| 8168 configuration management), MakeTool, etc. | |
| 428 | 8169 |
| 8170 EOS is the integration of XEmacs with the SPARCworks debugger. It | |
| 8171 allows one to use an XEmacs frame to view code (complete with | |
| 8172 fontification, etc.), set breakpoints, print variables, etc., while | |
| 2417 | 8173 using the SPARCworks debugger. |
| 8174 | |
| 8175 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten | |
| 8176 Again" and was the name used by Sun for its modified version of Lucid | |
| 8177 Emacs (later XEmacs) in the early-mid 90's. This is documented in | |
| 8178 more detail in the history section of the XEmacs About page. | |
| 8179 | |
| 8180 EOS was replaced around 1996 with a newer graphical development | |
| 8181 environment called Sun WorkShop. The current status of this is | |
| 8182 unknown. | |
| 8183 | |
| 2459 | 8184 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages |
| 8185 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21? | |
| 428 | 8186 |
| 8187 Add the switch ---with-workshop to the configure command when building | |
| 8188 XEmacs and put the following in one of your startup files | |
| 8189 (e.g. site-start.el or .emacs): | |
| 8190 | |
| 8191 @lisp | |
| 8192 (when (featurep 'tooltalk) | |
| 8193 (load "tooltalk-macros") | |
| 8194 (load "tooltalk-util") | |
| 8195 (load "tooltalk-init")) | |
| 8196 (when (featurep 'sparcworks) | |
| 8197 (load "sunpro-init") | |
| 8198 (load "ring") | |
| 8199 (load "comint") | |
| 8200 (load "annotations") | |
| 8201 (sunpro-startup)) | |
| 8202 @end lisp | |
| 8203 | |
| 8204 If you are not using the latest Workshop (5.0) you have to apply the | |
| 8205 following patch: | |
| 8206 | |
| 8207 @format | |
| 8208 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999 | |
| 8209 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999 | |
| 8210 @@@@ -42,7 +42,7 @@@@ | |
| 8211 (defvar running-xemacs nil "t if we're running XEmacs") | |
| 8212 (defvar running-emacs nil "t if we're running GNU Emacs 19") | |
| 438 | 8213 |
| 428 | 8214 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version) |
| 8215 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version) | |
| 8216 (setq running-xemacs t) | |
| 8217 (setq running-emacs t)) | |
| 438 | 8218 @end format |
| 428 | 8219 |
| 2459 | 8220 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages |
| 8221 @unnumberedsubsec Q8.2.3: What is/was Energize? | |
| 2417 | 8222 |
| 8223 The "Energize Programming System" was a C and C++ development environment | |
| 8224 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was | |
| 8225 created in the first place. Unfortunately, Lucid went out of business in | |
| 8226 1994. The rights to sell it in Japan were purchased by INS | |
| 8227 Engineering (which briefly employed Stig Hackvan aka Jonathan | |
| 8228 Stigelman to work on Japanese support for XEmacs, in late 1994 and | |
| 8229 early 1995) and Tartan bought the rights to sell it in the rest of the | |
| 8230 world. However, INS is not selling Energize at this point and may or | |
| 8231 may not have ever done so; Tartan certainly never did. | |
| 8232 | |
| 2459 | 8233 @node Q8.2.4, , Q8.2.3, Other Packages |
| 8234 @unnumberedsubsec Q8.2.4: What is Infodock? | |
| 428 | 8235 |
| 660 | 8236 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an |
| 8237 integrated productivity toolset, mainly aimed at technical people, | |
| 8238 hosted at SourceForge. | |
| 428 | 8239 |
| 8240 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of | |
| 8241 the power of Emacs, but with an easier to use and more comprehensive | |
| 8242 menu-based user interface. The bottom portion of this text describes | |
| 8243 how it differs from XEmacs and GNU Emacs from the Free Software | |
| 8244 Foundation. | |
| 8245 | |
| 8246 InfoDock is aimed at people who want a free, turn-key productivity | |
| 8247 environment. Although InfoDock is customizable, it is not intended for | |
| 8248 people who like basic versions of Emacs which need to be customized | |
| 8249 extensively for local use; standard Emacs distributions are better for | |
| 8250 such uses. InfoDock is for those people who want a complete, | |
| 8251 pre-customized environment in one package, which they need not touch | |
| 8252 more than once or twice a year to update to new revisions. | |
| 8253 | |
| 8254 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX, | |
| 8255 and Intel Linux systems. It is intended for use on a color display, | |
| 8256 although most features will work on monochrome monitors. Simply unpack | |
| 8257 InfoDock according to the instructions in the ID-INSTALL file and you | |
| 8258 are ready to run. | |
| 8259 | |
| 8260 The InfoDock Manual is concise, yet sufficient as a user guide for users | |
| 8261 who have never used an Emacs-type editor before. For users who are | |
| 8262 already familiar with Emacs, it supplements the information in the GNU | |
| 8263 Emacs Manual. | |
| 8264 | |
| 8265 InfoDock menus are much more extensive and more mature than standard | |
| 8266 Emacs menus. Each menu offers a @samp{Manual} item which displays | |
| 8267 documentation associated with the menu's functions. | |
| 8268 | |
| 8269 @noindent | |
| 8270 Four types of menubars are provided: | |
| 8271 @enumerate | |
| 8272 @item | |
| 8273 An extensive menubar providing access to global InfoDock commands. | |
| 8274 @item | |
| 8275 Mode-specific menubars tailored to the current major mode. | |
| 8276 @item | |
| 8277 A simple menubar for basic editing to help novices get started with InfoDock. | |
| 8278 @item | |
| 8279 The standard XEmacs menubar. | |
| 8280 @end enumerate | |
| 8281 | |
| 8282 Most modes also include mode-specific popup menus. Additionally, region and | |
| 8283 rectangle popup menus are included. | |
| 8284 | |
| 8285 @samp{Hyperbole}, the everyday information manager, is a core part of | |
| 8286 InfoDock. This provides context-sensitive mouse keys, a rolodex-type | |
| 8287 contact manager, programmable hypertext buttons, and an autonumbered | |
| 8288 outliner with embedded hyperlink anchors. | |
| 8289 | |
| 8290 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a | |
| 8291 standard part of InfoDock. | |
| 8292 | |
| 8293 InfoDock saves a more extensive set of user options than other Emacs | |
| 8294 versions. | |
| 8295 | |
| 8296 InfoDock inserts a useful file header in many file types, showing the | |
| 8297 author, summary, and last modification time of each file. A summary | |
| 8298 program can then be used to summarize all of the files in a directory, | |
| 8299 for easy MANIFEST file creation. | |
| 8300 | |
| 8301 Your working set of buffers is automatically saved and restored (if you | |
| 8302 answer yes to a prompt) between InfoDock sessions. | |
| 8303 | |
| 8304 Refined color choices for code highlighting are provided for both dark and | |
| 8305 light background display frames. | |
| 8306 | |
| 8307 The @kbd{C-z} key prefix performs frame-based commands which parallel the | |
| 8308 @kbd{C-x} key prefix for window-based commands. | |
| 8309 | |
| 8310 The Smart Menu system is included for producing command menus on dumb | |
| 8311 terminals. | |
| 8312 | |
| 8313 Lisp libraries are better categorized according to function. | |
| 8314 | |
| 8315 Extensions and improvements to many areas of Emacs are included, such as: | |
| 8316 paragraph filling, mail reading with Rmail, shell handling, outlining, code | |
| 8317 highlighting and browsing, and man page browsing. | |
| 8318 | |
| 8319 InfoDock questions, answers and discussion should go to the mail list | |
| 8320 @iftex | |
| 8321 @* | |
| 8322 @end iftex | |
| 8323 @email{infodock@@infodock.com}. Use | |
| 8324 @email{infodock-request@@infodock.com} to be added or removed from the | |
| 8325 list. Always include your InfoDock version number when sending help | |
| 8326 requests. | |
| 8327 | |
| 2459 | 8328 @node Current Events, Legacy Versions, Other Packages, Top |
| 8329 @unnumbered 9 What the Future Holds | |
| 8330 | |
| 8331 This is part 9 of the XEmacs Frequently Asked Questions list. This | |
| 611 | 8332 section will change frequently, and (in theory) should contain any |
| 8333 interesting items that have transpired recently. (But in practice it's | |
| 8334 not getting updated like this.) | |
| 8335 | |
| 8336 This section also contains descriptions of the new features in all the | |
| 8337 recent releases of XEmacs. For the most part, the information below is | |
| 8338 a synopsis of the more complete information that can be found in the | |
| 8339 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution. | |
| 8340 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help} | |
| 8341 menu. | |
| 8342 | |
| 8343 Information on older versions of XEmacs can be find in @file{ONEWS} in | |
| 8344 the same directory, or @file{OONEWS} for really old versions. | |
| 8345 | |
| 428 | 8346 @menu |
| 2537 | 8347 9.0: Changes |
| 2459 | 8348 * Q9.0.1:: What new features will be in XEmacs soon? |
| 8349 * Q9.0.2:: What's new in XEmacs 21.4? | |
| 8350 * Q9.0.3:: What's new in XEmacs 21.1? | |
| 8351 * Q9.0.4:: What's new in XEmacs 20.4? | |
| 8352 * Q9.0.5:: What's new in XEmacs 20.3? | |
| 8353 * Q9.0.6:: What's new in XEmacs 20.2? | |
| 428 | 8354 @end menu |
| 8355 | |
| 2459 | 8356 @unnumberedsec 9.0: Changes |
| 8357 | |
| 8358 @node Q9.0.1, Q9.0.2, Current Events, Current Events | |
| 8359 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon? | |
| 611 | 8360 |
| 2417 | 8361 #### Write me. |
| 428 | 8362 |
| 2459 | 8363 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events |
| 8364 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4? | |
| 611 | 8365 |
| 8366 21.4 was the "stable" version of the 21.2 series, which was considered | |
| 8367 "experimental" throughout its life; thus there were no "official" | |
| 8368 releases at all. In essence, XEmacs is now following the "alternating" | |
| 8369 scheme of Linux, where at any point there are at least two different | |
| 8370 development branches, one "stable" and one "experimental". Periodic | |
| 8371 releases happen in both branches, but those in the experimental branch | |
| 8372 are not tested as well, and there's no guarantee they will work at all. | |
| 4311 | 8373 The experimental branch is open to any and all code that's acceptable |
| 611 | 8374 to the developers; the stable branch, however, is in general limited |
| 8375 only to bug fixes, and all contributions are carefully reviewed to make | |
| 8376 sure they will increase and not decrease stability. | |
| 8377 | |
| 8378 21.3 never existed at all; it was decided to follow the Linux scheme | |
| 8379 exactly, where odd-numbered series are experimental and even-numbered | |
| 8380 ones stable. | |
| 8381 | |
| 8382 The following lists summarizes the essential changes made in this | |
| 8383 version. For a fuller list, see the @file{NEWS} in the @file{etc} | |
| 8384 directory of the XEmacs distribution, or use @kbd{C-h n} or the | |
| 8385 @samp{Help} menu to view this file inside of XEmacs. | |
| 8386 | |
| 676 | 8387 @unnumberedsubsubsec User-visible changes in XEmacs 21.4 |
| 611 | 8388 |
| 8389 @itemize @bullet | |
| 8390 | |
| 8391 @item | |
| 8392 The delete key now deletes forward by default. | |
| 8393 @item | |
| 8394 Shifted motion keys now select text by default. | |
| 8395 @item | |
| 8396 You can now build XEmacs with support for GTK+ widget set. | |
| 8397 @item | |
| 8398 ~/.xemacs/init.el is now the preferred location for the init | |
| 8399 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom | |
| 8400 file will move to ~/.xemacs/custom.el.) | |
| 8401 @item | |
| 8402 Much-improved sample init.el, showing how to use many useful features. | |
| 8403 @item | |
| 8404 XEmacs support for menu accelerators has been much improved. | |
| 8405 @item | |
| 8406 Default menubar improvements. (Default menubar has many new commands and | |
| 8407 better organization. The font-menu is now available under MS Windows.) | |
| 8408 @item | |
| 2417 | 8409 Dialog box improvements, including a real file dialog box. (XEmacs now |
| 8410 has a proper file dialog box under MS Windows (and GTK)! The old | |
| 8411 clunky file dialog box is improved. Keyboard traversal now works | |
| 8412 correctly in MS Windows dialog boxes. There is a Search dialog box | |
| 8413 available from @samp{Edit->Find...}) | |
| 611 | 8414 @item |
| 8415 New buffer tabs. | |
| 8416 @item | |
| 8417 There is a new MS Windows installer, netinstall, ported from Cygwin. | |
| 8418 @item | |
| 8419 The subprocess quote-handling mechanism under Windows is much improved. | |
| 8420 @item | |
| 8421 Printing support now available under MS Windows. | |
| 8422 @item | |
| 8423 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).) | |
| 8424 @item | |
| 8425 Mail spool locking now works correctly. | |
| 8426 @item | |
| 8427 International support changes. (The default coding-priority-list is now | |
| 8428 safer. International keysyms are now supported under X. MS Windows | |
| 8429 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese, | |
| 8430 Ethiopic now supported. Proper support for words in Latin 3 and Latin | |
| 8431 4.) | |
| 8432 @item | |
| 8433 Help buffers contain hyperlinks, and other changes. | |
| 8434 @item | |
| 8435 The modeline's text is now scrollable. | |
| 8436 @item | |
| 8437 The mouse wheel under MS Windows now functions correctly. | |
| 8438 @item | |
| 8439 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.) | |
| 8440 @item | |
| 8441 Rectangle functions rewritten to avoid inserting extra spaces. | |
| 8442 @item | |
| 8443 New command `kill-entire-line' that always kills the entire line. | |
| 8444 @item | |
| 8445 Default values correctly stored in minibuffer histories. | |
| 8446 @item | |
| 8447 You can now create "indirect buffers", like in GNU Emacs. | |
| 8448 @item | |
| 8449 Pixel-based scrolling has been implemented. | |
| 8450 @item | |
| 8451 Operation progress can be displayed using graphical widgets. | |
| 8452 @item | |
| 8453 User names following a tilde can now be completed at file name prompts. | |
| 8454 @item | |
| 8455 XEmacs can now play sound using Enlightenment Sound Daemon (ESD). | |
| 8456 @item | |
| 8457 X-Face support is now available under MS Windows. | |
| 8458 @item | |
| 8459 The PostgreSQL Relational Database Management System is now supported. | |
| 8460 @item | |
| 8461 Indentation no longer indents comments that begin at column zero. | |
| 8462 @item | |
| 8463 Face and variable settings can have comments in Customize. | |
| 8464 @item | |
| 8465 New locations for early package hierarchies. | |
| 8466 @item | |
| 8467 The `auto-save' library has been greatly improved. | |
| 8468 @item | |
| 8469 New variable `mswindows-alt-by-itself-activates-menu'. | |
| 8470 @item | |
| 8471 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.) | |
| 8472 @item | |
| 8473 Etags changes. See @file{NEWS} for full details. | |
| 8474 @end itemize | |
| 8475 | |
| 676 | 8476 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4 |
| 611 | 8477 |
| 8478 Not yet written. | |
| 8479 | |
| 661 | 8480 @c APA: Texi2html produces invalid HTML from an empty list of bullets! |
| 8481 @c Please uncomment following list when it does contain bullets. | |
| 8482 @c @itemize @bullet | |
| 8483 @c @end itemize | |
| 611 | 8484 |
| 2459 | 8485 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events |
| 8486 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1? | |
| 611 | 8487 |
| 8488 21.1 was the "stable" version of "experimental" 21.0 series. | |
| 2459 | 8489 @xref{Q9.0.2, What's new in XEmacs 21.4?}. |
| 611 | 8490 |
| 8491 The following lists summarizes the essential changes made in this | |
| 8492 version. For a fuller list, see the @file{NEWS} in the @file{etc} | |
| 8493 directory of the XEmacs distribution, or use @kbd{C-h n} or the | |
| 8494 @samp{Help} menu to view this file inside of XEmacs. | |
| 8495 | |
| 676 | 8496 @unnumberedsubsubsec User-visible changes in XEmacs 21.1 |
| 611 | 8497 |
| 8498 @itemize @bullet | |
| 8499 | |
| 8500 @item | |
| 2459 | 8501 XEmacs is now supported under Microsoft Windows 95/98 and Windows |
| 2417 | 8502 NT/2000/XP operating systems. To discuss Windows-specific issues, |
| 8503 subscribe to the mailing list at | |
| 8504 @email{xemacs-winnt-request@@xemacs.org}. | |
| 611 | 8505 |
| 8506 @item | |
| 8507 XEmacs has been unbundled into constituent installable packages. | |
| 8508 | |
| 8509 @item | |
| 8510 @strong{Other notable changes}: The @samp{Options} menu has been ported to | |
| 8511 Custom; XEmacs now is able to choose X visuals and use private | |
| 8512 colormaps; You can drag the vertical divider of "horizontally" | |
| 8513 (side-by-side) split windows. | |
| 8514 | |
| 8515 @item | |
| 8516 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp | |
| 8517 integers and 32-bit pointers (previously, it was 28-bit integers and | |
| 8518 pointers); XEmacs can be built with LDAP support; @file{dir} files can be | |
| 8519 removed in the Info subsystem, and will be regenerated on-the-fly. | |
| 8520 | |
| 8521 @item | |
| 8522 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight} | |
| 8523 | |
| 8524 @item | |
| 8525 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus}, | |
| 8526 @file{gnuclient}. See @file{NEWS} for full details. | |
| 8527 | |
| 8528 @item | |
| 8529 @strong{New commands, variables and functions}: | |
| 8530 @code{center-to-window-line} (like @code{recenter} but doesn't force a | |
| 8531 redisplay); variable @code{user-full-name} (customize what your full | |
| 8532 name looks like in mail); @kbd{M-x customize-changed-options} (customize | |
| 8533 options whose default values changes because you upgraded your XEmacs); | |
| 8534 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to | |
| 8535 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but | |
| 8536 doesn't delete the char searched for); commands to store, retrieve and | |
| 8537 increment numbers in registers, useful for macros. | |
| 8538 | |
| 8539 @item | |
| 8540 @strong{Changes to commands, variables, and functions}: @kbd{M-x | |
| 8541 query-replace} and friends operate only on the region when it's active; | |
| 8542 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.} | |
| 8543 searches exact tag matches before inexact ones; function | |
| 8544 @code{user-full-name} with no arguments returns the var | |
| 8545 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts | |
| 8546 the result in the current buffer. | |
| 1138 | 8547 |
| 611 | 8548 @item |
| 8549 @strong{Other changes}: Under X, new application class @samp{XEmacs}; | |
| 8550 byte-compilation of user-specs now works. | |
| 8551 | |
| 8552 @item | |
| 8553 @strong{XEmacs/Mule (internationalization) changes}: Mule support now | |
| 8554 works on TTY's; Egg/SJ3 input method now officially supported (Quail and | |
| 8555 Egg/Skk already available through LEIM since 20.3); localized Japanese | |
| 8556 menubars if XEmacs is built with the right support. | |
| 8557 | |
| 8558 @end itemize | |
| 8559 | |
| 676 | 8560 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1 |
| 611 | 8561 |
| 8562 @itemize @bullet | |
| 8563 | |
| 8564 @item | |
| 8565 @strong{Specifier changes}: The window locale now has a higher | |
| 8566 precedence than the buffer locale when instantiating; new macro | |
| 8567 @code{let-specifier}; new specifiers | |
| 8568 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p', | |
| 8569 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p}, | |
| 8570 @code{vertical-divider-always-visible-p}, | |
| 8571 @code{vertical-divider-shadow-thickness}, | |
| 8572 @code{vertical-divider-line-width}, @code{vertical-divider-spacing}; | |
| 8573 specifiers and symbols whose value is a specifier allowed as modeline | |
| 8574 specifications. | |
| 8575 | |
| 8576 @item | |
| 8577 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF, | |
| 8578 prevents any attempt to permanently change the selected frame; new | |
| 8579 function @code{focus-frame} sets the window system focus a frame; new | |
| 8580 special forms @code{save-selected-frame} and @code{with-selected-frame}. | |
| 8581 | |
| 8582 @item | |
| 8583 @strong{Window function changes}: @code{select-window} now has optional | |
| 8584 argument @var{NORECORD} to inhibit recording a buffer change; | |
| 8585 @code{vertical-motion} now correctly handles optional @var{WINDOW} | |
| 8586 argument and has new optional argument @var{PIXELS}, to have the | |
| 8587 returned values be in pixels; new function | |
| 8588 @code{vertical-motion-pixels}; new functions | |
| 8589 @code{window-text-area-pixel-@{width,height,edges@}}; new functions | |
| 8590 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new | |
| 8591 function @code{window-displayed-text-pixel-height}. | |
| 8592 | |
| 8593 @item | |
| 8594 @strong{Other function changes}: Arithmetic comparison functions | |
| 8595 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of | |
| 8596 arguments; hashtables now have a consistent read/print syntax; keyword | |
| 8597 symbols cannot be set to a value other than themselves; @code{concat} no | |
| 8598 longer accepts integer arguments; new function @code{string}, like | |
| 8599 @code{list}, @code{vector}, etc.; new function @code{temp-directory} | |
| 8600 (OS-independent way to get a temp directory); @code{load-average} has | |
| 8601 optional argument @var{USE-FLOATS}; @code{make-event} implemented | |
| 8602 completely; new function @code{function-interactive} (returns a | |
| 8603 function's interactive spec); new functions @code{lmessage}, | |
| 8604 @code{lwarn} (printf-like versions of @code{display-wessage}, | |
| 8605 @code{display-warning}); new keyword @code{:version} to | |
| 8606 @code{defcustom}. | |
| 8607 | |
| 8608 @item | |
| 8609 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is | |
| 8610 available, it will be used (better performance on libc6 Linux systems); | |
| 8611 tracking line-numbers in modeline is now efficient; profiling records a | |
| 8612 call-count of all called functions, retrievable through | |
| 8613 @code{profile-call-count-results}. | |
| 8614 | |
| 8615 @item | |
| 8616 @strong{Startup and path searching}: code to assemble paths at startup | |
| 8617 rewritten for new package system; new function @code{split-path} (splits | |
| 8618 by @code{path-separator}); @code{Info-default-directory-list} obsolete, | |
| 8619 use @code{Info-directory-list} instead; site-lisp is deprecated and no | |
| 8620 longer on the load-path by default. | |
| 8621 | |
| 8622 @end itemize | |
| 8623 | |
| 2459 | 8624 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events |
| 8625 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4? | |
| 611 | 8626 |
| 8627 XEmacs 20.4 is a bugfix release with no user-visible changes. | |
| 8628 @c Filled in from NEWS file of 20.5-b33 | |
| 8629 | |
| 2459 | 8630 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events |
| 8631 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3? | |
| 428 | 8632 |
| 8633 XEmacs 20.3 was released in November 1997. It contains many bugfixes, | |
| 8634 and a number of new features, including Autoconf 2 based configuration, | |
| 8635 additional support for Mule (Multi-language extensions to Emacs), many | |
| 8636 more customizations, multiple frames on TTY-s, support for multiple info | |
| 8637 directories, an enhanced gnuclient, improvements to regexp matching, | |
| 8638 increased MIME support, and many, many synches with GNU Emacs 20. | |
| 8639 | |
| 8640 The XEmacs/Mule support has been only seriously tested in a Japanese | |
| 8641 locale, and no doubt many problems still remain. The support for | |
| 8642 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a | |
| 440 | 8643 price---about a 30% slowdown from 19.16. We're making progress on |
| 428 | 8644 improving performance and XEmacs 20.3 compiled without Mule (which is |
| 8645 the default) is definitely faster than XEmacs 19.16. | |
| 8646 | |
| 8647 XEmacs 20.3 is the first non-beta v20 release, and will be the | |
| 8648 basis for all further development. | |
| 8649 | |
| 2459 | 8650 @node Q9.0.6, , Q9.0.5, Current Events |
| 8651 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2? | |
| 611 | 8652 |
| 8653 The biggest changes in 20.2 include integration of EFS (the next | |
| 8654 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a | |
| 8655 major mode for editing Tex and LaTeX, and a lot of other stuff). Many | |
| 8656 bugs from 20.0 have been fixed for this release. 20.2 also contains a | |
| 8657 new system for customizing XEmacs options, invoked via @kbd{M-x | |
| 8658 customize}. | |
| 8659 | |
| 8660 XEmacs 20.2 is the development release (20.0 was beta), and is no longer | |
| 8661 considered unstable. | |
| 8662 | |
| 8663 For older news, see the file @file{ONEWS} in the @file{etc} directory of | |
| 8664 the XEmacs distribution. | |
| 428 | 8665 |
| 2417 | 8666 @node Legacy Versions, , Current Events, Top |
| 2459 | 8667 @unnumbered 10 New information about old XEmacsen |
| 8668 | |
| 8669 This is part 10 of the XEmacs Frequently Asked Questions list. It will | |
| 1495 | 8670 occasionally be updated to reflect new information about versions which |
| 8671 are no longer being revised by the XEmacs Project. The primary purpose | |
| 8672 is advice on compatibility of older XEmacsen with new packages and | |
| 8673 updated versions of packages, but bug fixes (which will not be applied | |
| 8674 to released XEmacsen, but users can apply themselves) are also accepted. | |
| 8675 | |
| 8676 @menu | |
| 2537 | 8677 10.0: XEmacs 21.1 |
| 2459 | 8678 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. |
| 2559 | 8679 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1. |
| 1495 | 8680 @end menu |
| 8681 | |
| 2459 | 8682 @unnumberedsec 10.0: XEmacs 21.1 |
| 8683 | |
| 2559 | 8684 @node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions |
| 2459 | 8685 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1. |
| 1495 | 8686 |
| 8687 @email{eeide@@cs.utah.edu, Eric Eide} wrote: | |
| 8688 | |
| 8689 @quotation | |
| 8690 Previously I wrote: | |
| 8691 | |
| 8692 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see | |
| 8693 Eric> any smileys :-(. | |
| 8694 | |
| 8695 After a bit of sleuthing, I discovered the essence of the problem. | |
| 8696 For me, the form: | |
| 8697 | |
| 8698 @lisp | |
| 8699 (with-temp-buffer | |
| 8700 (insert-file-contents "foo.xpm") | |
| 8701 (buffer-string)) | |
| 8702 @end lisp | |
| 8703 | |
| 8704 returns the empty string. This is because something somewhere | |
| 8705 replaces the XPM data with a glyph --- I haven't figured out where | |
| 8706 this occurs. | |
| 8707 @end quotation | |
| 8708 | |
| 8709 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies: | |
| 8710 | |
| 8711 @quotation | |
| 8712 Do this: | |
| 8713 | |
| 8714 @lisp | |
| 8715 (setq format-alist nil) | |
| 8716 @end lisp | |
| 8717 | |
| 8718 The image-mode stuff is gone from format-alist in the 21.4 | |
| 8719 branch, praise be. | |
| 8720 @end quotation | |
| 8721 | |
| 2559 | 8722 @node Q10.0.2, , Q10.0.1, Legacy Versions |
| 8723 @unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1. | |
| 8724 | |
| 8725 XEmacs relies on a process called "dumping" to generate a working | |
| 8726 executable. Under MS-Windows this process effectively fixes the memory | |
| 8727 addresses of information in the executable. When XEmacs starts up it tries | |
| 8728 to reserve these memory addresses so that the dumping process can be | |
| 8729 reversed -- putting the information back at the correct addresses. | |
| 8730 Unfortunately some .DLLs (for instance the soundblaster driver) occupy | |
| 8731 memory addresses that can conflict with those needed by the dumped XEmacs | |
| 8732 executable. In this instance XEmacs will fail to start without any | |
| 8733 explanation. Note that this is extremely machine specific. | |
| 8734 | |
| 8735 21.1.10 includes a fix for this that makes more intelligent guesses | |
| 8736 about which memory addresses will be free, and this should cure the | |
| 8737 problem for most people. 21.4 implements "portable dumping", which | |
| 8738 eliminates the problem altogether. We recommend you use the 21.4 | |
| 8739 binaries, but you can use the 21.1 binaries if you are very paranoid | |
| 8740 about stability. @xref{Q1.1.2, Are binaries available?}. | |
| 8741 | |
| 428 | 8742 @bye |