Mercurial > hg > xemacs-beta
annotate man/xemacs-faq.texi @ 5940:c608d4b0b75e cygwin64 tip
rescue lost branch from 64bit.backup
| author | Henry Thompson <ht@markup.co.uk> |
|---|---|
| date | Thu, 16 Dec 2021 18:48:58 +0000 |
| parents | d11efddf3617 |
| children |
| 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 | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
171 @file{/usr/local/lib/xemacs-21.5/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. |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
191 * Legacy Versions:: New Information about Old XEmacsen. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
192 * Bleeding Edge:: Working with XEmacs Source Code Repositories. |
| 428 | 193 |
| 194 @detailmenu | |
| 195 --- The Detailed Node Listing --- | |
| 196 | |
| 2417 | 197 1 Introduction, Policy, Credits |
| 198 | |
| 2537 | 199 1.0: What is XEmacs? |
| 2417 | 200 * Q1.0.1:: What is XEmacs? |
| 201 * Q1.0.2:: What is the current version of XEmacs? | |
| 2537 | 202 * Q1.0.3:: How do you pronounce XEmacs? |
| 203 * Q1.0.4:: What does XEmacs look like? | |
| 204 * Q1.0.5:: Who wrote XEmacs? | |
| 205 * Q1.0.6:: Who wrote the FAQ? | |
| 206 | |
| 207 1.1: Getting XEmacs | |
| 208 * Q1.1.1:: Where can I find XEmacs? | |
| 209 * Q1.1.2:: Are binaries available? | |
| 210 * Q1.1.3:: How do I get the bleeding-edge sources? | |
| 211 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 212 | |
| 213 1.2: Versions for Different Operating Systems | |
| 214 * Q1.2.1:: Do I need X11 to run XEmacs? | |
| 215 * Q1.2.2:: What versions of Unix does XEmacs run on? | |
| 216 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows? | |
| 217 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 218 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 219 * Q1.2.6:: What are the differences between the various MS Windows emacsen? | |
| 220 * Q1.2.7:: How does the port cope with differences in the Windows user interface? | |
| 221 * Q1.2.8:: Is there a port of XEmacs to the Macintosh? | |
| 222 * Q1.2.9:: Is there a port of XEmacs to MS-DOS? | |
| 223 * Q1.2.10:: Is there a port of XEmacs to OS/2? | |
| 224 * Q1.2.11:: Is there a port of XEmacs to NextStep? | |
| 225 * Q1.2.12:: Is there a port of XEmacs to VMS? | |
| 226 | |
| 227 1.3: Getting Started | |
| 228 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? | |
| 229 * Q1.3.2:: Where do I put my @file{init.el} file? | |
| 230 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs? | |
| 231 * Q1.3.4:: Any good XEmacs tutorials around? | |
| 232 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function? | |
| 233 * Q1.3.6:: And how do I bind it to a key? | |
| 234 * Q1.3.7:: What's the difference between a macro and a function? | |
| 235 * Q1.3.8:: What is @code{Custom}? | |
| 236 | |
| 237 1.4: Getting Help | |
| 238 * Q1.4.1:: Where can I get help? | |
| 239 * Q1.4.2:: Which mailing lists are there? | |
| 2559 | 240 * Q1.4.3:: Where are the mailing lists archived? |
| 241 * Q1.4.4:: How can I get two instances of info? | |
| 242 * Q1.4.5:: How do I add new Info directories? | |
| 2537 | 243 |
| 244 1.5: Contributing to XEmacs | |
| 245 * Q1.5.1:: How do I submit changes to the FAQ? | |
| 246 * Q1.5.2:: How do I become a beta tester? | |
| 247 * Q1.5.3:: How do I contribute to XEmacs itself? | |
| 2559 | 248 * Q1.5.4:: How do I get started developing XEmacs? |
| 249 * Q1.5.5:: What's the basic layout of the code? | |
| 2537 | 250 |
| 251 1.6: Politics (XEmacs vs. GNU Emacs) | |
| 252 * Q1.6.1:: What is GNU Emacs? | |
| 253 * Q1.6.2:: How does XEmacs differ from GNU Emacs? | |
| 254 * Q1.6.3:: How much does XEmacs differ? | |
| 255 * Q1.6.4:: Is XEmacs "GNU"? | |
| 256 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 257 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged? | |
| 258 | |
| 259 1.7: External Packages | |
| 2559 | 260 * Q1.7.1:: What is the package system? |
| 261 * Q1.7.2:: Which external packages are there? | |
| 262 * Q1.7.3:: Do I need to have the packages to run XEmacs? | |
| 263 * Q1.7.4:: Is there a way to find which package has particular functionality? | |
| 2537 | 264 |
| 265 1.8: Internationalization | |
| 266 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)? | |
| 267 * Q1.8.2:: How can I help with internationalization? | |
| 268 * Q1.8.3:: How do I type non-ASCII characters? | |
| 269 * Q1.8.4:: Can XEmacs messages come out in a different language? | |
| 270 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs | |
| 271 * Q1.8.6:: How do I portably code for MULE/XEmacs? | |
| 272 * Q1.8.7:: How about Cyrillic modes? | |
| 273 * Q1.8.8:: Does XEmacs support Unicode? | |
| 274 * Q1.8.9:: How does XEmacs display Unicode? | |
| 2417 | 275 |
| 276 2 Installation and Troubleshooting | |
| 277 | |
| 2559 | 278 2.0: Installation (General) |
| 279 * Q2.0.1:: How do I build and install XEmacs? | |
| 280 * Q2.0.2:: Where do I find external libraries? | |
| 281 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files? | |
| 282 * Q2.0.4:: Running XEmacs without installing | |
| 283 * Q2.0.5:: XEmacs is too big | |
| 284 | |
| 285 2.1: Package Installation | |
| 286 * Q2.1.1:: How do I install the packages? | |
| 287 * Q2.1.2:: Can I install the packages individually? | |
| 288 * Q2.1.3:: Can I install the packages automatically? | |
| 289 * Q2.1.4:: Can I upgrade or remove packages? | |
| 290 * Q2.1.5:: Which packages to install? | |
| 291 * Q2.1.6:: Can you describe the package location process in more detail? | |
| 292 * Q2.1.7:: EFS fails with "500 AUTH not understood" | |
| 293 | |
| 294 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) | |
| 295 * Q2.2.1:: Libraries in non-standard locations | |
| 296 * Q2.2.2:: Why can't I strip XEmacs? | |
| 3404 | 297 * Q2.2.3:: X11/bitmaps/gray (or other X11-related file) not found. |
| 2559 | 298 |
| 299 2.3: Windows Installation (Windows, Cygwin, MinGW) | |
| 300 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows? | |
| 301 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs? | |
| 302 * Q2.3.3:: How do I compile the native port? | |
| 303 * Q2.3.4:: What do I need for Cygwin? | |
| 304 * Q2.3.5:: How do I compile under Cygwin? | |
| 305 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 306 * Q2.3.7:: How do I compile with X support? | |
| 307 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 308 | |
| 309 2.4: General Troubleshooting | |
| 310 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running? | |
| 311 * Q2.4.2:: Help! XEmacs just crashed on me! | |
| 312 * Q2.4.3:: XEmacs crashes and I compiled it myself. | |
| 313 * Q2.4.4:: How to debug an XEmacs problem with a debugger | |
| 314 * Q2.4.5:: I get a cryptic error message when trying to do something. | |
| 315 * Q2.4.6:: XEmacs hangs when I try to do something. | |
| 316 * Q2.4.7:: I get an error message when XEmacs is running in batch mode. | |
| 317 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 318 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken? | |
| 319 * Q2.4.10:: How do I debug process-related problems? | |
| 320 * Q2.4.11:: XEmacs is outputting lots of X errors. | |
| 321 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more! | |
| 322 | |
| 323 2.5: Startup-Related Problems | |
| 324 * Q2.5.1:: XEmacs cannot connect to my X Terminal! | |
| 325 * Q2.5.2:: Startup problems related to paths or package locations. | |
|
4658
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
326 * Q2.5.3:: XEmacs won't start without network, or starts slowly. |
| 2559 | 327 * Q2.5.4:: Startup warnings about deducing proper fonts? |
| 328 * Q2.5.5:: Warnings from incorrect key modifiers. | |
| 329 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? | |
|
5390
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
330 * Q2.5.7:: XEmacs issues messages about ``auto-autoloads already loaded.'' |
| 2417 | 331 |
| 2459 | 332 3 Editing Functions |
| 2417 | 333 |
| 334 3.0: The Keyboard | |
| 2459 | 335 * Q3.0.1:: How can I customize the keyboard? |
| 336 * Q3.0.2:: How can I bind complex functions (or macros) to keys? | |
| 337 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down? | |
| 338 * Q3.0.4:: Globally binding @kbd{Delete}? | |
| 339 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 340 * Q3.0.6:: How can you type in special characters in XEmacs? | |
| 341 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys? | |
| 342 * Q3.0.8:: How do I map the arrow keys? | |
| 343 * Q3.0.9:: HP Alt key as Meta. | |
| 344 * Q3.0.10:: Why does edt emulation not work? | |
| 345 * 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
|
346 * Q3.0.12:: Mac Alt/Option key as Meta. |
| 2417 | 347 |
| 348 3.1: The Mouse | |
| 349 * Q3.1.1:: How can I turn off Mouse pasting? | |
| 350 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons? | |
| 351 * Q3.1.3:: Clicking the left button does not do anything in buffer list. | |
| 352 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3? | |
| 2459 | 353 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is? |
| 354 | |
| 355 3.2: Buffers, Text Editing | |
| 356 * Q3.2.1:: Can I have the end of the buffer delimited in some way? | |
| 357 * Q3.2.2:: How do I insert today's date into a buffer? | |
| 358 * Q3.2.3:: How do I get a single minibuffer frame? | |
| 359 * Q3.2.4:: How can I enable auto-indent and/or Filladapt? | |
| 360 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 361 | |
| 362 3.3: Text Selections | |
| 363 * Q3.3.1:: How do I select a rectangular region? | |
| 364 * Q3.3.2:: How can I turn off or change highlighted selections? | |
| 365 * Q3.3.3:: How do I cause typing on an active region to remove it? | |
| 366 * Q3.3.4:: Can I turn off the highlight during isearch? | |
| 367 * Q3.3.5:: Why is killing so slow? | |
| 368 * Q3.3.6:: Why does @kbd{M-w} take so long? | |
| 369 | |
| 370 3.4: Editing Source Code | |
| 371 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode? | |
| 372 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly? | |
| 373 | |
| 374 4 Display Functions | |
| 375 | |
| 376 4.0: Textual Fonts and Colors | |
| 377 * Q4.0.1:: How do I specify a font? | |
| 378 * Q4.0.2:: How do I set the text, menu and modeline fonts? | |
| 379 * Q4.0.3:: How can I set color options from @file{init.el}? | |
| 380 * Q4.0.4:: How can I set the colors when highlighting a region? | |
| 381 * Q4.0.5:: How can I limit color map usage? | |
| 382 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them. | |
| 383 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs? | |
| 384 * Q4.0.8:: How do I display non-ASCII characters? | |
| 385 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}. | |
| 386 | |
| 387 4.1: Syntax Highlighting (Font Lock) | |
| 388 * Q4.1.1:: How can I do source code highlighting using font-lock? | |
| 389 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default? | |
| 390 | |
| 391 4.2: The Modeline | |
| 392 * Q4.2.1:: How can I make the modeline go away? | |
| 393 * Q4.2.2:: How do you have XEmacs display the line number in the modeline? | |
| 394 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline? | |
| 395 * Q4.2.4:: How can I change the modeline color based on the mode used? | |
| 396 | |
| 397 4.3: The Cursor | |
| 398 * Q4.3.1:: Is there a way to make the bar cursor thicker? | |
| 399 * Q4.3.2:: Is there a way to get back the block cursor? | |
| 400 * Q4.3.3:: Can I make the cursor blink? | |
| 401 | |
| 402 4.4: The Menubar | |
| 403 * Q4.4.1:: How do I get rid of the menubar? | |
| 404 * Q4.4.2:: How can I customize the menubar? | |
| 405 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 406 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 407 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working? | |
| 408 | |
| 409 4.5: The Toolbar | |
| 410 * Q4.5.1:: How do I get rid of the toolbar? | |
| 411 * Q4.5.2:: How can I customize the toolbar? | |
| 412 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar? | |
| 413 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar | |
| 414 | |
| 415 4.6: Scrollbars and Scrolling | |
| 416 * Q4.6.1:: How can I disable the scrollbar? | |
| 417 * Q4.6.2:: How can I change the scrollbar width? | |
| 418 * Q4.6.3:: How can I use resources to change scrollbar colors? | |
| 419 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this? | |
| 420 * Q4.6.5:: Scrolling one line at a time. | |
| 421 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes? | |
| 422 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off? | |
| 423 | |
| 424 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 425 * Q4.7.1:: How can I disable the gutter tabs? | |
| 426 * Q4.7.2:: How can I disable the progress bar? | |
| 427 * Q4.7.3:: There are bugs in the gutter or widgets. | |
| 428 * Q4.7.4:: How can I customize the gutter or gutter tabs? | |
| 429 | |
| 430 5 Interfacing with the Operating System and External Devices | |
| 431 | |
| 432 5.0: X Window System and Resources | |
| 433 * Q5.0.1:: Where is a list of X resources? | |
| 434 * Q5.0.2:: How can I detect a color display? | |
| 435 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}? | |
| 436 * Q5.0.4:: How can I have the window title area display the full path? | |
| 437 * Q5.0.5:: @samp{xemacs -name junk} doesn't work? | |
| 438 * 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
|
439 * Q5.0.7:: How can I use antialiased fonts under X11? |
| 2459 | 440 |
| 441 5.1: Microsoft Windows | |
| 442 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? | |
| 443 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 444 | |
| 445 5.2: Printing | |
| 446 * Q5.2.1:: What do I need to change to make printing work? | |
| 447 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer? | |
| 448 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 449 * Q5.2.4:: Can you print under MS Windows? | |
| 450 | |
| 451 5.3: Sound | |
| 452 * Q5.3.1:: How do I turn off the sound? | |
| 453 * Q5.3.2:: How do I get funky sounds instead of a boring beep? | |
| 454 * Q5.3.3:: What are NAS and ESD (EsounD)? | |
| 455 * Q5.3.4:: Sunsite sounds don't play. | |
| 456 | |
| 457 5.4: Running an Interior Shell, Invoking Subprocesses | |
| 458 * Q5.4.1:: What is an interior shell? | |
| 459 * Q5.4.2:: How do I start up a second shell buffer? | |
| 460 * Q5.4.3:: Telnet from shell filters too much | |
| 461 * Q5.4.4:: Strange things are happening in Shell Mode. | |
| 462 * Q5.4.5:: XEmacs complains "No such file or directory, diff" | |
| 2995 | 463 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed" |
| 2459 | 464 |
| 465 5.5: Multiple Device Support | |
| 466 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display? | |
| 467 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 468 * Q5.5.3:: How do I disable gnuserv from opening a new frame? | |
| 469 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 470 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 471 | |
| 472 6 Connecting to the Internet | |
| 473 | |
| 474 6.0: General Mail and News | |
| 475 * Q6.0.1:: What are the various packages for reading mail? | |
| 476 * Q6.0.2:: How can I send mail? | |
| 477 * Q6.0.3:: How do I get my outgoing mail archived? | |
| 478 * Q6.0.4:: How can I read and/or compose MIME messages? | |
| 479 * Q6.0.5:: How do I customize the From line? | |
| 480 * Q6.0.6:: How do I get my MUA to filter mail for me? | |
| 481 * Q6.0.7:: Remote mail reading with an MUA. | |
| 482 * Q6.0.8:: An MUA gets an error incorporating new mail. | |
| 483 * Q6.0.9:: Why isn't @file{movemail} working? | |
| 484 * Q6.0.10:: How do I make my MUA display graphical smilies? | |
| 485 * Q6.0.11:: How can I get those oh-so-neat X-Face lines? | |
| 486 | |
| 487 6.1: Reading Mail with VM | |
| 488 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP? | |
| 489 * Q6.1.2:: How can I get VM to automatically check for new mail? | |
| 490 * 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"? | |
| 491 * Q6.1.4:: Is there a mailing list or FAQ for VM? | |
| 492 * Q6.1.5:: How do I make VM stay in a single frame? | |
| 493 * Q6.1.6:: Customization of VM not covered in the manual, or here. | |
| 494 | |
| 495 6.2: Reading Netnews and Mail with Gnus | |
| 496 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 497 * Q6.2.2:: How do I make Gnus stay within a single frame? | |
| 498 | |
| 499 6.3: FTP Access | |
| 500 * Q6.3.1:: Can I edit files on other hosts? | |
| 501 * Q6.3.2:: What is EFS? | |
| 502 | |
| 503 6.4: Web Browsing with W3 | |
| 504 * Q6.4.1:: What is W3? | |
| 505 * Q6.4.2:: How do I run W3 from behind a firewall? | |
| 506 * Q6.4.3:: Is it true that W3 supports style sheets and tables? | |
| 507 | |
| 508 7 Advanced Customization Using XEmacs Lisp | |
| 509 | |
| 2537 | 510 7.0: Emacs Lisp and @file{init.el} |
| 511 * Q7.0.1:: What version of Emacs am I running? | |
| 512 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions? | |
| 513 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. | |
| 514 * Q7.0.4:: How can I add directories to the @code{load-path}? | |
| 515 * Q7.0.5:: How to check if a lisp function is defined? | |
| 516 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? | |
| 517 | |
| 518 7.1: Emacs Lisp Programming Techniques | |
| 519 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 520 * Q7.1.2:: Can I generate "fake" keyboard events? | |
| 521 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? | |
| 522 * Q7.1.4:: What is the performance hit of @code{let}? | |
| 523 * Q7.1.5:: What is the recommended use of @code{setq}? | |
| 524 * Q7.1.6:: What is the typical misuse of @code{setq}? | |
| 525 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down? | |
| 526 * Q7.1.8:: I like recursion, does it slow things down? | |
| 527 * Q7.1.9:: How do I put a glyph as annotation in a buffer? | |
| 528 * Q7.1.10:: @code{map-extents} won't traverse all of my extents! | |
| 529 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 530 | |
| 531 7.2: Mathematics | |
| 2559 | 532 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp? |
| 533 * Q7.2.2:: XEmacs segfaults when I use very big numbers! | |
| 534 * Q7.2.3:: Bignums are really slow! | |
| 535 * Q7.2.4:: Equal bignums don't compare as equal! What gives? | |
| 2459 | 536 |
| 537 8 Other External Packages | |
| 538 | |
| 539 8.0: TeX | |
| 540 * Q8.0.1:: Is there something better than LaTeX mode? | |
| 541 * Q8.0.2:: What is AUCTeX? Where do you get it? | |
| 542 * Q8.0.3:: Problems installing AUCTeX. | |
| 543 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline? | |
| 544 | |
| 545 8.1: Other Unbundled Packages | |
| 546 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 547 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets? | |
| 548 * Q8.1.3:: Is there a MatLab mode? | |
| 549 | |
| 550 8.2: Environments Built Around XEmacs | |
| 551 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop? | |
| 552 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21? | |
| 553 * Q8.2.3:: What is/was Energize? | |
| 554 * Q8.2.4:: What is Infodock? | |
| 555 | |
| 556 9 What the Future Holds | |
| 557 | |
| 558 9.0: Changes | |
| 559 * Q9.0.1:: What new features will be in XEmacs soon? | |
| 560 * Q9.0.2:: What's new in XEmacs 21.4? | |
| 561 * Q9.0.3:: What's new in XEmacs 21.1? | |
| 562 * Q9.0.4:: What's new in XEmacs 20.4? | |
| 563 * Q9.0.5:: What's new in XEmacs 20.3? | |
| 564 * Q9.0.6:: What's new in XEmacs 20.2? | |
| 565 | |
| 566 10 New information about old XEmacsen | |
| 567 | |
| 568 10.0: XEmacs 21.1 | |
| 569 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. | |
| 2559 | 570 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1. |
| 571 | |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
572 11 Working with XEmacs source code repositories |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
573 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
574 11.0: The XEmacs repositories |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
575 * Q11.0.1:: Where is the most recent XEmacs development code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
576 * Q11.0.2:: Where is the most recent XEmacs stable code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
577 * Q11.0.3:: Where is the most recent XEmacs package code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
578 * Q11.0.4:: Why isn't @var{package} available? and what to do about it. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
579 * Q11.0.5:: How do I get commit access? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
580 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
581 11.1: Working with CVS |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
582 * Q11.1.1:: How do I keep cool using CVS? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
583 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
584 11.2: Working with Mercurial |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
585 * Q11.2.1:: What is Mercurial? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
586 * Q11.2.2:: Where do I get Mercurial? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
587 * Q11.2.3:: Do I really have to waste space on history? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
588 * Q11.2.4:: @code{hg diff} gives bizarre output. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
589 * Q11.2.5:: How do I recover from a bad commit? (I already pushed.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
590 * Q11.2.6:: How do I recover from a bad commit? (I haven't pushed yet.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
591 * Q11.2.7:: Testing patches with Mercurial Queues. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
592 |
| 428 | 593 @end detailmenu |
| 594 @end menu | |
| 595 | |
| 596 @node Introduction, Installation, Top, Top | |
| 597 @unnumbered 1 Introduction, Policy, Credits | |
| 598 | |
| 599 Learning XEmacs is a lifelong activity. Even people who have used Emacs | |
| 600 for years keep discovering new features. Therefore this document cannot | |
| 601 be complete. Instead it is aimed at the person who is either | |
| 602 considering XEmacs for their own use, or has just obtained it and is | |
| 603 wondering what to do next. It is also useful as a reference to | |
| 604 available resources. | |
| 605 | |
| 2417 | 606 The previous maintainer of the FAQ was |
| 607 @email{rossini@@biostat.washington.edu, Anthony Rossini}, who started | |
| 608 it, after getting tired of hearing JWZ complain about repeatedly | |
| 609 having to answer questions. @email{ben@@xemacs.org, Ben Wing} then | |
| 610 took over and did a massive update reorganizing the whole thing. At | |
| 611 this point Anthony took back over, but then had to give it up again. | |
| 612 Some of the other contributors to this FAQ are listed later in this | |
| 613 document. | |
| 428 | 614 |
| 615 The previous version was converted to hypertext format, and edited by | |
| 616 @email{steve@@xemacs.org, Steven L. Baur}. It was converted back to | |
| 434 | 617 texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then |
| 618 maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it | |
| 2417 | 619 on to ChristianNyb@o{}, and then to @email{wambold@@xemacs.org,Sandra Wambold}. |
| 620 | |
| 621 The current version of the FAQ has been heavily redone by | |
| 622 @email{ben@@xemacs.org, Ben Wing}. | |
| 428 | 623 |
| 624 If you notice any errors or items which should be added or amended to | |
| 2417 | 625 this FAQ please send email to @email{xemacs-beta@@xemacs.org}. |
| 626 Include @samp{XEmacs FAQ} on the Subject: line. | |
| 428 | 627 |
| 628 @menu | |
| 2537 | 629 1.0: What is XEmacs? |
| 2417 | 630 * Q1.0.1:: What is XEmacs? |
| 631 * Q1.0.2:: What is the current version of XEmacs? | |
| 2537 | 632 * Q1.0.3:: How do you pronounce XEmacs? |
| 633 * Q1.0.4:: What does XEmacs look like? | |
| 634 * Q1.0.5:: Who wrote XEmacs? | |
| 635 * Q1.0.6:: Who wrote the FAQ? | |
| 636 | |
| 637 1.1: Getting XEmacs | |
| 638 * Q1.1.1:: Where can I find XEmacs? | |
| 639 * Q1.1.2:: Are binaries available? | |
| 640 * Q1.1.3:: How do I get the bleeding-edge sources? | |
| 641 * Q1.1.4:: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 642 | |
| 643 1.2: Versions for Different Operating Systems | |
| 644 * Q1.2.1:: Do I need X11 to run XEmacs? | |
| 645 * Q1.2.2:: What versions of Unix does XEmacs run on? | |
| 646 * Q1.2.3:: Is there a port of XEmacs to Microsoft Windows? | |
| 647 * Q1.2.4:: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 648 * Q1.2.5:: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 649 * Q1.2.6:: What are the differences between the various MS Windows emacsen? | |
| 650 * Q1.2.7:: How does the port cope with differences in the Windows user interface? | |
| 651 * Q1.2.8:: Is there a port of XEmacs to the Macintosh? | |
| 652 * Q1.2.9:: Is there a port of XEmacs to MS-DOS? | |
| 653 * Q1.2.10:: Is there a port of XEmacs to OS/2? | |
| 654 * Q1.2.11:: Is there a port of XEmacs to NextStep? | |
| 655 * Q1.2.12:: Is there a port of XEmacs to VMS? | |
| 656 | |
| 657 1.3: Getting Started | |
| 658 * Q1.3.1:: What is an @file{init.el} or @file{.emacs} and is there a sample one? | |
| 659 * Q1.3.2:: Where do I put my @file{init.el} file? | |
| 660 * Q1.3.3:: Can I use the same @file{init.el} with the other Emacs? | |
| 661 * Q1.3.4:: Any good XEmacs tutorials around? | |
| 662 * Q1.3.5:: May I see an example of a useful XEmacs Lisp function? | |
| 663 * Q1.3.6:: And how do I bind it to a key? | |
| 664 * Q1.3.7:: What's the difference between a macro and a function? | |
| 665 * Q1.3.8:: What is @code{Custom}? | |
| 666 | |
| 667 1.4: Getting Help | |
| 668 * Q1.4.1:: Where can I get help? | |
| 669 * Q1.4.2:: Which mailing lists are there? | |
| 2559 | 670 * Q1.4.3:: Where are the mailing lists archived? |
| 671 * Q1.4.4:: How can I get two instances of info? | |
| 672 * Q1.4.5:: How do I add new Info directories? | |
| 2537 | 673 |
| 674 1.5: Contributing to XEmacs | |
| 675 * Q1.5.1:: How do I submit changes to the FAQ? | |
| 676 * Q1.5.2:: How do I become a beta tester? | |
| 677 * Q1.5.3:: How do I contribute to XEmacs itself? | |
| 2559 | 678 * Q1.5.4:: How do I get started developing XEmacs? |
| 679 * Q1.5.5:: What's the basic layout of the code? | |
| 2537 | 680 |
| 681 1.6: Politics (XEmacs vs. GNU Emacs) | |
| 682 * Q1.6.1:: What is GNU Emacs? | |
| 683 * Q1.6.2:: How does XEmacs differ from GNU Emacs? | |
| 684 * Q1.6.3:: How much does XEmacs differ? | |
| 685 * Q1.6.4:: Is XEmacs "GNU"? | |
| 686 * Q1.6.5:: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 687 * Q1.6.6:: Why haven't XEmacs and GNU Emacs merged? | |
| 688 | |
| 689 1.7: External Packages | |
| 2559 | 690 * Q1.7.1:: What is the package system? |
| 691 * Q1.7.2:: Which external packages are there? | |
| 692 * Q1.7.3:: Do I need to have the packages to run XEmacs? | |
| 693 * Q1.7.4:: Is there a way to find which package has particular functionality? | |
| 2537 | 694 |
| 695 1.8: Internationalization | |
| 696 * Q1.8.1:: What is the status of internationalization support aka MULE (including Asian language support)? | |
| 697 * Q1.8.2:: How can I help with internationalization? | |
| 698 * Q1.8.3:: How do I type non-ASCII characters? | |
| 699 * Q1.8.4:: Can XEmacs messages come out in a different language? | |
| 700 * Q1.8.5:: Please explain the various input methods in MULE/XEmacs | |
| 701 * Q1.8.6:: How do I portably code for MULE/XEmacs? | |
| 702 * Q1.8.7:: How about Cyrillic modes? | |
| 703 * Q1.8.8:: Does XEmacs support Unicode? | |
| 704 * Q1.8.9:: How does XEmacs display Unicode? | |
| 428 | 705 @end menu |
| 706 | |
| 2537 | 707 @unnumberedsec 1.0: What is XEmacs? |
| 2417 | 708 |
| 428 | 709 @node Q1.0.1, Q1.0.2, Introduction, Introduction |
| 710 @unnumberedsubsec Q1.0.1: What is XEmacs? | |
| 711 | |
| 479 | 712 XEmacs is a powerful, highly customizable open source text editor and |
| 2417 | 713 application development system, with full GUI support. It is |
| 714 protected under the GNU Public License and related to other versions | |
| 715 of Emacs, in particular GNU Emacs. Its emphasis is on modern | |
| 716 graphical user interface support and an open software development | |
| 717 model, similar to Linux. XEmacs has an active development community | |
| 718 numbering in the hundreds (and thousands of active beta testers on top | |
| 719 of this), and runs on all versions of MS Windows, on Mac OS X, on | |
| 720 Linux, and on nearly every other version of Unix in existence. | |
| 721 Support for XEmacs has been supplied by Sun Microsystems, University | |
| 722 of Illinois, Lucid, ETL/Electrotechnical Laboratory, Amdahl | |
| 723 Corporation, BeOpen, and others, as well as the unpaid time of a great | |
| 724 number of individual developers. | |
| 428 | 725 |
| 726 @node Q1.0.2, Q1.0.3, Q1.0.1, Introduction | |
| 727 @unnumberedsubsec Q1.0.2: What is the current version of XEmacs? | |
| 728 | |
| 2417 | 729 XEmacs versions 21.4.* are releases made from the current stable |
| 730 sources. XEmacs versions 21.5.* (which will be released as 22.0) are | |
| 731 releases made from the development sources. Check at | |
| 732 @uref{http://www.xemacs.org} for the current minor version. XEmacs | |
| 733 versions 21.1.* were the previous stable releases, now retired. | |
| 734 | |
| 735 XEmacs 20.4, released in February 1998, was the last release of v20. | |
| 736 | |
| 737 XEmacs 19.16, released in November, 1997. was the last release of v19, | |
| 738 and was also the last version without international language support. | |
| 428 | 739 |
| 740 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction | |
| 2537 | 741 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs? |
| 742 | |
|
5384
3889ef128488
Fix misspelled words, and some grammar, across the entire source tree.
Jerry James <james@xemacs.org>
parents:
5028
diff
changeset
|
743 The most common pronunciation is @samp{Eks eemax}, @samp{Eks'im&ks} in |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
744 Kirshenbaum IPA. (See |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
745 @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
|
746 already and want to know how to map from Kirshenbaum to it.) |
| 428 | 747 |
| 748 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction | |
| 2537 | 749 @unnumberedsubsec Q1.0.4: What does XEmacs look like? |
| 750 | |
| 751 Screen snapshots are available at | |
| 752 @uref{http://www.xemacs.org/About/Screenshots/index.html} | |
| 753 as part of the XEmacs website. | |
| 754 | |
| 755 @node Q1.0.5, Q1.0.6, Q1.0.4, Introduction | |
| 756 @unnumberedsubsec Q1.0.5: Who wrote XEmacs? | |
| 757 | |
| 758 XEmacs is the result of the time and effort of many people, and the | |
| 759 active developers have changed over time. There are two major | |
| 760 components of the XEmacs effort -- writing the code itself and providing | |
| 761 all the support work (testing the code, releasing beta and final | |
| 762 versions, handling patches, reading bug reports, maintaining the web | |
| 763 site, managing the mailing lists, etc. etc.). Neither component would | |
| 764 work without the other. | |
| 765 | |
| 766 @subheading CODING | |
| 767 | |
| 768 The primary code contributor over the years has been Ben Wing (active | |
| 769 since late 1992). Between 1991 and 1995, large amounts of coding was | |
| 770 contributed by Jamie Zawinski and Chuck Thompson. Many other people | |
| 771 have authored major subsystems or otherwise contributed large amounts of | |
| 772 code, including Andy Piper, Hrvoje Niksic, Jerry James, Jonathan Harris, | |
| 773 Kyle Jones, Martin Buchholz, Michael Sperber, Olivier Galibert, Richard | |
| 774 Mlynarik, Stig, William Perry and plenty of others. | |
| 775 | |
| 776 Primary XEmacs-specific subsystems and their authors: | |
| 777 | |
| 778 @table @asis | |
| 779 @item Objects | |
| 780 @itemize @minus | |
| 781 @item | |
| 782 Conversion from 26-bit to 28-bit pointers and integers, lrecords, lcrecords: Richard Mlynarik, 1994 | |
| 783 @item | |
| 784 Conversion to 32-bit pointers and 31-bit integers: Kyle Jones, Martin Buchholz | |
| 785 @item | |
| 786 Portable dumper, object descriptions: Olivier Galibert | |
| 787 @item | |
| 788 KKCC (new garbage collector), ephemerons, weak boxes: Michael Sperber and students | |
| 789 @item | |
| 790 Random object work (object equal and hash methods, weak lists, lcrecord lists, bit vectors, dynarr, blocktype, opaque, string resizing): Ben Wing | |
| 791 @item | |
| 792 Profiling: Ben Wing | |
| 793 @item | |
| 794 Some byte-compilation and hash-table improvements: Martin Buchholz | |
| 795 @item | |
| 796 Bignum: Jerry James | |
| 797 @end itemize | |
| 798 | |
| 799 @item Internationalization/Mule | |
| 800 @itemize @minus | |
| 801 @item | |
| 802 mostly Ben Wing; many ideas for future work, Stephen Turnbull | |
| 803 @end itemize | |
| 804 | |
| 805 @item I/O | |
| 806 @itemize @minus | |
| 807 @item | |
| 808 Basic event/event-stream implementation: Jamie Zawinski | |
| 809 @item | |
| 810 Most event work since 1994: Ben Wing | |
| 811 @item | |
| 812 Asynchronous stuff (async timeouts, signals, quit-checking): Ben Wing | |
| 813 @item | |
| 814 Process method abstraction, Windows process work: Kirill Katsnelson | |
| 815 @item | |
| 816 Misc-user events, async timeouts, most quit-checking and signal code, most other work since 1994: Ben Wing | |
| 817 @item | |
| 818 Lstreams: Ben Wing | |
| 819 @end itemize | |
| 820 | |
| 821 @item Display | |
| 822 @itemize @minus | |
| 823 @item | |
| 824 Redisplay mechanism: implementation, Chuck Thompson; additional work, lots of people | |
| 825 @item | |
| 826 Glyphs: mostly Ben Wing | |
| 827 @item | |
| 828 Specifiers: Ben Wing | |
| 829 @item | |
| 830 Extents: initial implementation, someone at Lucid; rewrite, 1994, Ben Wing | |
| 831 @item | |
| 832 Widgets: Andy Piper | |
| 833 @item | |
| 834 JPEG/PNG/TIFF image converters: Ben Wing, William Perry, Jareth Hein, others (see comment in @file{glyphs-eimage.c}) | |
| 835 @item | |
| 836 Menus: Jamie Zawinski, someone at Lucid (Lucid menus) | |
| 837 @item | |
| 838 Scrollbars: Chuck Thompson, ??? (Lucid scrollbar) | |
| 839 @item | |
| 840 Multi-device/device-independence work (console/device/etc methods): Ben Wing, prototype by chuck thompson | |
| 841 @item | |
| 842 Faces: first implementation, Jamie Zawinski; second, chuck; third, Ben Wing | |
| 843 @item | |
| 844 Fonts/colors: first implementation, Jamie Zawinski; further work, Ben Wing | |
| 845 @item | |
| 846 Toolbars: implementation, chuck, much interface work, Ben Wing | |
| 847 @item | |
| 848 Gutters, tabs: andy piper | |
| 849 @end itemize | |
| 850 | |
| 851 @item Device subsystems | |
| 852 @itemize @minus | |
| 853 @item | |
| 4311 | 854 X Windows: Jamie Zawinski, Ben Wing, others |
| 2537 | 855 @item |
| 856 GTK: William Perry, Malcolm Purvis | |
| 857 @item | |
| 858 MS Windows: initial implementation, Jonathan Harris; some more work, Andy Piper, Ben Wing | |
| 859 @item | |
| 860 TTY: Chuck Thompson, Ben Wing | |
| 861 @item | |
| 862 Cygwin: Andy Piper | |
| 863 @end itemize | |
| 864 | |
| 865 @item Misc | |
| 866 @itemize @minus | |
| 867 @item | |
| 868 Configure: initial porting from fsf, Chuck Thompson; conversion to autoconf 2, much rewriting, Martin Buchholz | |
| 869 @item | |
| 870 Most initialization-related code: Ben Wing | |
| 871 @item | |
| 872 Internals manual, much of Lisp manual: Ben Wing | |
| 873 @item | |
| 874 FSF synching: initial sync with FSF 19, Richard Mlynarik, further work, Ben Wing | |
| 875 @end itemize | |
| 876 @end table | |
| 877 | |
| 878 @subheading SUPPORT | |
| 879 | |
| 880 Currently, support duties are handled by many different people. | |
| 881 | |
| 882 Release managers have been | |
| 883 | |
| 884 @itemize @minus | |
| 885 @item | |
| 886 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) | |
| 887 @item | |
| 888 Vin Shelton (May 2003 - present, 21.4.13 - present) | |
| 889 @item | |
| 890 Steve Youngs (July 2002 - September 2003, 21.5.8 - 21.5.16) | |
| 891 @item | |
| 892 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) | |
| 893 @item | |
| 894 Steve Baur (early 1997 - December 1998, February 1999 - November 1999, 19.15 - 21.2.5, 21.2.9 - 21.2.20) | |
| 895 @item | |
| 896 Andy Piper (December 1998, 21.2.6) | |
| 897 @item | |
| 898 Chuck Thompson (June 1994 - September 1996, 19.11 - 19.14) | |
| 899 @item | |
| 900 Jamie Zawinski (April 1991 - June 1994, 19.0 - 19.10) | |
| 901 @end itemize | |
| 902 | |
| 903 The recent overlapping dates are intentional, since two or three trees | |
| 904 are maintained simultaneously at any point. | |
| 905 | |
| 906 Other major support work: | |
| 907 | |
| 908 @itemize @minus | |
| 909 @item | |
| 910 Adrian Aichner wrote and maintains the web site. | |
| 911 @item | |
| 912 Stephen Turnbull has produced many of the beta and semi-stable releases | |
| 913 and has attempted to be the "face" of XEmacs on the newsgroups and | |
| 914 mailing lists. | |
| 915 @item | |
| 916 Steve Youngs currently produces the beta releases (???). | |
| 917 @item | |
| 4311 | 918 Steve Youngs, Ville Skyttä, and now Norbert Koch have taken turns |
| 2537 | 919 maintaining the packages. |
| 920 @item | |
| 921 Vin Shelton maintains the stable releases. | |
| 922 @item | |
| 923 Testing - #### Norbert, Adrian, ??? | |
| 924 @end itemize | |
| 925 | |
| 926 Portraits and email of some of the major developers: | |
| 927 | |
| 928 @itemize @bullet | |
| 929 @item @email{andy@@xemacs.org, Andy Piper} | |
| 930 @html | |
| 931 <br><img src="piper.png" alt="Portrait of Andy Piper"><br> | |
| 932 @end html | |
| 933 | |
| 934 @item @email{ben@@xemacs.org, Ben Wing} | |
| 935 @html | |
| 936 <br><img src="ben.png" alt="Portrait of Ben Wing"><br> | |
| 937 @end html | |
| 938 | |
| 939 @item @email{cthomp@@xemacs.org, Chuck Thompson} | |
| 940 @html | |
| 941 <br><img src="cthomp.png" alt="Portrait of Chuck Thompson"><br> | |
| 942 @end html | |
| 943 | |
| 944 @item @email{hniksic@@xemacs.org, Hrvoje Niksic} | |
| 945 | |
| 946 @html | |
| 947 <br><img src="hniksic.png" alt="Portrait of Hrvoje Niksic"><br> | |
| 948 @end html | |
| 949 | |
| 950 @item @email{jwz@@jwz.org, Jamie Zawinski} | |
| 951 @html | |
| 952 <br><img src="jwz.png" alt="Portrait of Jamie Zawinski"><br> | |
| 953 @end html | |
| 954 | |
| 955 @item @email{martin@@xemacs.org, Martin Buchholz} | |
| 956 @html | |
| 957 <br><img src="martin.png" alt="Portrait of Martin Buchholz"><br> | |
| 958 @end html | |
| 959 | |
| 960 @item @email{mly@@adoc.xerox.com, Richard Mlynarik} | |
| 961 @html | |
| 962 <br><img src="mly.png" alt="Portrait of Richard Mlynarik"><br> | |
| 963 @end html | |
| 964 | |
| 965 @item @email{stephen@@xemacs.org, Stephen Turnbull} | |
| 966 | |
| 967 @item @email{steve@@xemacs.org, Steve Baur} | |
| 968 @html | |
| 969 <br><img src="slb.png" alt="Portrait of Steve Baur"><br> | |
| 970 @end html | |
| 971 @end itemize | |
| 972 | |
| 973 Many other people have contributed to XEmacs; this is partially | |
| 974 enumerated in the @samp{About XEmacs} option in the Help menu. | |
| 975 | |
| 976 @node Q1.0.6, Q1.1.1, Q1.0.5, Introduction | |
| 977 @unnumberedsubsec Q1.0.6: Who wrote the FAQ? | |
| 978 | |
| 979 The current version of this FAQ was created by @email{ben@@xemacs.org, | |
| 980 Ben Wing}. | |
| 981 | |
| 982 Previous contributors to the FAQ include | |
| 983 | |
| 984 @itemize @bullet | |
| 985 @item @email{steve@@xemacs.org, SL Baur} | |
| 986 | |
| 987 @item @email{hniksic@@xemacs.org, Hrvoje Niksic} | |
| 988 | |
| 989 @item @email{binge@@aloft.att.com, Curtis.N.Bingham} | |
| 990 | |
| 991 @item @email{bruncott@@dormeur.inria.fr, Georges Brun-Cottan} | |
| 992 | |
| 993 @item @email{rjc@@cogsci.ed.ac.uk, Richard Caley} | |
| 994 | |
| 995 @item @email{cognot@@ensg.u-nancy.fr, Richard Cognot} | |
| 996 | |
| 997 @item @email{daku@@nortel.ca, Mark Daku} | |
| 998 | |
| 999 @item @email{wgd@@martigny.ai.mit.edu, William G. Dubuque} | |
| 1000 | |
| 1001 @item @email{eeide@@cs.utah.edu, Eric Eide} | |
| 1002 | |
| 1003 @item @email{af@@biomath.jussieu.fr, Alain Fauconnet} | |
| 1004 | |
| 1005 @item @email{cflatter@@nrao.edu, Chris Flatters} | |
| 1006 | |
| 1007 @item @email{ginsparg@@adra.com, Evelyn Ginsparg} | |
| 1008 | |
| 1009 @item @email{hall@@aplcenmp.apl.jhu.edu, Marty Hall} | |
| 1010 | |
| 1011 @item @email{dkindred@@cmu.edu, Darrell Kindred} | |
| 1012 | |
| 1013 @item @email{dmoore@@ucsd.edu, David Moore} | |
| 1014 | |
| 1015 @item @email{arup+@@cmu.edu, Arup Mukherjee} | |
| 1016 | |
| 1017 @item @email{nickel@@prz.tu-berlin.de, Juergen Nickelsen} | |
| 1018 | |
| 1019 @item @email{powell@@csl.ncsa.uiuc.edu, Kevin R. Powell} | |
| 1020 | |
| 1021 @item @email{dworkin@@ccs.neu.edu, Justin Sheehy} | |
| 1022 | |
| 1023 @item @email{stig@@hackvan.com, Stig} | |
| 1024 | |
| 1025 @item @email{Aki.Vehtari@@hut.fi, Aki Vehtari} | |
| 1026 @end itemize | |
| 1027 | |
| 1028 @unnumberedsec 1.1: Getting XEmacs | |
| 1029 | |
| 1030 @node Q1.1.1, Q1.1.2, Q1.0.6, Introduction | |
| 1031 @unnumberedsubsec Q1.1.1: Where can I find XEmacs? | |
| 1032 | |
| 1033 To download XEmacs, visit the XEmacs WWW page at | |
| 1034 @uref{http://www.xemacs.org/Download/}. The most up-to-date list of | |
| 1035 distribution sites can always be found there. Try to pick a site that | |
| 1036 is networkologically close to you. If you know of other mirrors of | |
| 1037 the XEmacs archives, please send e-mail to | |
| 1038 @uref{mailto:webmaster@@xemacs.org} and we will list them here as well. | |
| 1039 | |
| 1040 The canonical distribution point is ftp.xemacs.org, available either | |
| 1041 through HTTP (@uref{http://ftp.xemacs.org/}) or anonymous FTP | |
| 1042 (@uref{ftp://ftp.xemacs.org/pub/xemacs/}). | |
| 1043 | |
| 1044 @node Q1.1.2, Q1.1.3, Q1.1.1, Introduction | |
| 1045 @unnumberedsubsec Q1.1.2: Are binaries available? | |
| 2417 | 1046 |
| 1047 MS Windows binaries are available at | |
| 1048 @uref{http://www.xemacs.org/Download/win32/} for the native versions | |
| 1049 of 21.4 and 21.1. Cygwin binaries are now available as part of the | |
| 1050 standard Cygwin installation process. XEmacs also comes pre-built as | |
| 1051 part of many Linux distributions, such as Red Hat and SuSE. | |
| 1052 | |
| 1053 Otherwise, you will need to build XEmacs yourself or get your system | |
| 1054 administrator to do it. Generally, this is not a difficult process | |
| 1055 under Unix and Mac OS X, as XEmacs has been tested under all of the | |
| 1056 common Unix versions and under Mac OS X and comes with an extensive | |
| 1057 configure script that is able to automatically detect most aspects of | |
| 1058 the configuration of your particular system. | |
| 1059 | |
| 2537 | 1060 @node Q1.1.3, Q1.1.4, Q1.1.2, Introduction |
| 1061 @unnumberedsubsec Q1.1.3: How do I get the bleeding-edge sources? | |
| 1062 | |
| 1063 If you are interested in developing XEmacs, or getting the absolutely most | |
| 1064 recent, up-to-the-moment, bleeding-edge source code, you can directly | |
| 1065 access the master CVS source tree (read-only, of course, until you ask for | |
| 1066 and are granted permission to directly modify portions of the source tree) | |
| 1067 at cvs.xemacs.org. Directions on how to access the source tree are located | |
| 1068 at @uref{http://www.xemacs.org/Develop/cvsaccess.html}. | |
| 1069 | |
| 1070 Nightly CVS snapshots are available at | |
| 1071 @uref{http://www.dk.xemacs.org/Download/CVS-snapshots/}. | |
| 1072 | |
| 1073 @node Q1.1.4, Q1.2.1, Q1.1.3, Introduction | |
| 1074 @unnumberedsubsec Q1.1.4: Where can I obtain a printed copy of the XEmacs User's Manual? | |
| 1075 | |
| 1076 Pre-printed manuals are not available. If you are familiar with | |
| 1077 TeX, you can generate your own manual from the XEmacs sources. | |
| 1078 | |
| 1079 HTML and Postscript versions of XEmacs manuals are available from the | |
| 1080 XEmacs web site at | |
| 1081 @uref{http://www.xemacs.org/Documentation/index.html}. | |
| 1082 | |
| 1083 @unnumberedsec 1.2: Versions for Different Operating Systems | |
| 1084 | |
| 1085 @node Q1.2.1, Q1.2.2, Q1.1.4, Introduction | |
| 1086 @unnumberedsubsec Q1.2.1: Do I need X11 to run XEmacs? | |
| 1087 | |
| 1088 No. The name @dfn{XEmacs} is unfortunate in the sense that it is | |
| 1089 @strong{not} an X Window System-only version of Emacs. XEmacs has | |
| 1090 full color support on a color-capable character terminal. | |
| 1091 | |
| 1092 @node Q1.2.2, Q1.2.3, Q1.2.1, Introduction | |
| 1093 @unnumberedsubsec Q1.2.2: What versions of Unix does XEmacs run on? | |
| 1094 | |
|
4759
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1095 XEmacs is regularly tested on Linux, Solaris and OpenSolaris, HP/UX, |
|
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1096 FreeBSD, OpenBSD, Cygwin, Mac OS X, and probably others. It should work |
|
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1097 on all versions of Unix created in the last 10 years or so, perhaps with |
|
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1098 a bit of work on more obscure platforms to correct bit-rot. It uses a |
|
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1099 sophisticated configuration system to auto-detect zillions of features |
|
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1100 that are implemented differently in different versions of Unix, so it |
|
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1101 will probably work on your vendor's version, possibly with a bit of |
|
aa5ed11f473b
Remove support for obsolete systems. See xemacs-patches message with ID
Jerry James <james@xemacs.org>
parents:
4658
diff
changeset
|
1102 tweaking, even if we've never heard of it. |
| 2559 | 1103 |
| 2537 | 1104 For problems with particular machines and versions of Unix, see the |
| 1105 @file{PROBLEMS} file. | |
| 1106 | |
| 1107 Much effort has gone into making XEmacs work on as many different | |
| 1108 machines, configurations, and compilers as possible. | |
| 1109 | |
| 1110 Much effort has gone into making XEmacs 64-bit clean. | |
| 1111 | |
| 1112 Much effort has gone into removing system-specific code, and replacing | |
| 1113 such code with autodetection at configure time. | |
| 1114 | |
| 1115 The XEmacs core should build "out of the box" on most Unix-like systems. | |
| 1116 | |
| 1117 XEmacs 21.2 was tested and @samp{make check} succeeded on these Unix | |
| 1118 configurations as of 2001-02-10: | |
| 1119 | |
| 1120 @example | |
| 1121 alphaev56-dec-osf4.0e (both Compaq C and gcc) | |
| 1122 i386-unknown-freebsd4.2 | |
| 1123 i386-unknown-netbsdelf1.5 | |
| 1124 i586-sco-sysv5uw7.0.1 (both SCO's cc and gcc) | |
| 1125 i686-pc-linux-gnu | |
| 1126 hppa2.0-hp-hpux10.20 (both HP's ANSI cc and gcc) | |
| 1127 mips-sgi-irix6.5 (both MIPSpro cc and gcc) | |
| 1128 rs6000-ibm-aix4.3.0.0 (both IBM's xlc and gcc) | |
| 1129 sparc-sun-solaris2.6 (both Sun's Forte C and gcc) | |
| 1130 sparc-sun-solaris2.7 (both Sun's Forte C and gcc) | |
| 1131 sparc-sun-sunos4.1.4 (gcc) | |
| 1132 @end example | |
| 1133 | |
| 3018 | 1134 Some systems have a dual mode 32-bit/64-bit compiler. On most of these, |
| 1135 XEmacs requires the @samp{--pdump} (in XEmacs 21.5, | |
| 1136 @samp{--enable-pdump}) configure option to build correctly with the | |
| 1137 64-bit version of the compiler. | |
| 2537 | 1138 |
| 1139 @example | |
| 1140 mips-sgi-irix6.5, CC="gcc -mabi=64" | |
| 1141 mips-sgi-irix6.5, CC="cc -64" | |
| 1142 rs6000-ibm-aix4.3.0.0, CC="cc -q64" | |
| 1143 @end example | |
| 1144 | |
| 1145 On most of these systems, XEmacs also builds with a C++ compiler, | |
| 1146 but not "out of the box". This feature is only for use by the | |
| 1147 maintainers. | |
| 1148 | |
| 1149 XEmacs 21.2 is known @emph{not} to work on any machines with m680x0 | |
| 1150 processors. Sorry, all you sun3 and Unix PC nostalgia buffs out there. | |
| 1151 | |
| 1152 VMS has never been supported by XEmacs. In fact, all the old VMS code | |
| 1153 inherited from Emacs has been removed. Sorry, all you VMS fans out there. | |
| 1154 | |
| 1155 @node Q1.2.3, Q1.2.4, Q1.2.2, Introduction | |
| 1156 @unnumberedsubsec Q1.2.3: Is there a port of XEmacs to Microsoft Windows? | |
| 1157 | |
| 1158 Yes. Beginning with release 21.0, XEmacs has worked under MS Windows | |
| 1159 and is fully-featured and actively developed. A group of dedicated | |
| 1160 developers actively maintains and improves the Windows-specific | |
| 1161 portions of the code. Some of the core developers, in fact, use | |
| 1162 Windows as their only development environment, and some features, such | |
| 1163 as printing, actually work better on Windows than native Unix and Mac | |
| 1164 OS X. The mailing list at @email{xemacs-winnt@@xemacs.org} is dedicated | |
| 1165 to that effort (please use the -request address to | |
| 1166 subscribe). (Despite its name, XEmacs actually works on all versions | |
| 1167 of Windows.) | |
| 1168 | |
| 1169 The list name is misleading, as XEmacs supports and has been compiled on | |
| 1170 Windows 95, Windows 98, Windows NT, Windows 2000, Windows ME, Windows | |
| 1171 XP, and all newer versions of Windows. The MS Windows-specific code is | |
| 1172 based on Microsoft Win32 API, and will not work on MS Windows 3.x or on | |
| 1173 MS-DOS. | |
| 1174 | |
| 1175 XEmacs also supports the Cygwin and MinGW development and runtime | |
| 1176 environments, where it also uses native Windows code for graphical | |
| 1177 features. In addition, under Cygwin it is possible to compile XEmacs | |
| 1178 to use an X server (and XFree86 is available as part of the standard | |
| 1179 Cygwin installation). | |
| 1180 | |
| 1181 @node Q1.2.4, Q1.2.5, Q1.2.3, Introduction | |
| 1182 @unnumberedsubsec Q1.2.4: Can I build XEmacs on MS Windows with X support? Do I need to? | |
| 1183 | |
| 1184 Yes, you can, but no you do not need to. In fact, we recommend that you | |
| 1185 use a native-GUI version unless you have a specific need for an X | |
| 1186 version. | |
| 1187 | |
| 1188 @node Q1.2.5, Q1.2.6, Q1.2.4, Introduction | |
| 1189 @unnumberedsubsec Q1.2.5: What are Cygwin and MinGW, and do I need them to run XEmacs? | |
| 1190 | |
| 1191 To answer the second part of the question: No, you, you don't need | |
| 1192 Cygwin or MinGW to build or to run XEmacs. But if you have them and | |
| 1193 want to use them, XEmacs supports these environments. | |
| 1194 | |
| 1195 (One important reason to support Cygwin is that it lets the MS Windows | |
| 1196 developers test out their code in a Unix environment without actually | |
| 1197 having to have a Unix machine around. For this reason alone, Cygwin | |
| 1198 support is likely to remain supported for a long time in XEmacs. Same | |
| 1199 goes for the X support under Cygwin, for the same reasons. MinGW | |
| 1200 support, on the other hand, depends on volunteers to keep it up to date; | |
| 1201 but this is generally not hard.) | |
| 1202 | |
| 1203 Cygwin is a set of tools providing Unix-like API on top of Win32. | |
| 1204 It makes it easy to port large Unix programs without significant | |
| 1205 changes to their source code. It is a development environment as well | |
| 1206 as a runtime environment. | |
| 1207 | |
| 1208 When built with Cygwin, XEmacs supports all display types -- TTY, X & | |
| 1209 Win32 GUI, and can be built with support for all three simultaneously. | |
| 1210 If you build with Win32 GUI support then the Cygwin version uses the | |
| 1211 majority of the Windows-specific code, which is mostly related to | |
| 1212 display. If you want to build with X support you need X libraries (and | |
| 2559 | 1213 an X server to display XEmacs on); see @ref{Q2.3.7}. TTY and Win32 GUI |
| 2537 | 1214 require no additional libraries beyond what comes standard with Cygwin. |
| 1215 | |
| 1216 The advantages of the Cygwin version are that it integrates well with | |
| 1217 the Cygwin environment for existing Cygwin users; uses configure so | |
| 1218 building with different features is very easy; and actively supports X & | |
| 1219 TTY. Furthermore, the entire Cygwin environment and compiler are free, | |
| 1220 whereas Visual C++ costs money. | |
| 1221 | |
| 1222 The disadvantage is that it requires the whole Cygwin environment, | |
| 1223 whereas the native port requires only a suitable MS Windows compiler. | |
| 1224 Also, it follows the Unix filesystem and process model very closely | |
| 1225 (some will undoubtedly view this as an advantage). | |
| 1226 | |
| 1227 See @uref{http://www.cygwin.com/} for more information on | |
| 1228 Cygwin. | |
| 1229 | |
| 1230 MinGW is a collection of header files and import libraries that allow | |
| 1231 one to use GCC under the Cygwin environment to compile and produce | |
| 1232 exactly the same native Win32 programs that you can using Visual C++. | |
| 1233 Programs compiled with MinGW make use of the standard Microsoft runtime | |
| 1234 library @file{MSVCRT.DLL}, present on all Windows systems, and look, | |
| 1235 feel, and act like a standard Visual-C-produced application. (The only | |
| 1236 difference is the compiler.) This means that, unlike a | |
| 1237 standardly-compiled Cygwin application, no extra runtime support | |
| 1238 (e.g. Cygwin's @file{cygwin1.dll}) is required. This, along with the | |
| 1239 fact that GCC is free (and works in a nice Unix-y way in a nice Unix-y | |
| 1240 environment, for those die-hard Unix hackers out there), is the main | |
| 1241 advantage of MinGW. It is also potentially faster than Cygwin because | |
| 1242 it has less overhead when calling Windows, but you lose the POSIX | |
| 1243 emulation layer, which makes Unix programs harder to port. (But this is | |
| 1244 irrelevant for XEmacs since it's already ported to Win32.) | |
| 1245 | |
| 1246 See @uref{http://www.mingw.org/} for more information on MinGW. | |
| 1247 | |
| 1248 @node Q1.2.6, Q1.2.7, Q1.2.5, Introduction | |
| 1249 @unnumberedsubsec Q1.2.6: What are the differences between the various MS Windows emacsen? | |
| 1250 | |
| 1251 XEmacs, Win-Emacs, DOS Emacs, NT Emacs, this is all very confusing. | |
| 1252 Could you briefly explain the differences between them? | |
| 1253 | |
| 1254 Here is a recount of various Emacs versions running on MS Windows: | |
| 1255 | |
| 1256 @itemize @bullet | |
| 1257 | |
| 1258 @item | |
| 1259 XEmacs | |
| 1260 | |
| 1261 @itemize @minus | |
| 1262 | |
| 1263 @item | |
| 1264 Beginning with XEmacs 19.12, XEmacs' architecture was redesigned | |
| 1265 in such a way to allow clean support of multiple window systems. At | |
| 1266 this time the TTY support was added, making X and TTY the first two | |
| 1267 "window systems" supported by XEmacs. The 19.12 design is the basis for | |
| 1268 the current native MS Windows code. | |
| 1269 | |
| 1270 @item | |
| 1271 Some time during 1997, David Hobley (soon joined by Marc Paquette) | |
| 1272 imported some of the NT-specific portions of GNU Emacs, making XEmacs | |
| 1273 with X support compile under Windows NT, and creating the "X" port. | |
| 1274 | |
| 1275 @item | |
| 1276 Several months later, Jonathan Harris sent out initial patches to use | |
| 1277 the Win32 API, thus creating the native port. Since then, various | |
| 1278 people have contributed, including Kirill M. Katsnelson (contributed | |
| 1279 support for menubars, subprocesses and network, as well as loads of | |
| 1280 other code), Andy Piper (ported XEmacs to Cygwin environment, | |
| 1281 contributed Windows unexec, Windows-specific glyphs and toolbars code, | |
| 1282 and more), Ben Wing (loads of improvements; primary MS Windows developer | |
| 1283 since 2000), Jeff Sparkes (contributed scrollbars support) and many | |
| 1284 others. | |
| 1285 @end itemize | |
| 1286 | |
| 1287 @item | |
| 1288 NT Emacs | |
| 1289 | |
| 1290 @itemize @minus | |
| 1291 | |
| 1292 @item | |
| 1293 NT Emacs was an early version of GNU Emacs 19 modified to compile and | |
| 1294 run under MS Windows 95 and NT using the native Win32 API. It was | |
| 1295 written by Geoff Voelker, and has long since been incorporated into | |
| 1296 the mainline GNU Emacs distribution. | |
| 1297 @end itemize | |
| 1298 | |
| 1299 @item | |
| 1300 Win-Emacs | |
| 1301 | |
| 1302 @itemize @minus | |
| 1303 | |
| 1304 @item | |
| 1305 Win-Emacs was a port of Lucid Emacs 19.6 to MS Windows using X | |
| 1306 compatibility libraries. Win-Emacs was written by Ben Wing. The MS | |
| 1307 Windows code never made it back to Lucid Emacs, and its creator (Pearl | |
| 1308 Software) has long since gone out of business. | |
| 1309 @end itemize | |
| 1310 | |
| 1311 @item | |
| 1312 GNU Emacs for DOS | |
| 1313 | |
| 1314 @itemize @minus | |
| 1315 | |
| 1316 @item | |
| 1317 GNU Emacs features support for MS-DOS and DJGPP (D.J. Delorie's DOS | |
| 1318 port of GCC). Such an Emacs is heavily underfeatured, because it does | |
| 1319 not support long file names, lacks proper subprocesses support, and | |
| 1320 is far too big compared with typical DOS editors. | |
| 1321 @end itemize | |
| 1322 | |
| 1323 @item | |
| 1324 GNU Emacs compiled with Win32 | |
| 1325 | |
| 1326 @itemize @minus | |
| 1327 | |
| 1328 @item | |
| 1329 Starting with GNU Emacs 19.30, it has been possible to compile GNU Emacs | |
| 1330 under MS Windows using the DJGPP compiler and X libraries. The result | |
| 1331 is very similar to GNU Emacs compiled under MS DOS, only it works | |
| 1332 somewhat better because it runs in 32-bit mode, makes use of all the | |
| 1333 system memory, supports long file names, etc. | |
| 1334 @end itemize | |
| 1335 | |
| 1336 @end itemize | |
| 1337 | |
| 1338 @node Q1.2.7, Q1.2.8, Q1.2.6, Introduction | |
| 1339 @unnumberedsubsec Q1.2.7: How does the port cope with differences in the Windows user interface? | |
| 1340 | |
| 1341 The XEmacs (and Emacs in general) user interface is pretty different | |
| 1342 from what is expected of a typical MS Windows program. How does the MS | |
| 1343 Windows port cope with it? | |
| 1344 | |
| 1345 As a general rule, we follow native MS Windows conventions as much as | |
| 1346 possible. 21.4 is a fairly complete Windows application, supporting | |
| 1347 native printing, system file dialog boxes, tool tips, etc. In cases | |
| 1348 where there's a clear UI conflict, we currently use normal Unix XEmacs | |
| 1349 behavior by default, but make sure the MS Windows "look and feel" (mark | |
| 1350 via shift-arrow, self-inserting deletes region, Alt selects menu items, | |
| 1351 etc.) is easily configurable (respectively: using the variable | |
| 1352 @code{shifted-motion-keys-select-region} in 21.4 and above [it's in fact | |
| 1353 the default in these versions], or the @file{pc-select} package; using | |
| 1354 the @file{pending-del} package; and setting the variable | |
| 1355 @code{menu-accelerator-enabled} to @code{menu-force} in 21.4 and above). | |
| 1356 In fact, if you use the sample @file{init.el} file as your init file, | |
| 1357 you will get all these behaviors automatically turned on. | |
| 1358 | |
| 1359 In future versions, some of these features might be turned on by | |
| 1360 default in the MS Windows environment. | |
| 1361 | |
| 1362 @node Q1.2.8, Q1.2.9, Q1.2.7, Introduction | |
| 1363 @unnumberedsubsec Q1.2.8: Is there a port of XEmacs to the Macintosh? | |
| 1364 | |
| 1365 Yes. | |
| 1366 | |
| 1367 XEmacs 21.5 (perhaps 21.4 also?) works on MacOS X, although it certainly | |
| 1368 will not feel very much like a Mac application as it has no Mac-specific | |
| 1369 code in it. | |
| 1370 | |
| 1371 There is also a port of XEmacs 19.14 that works on all recent versions | |
| 1372 of MacOS, from 8.1 through MacOS X, by @email{pjarvis@@ispchannel.com, | |
| 1373 Pitts Jarvis} (recently deceased). It runs in an equivalent of TTY | |
| 1374 mode only (one single Macintosh window, 25 colors), but has a large | |
| 1375 number of Mac-specific additions. It's available at | |
| 1376 @uref{http://homepage.mac.com/pjarvis/xemacs.html}. | |
| 1377 | |
| 1378 @node Q1.2.9, Q1.2.10, Q1.2.8, Introduction | |
| 2559 | 1379 @unnumberedsubsec Q1.2.9: Is there a port of XEmacs to MS-DOS? |
| 1380 | |
| 1381 No. We have never supported running on MS-DOS or Windows 3.1, and in | |
| 1382 fact have long since deleted all MS-DOS-related code. We're not | |
| 1383 particularly interested in patches for these platforms, as they would | |
| 1384 introduce huge amounts of code clutter due to the woefully | |
| 1385 underfeatured nature of these systems. (See GNU Emacs for a port to | |
| 1386 MS-DOS.) | |
| 2537 | 1387 |
| 1388 @node Q1.2.10, Q1.2.11, Q1.2.9, Introduction | |
| 2559 | 1389 @unnumberedsubsec Q1.2.10: Is there a port of XEmacs to OS/2? |
| 2537 | 1390 |
| 1391 No, but Alexander Nikolaev <avn_1251@@mail.ru> was at one point | |
| 1392 working on it. | |
| 1393 | |
| 2559 | 1394 @node Q1.2.11, Q1.2.12, Q1.2.10, Introduction |
| 1395 @unnumberedsubsec Q1.2.11: Is there a port of XEmacs to NextStep? | |
| 2537 | 1396 |
| 1397 Carl Edman, apparently no longer at @email{cedman@@princeton.edu}, did | |
| 1398 the port of GNU Emacs to NeXTstep and expressed interest in doing the | |
| 1399 XEmacs port, but never went any farther. | |
| 1400 | |
| 2559 | 1401 @node Q1.2.12, Q1.3.1, Q1.2.11, Introduction |
| 1402 @unnumberedsubsec Q1.2.12: Is there a port of XEmacs to VMS? | |
| 2537 | 1403 |
| 1404 VMS has never been supported by XEmacs. In fact, all the old VMS code | |
| 1405 inherited from GNU Emacs has been removed. Sorry, all you VMS fans | |
| 1406 out there. | |
| 1407 | |
| 1408 @unnumberedsec 1.3: Getting Started | |
| 1409 | |
| 2559 | 1410 @node Q1.3.1, Q1.3.2, Q1.2.12, Introduction |
| 2537 | 1411 @unnumberedsubsec Q1.3.1: What is an @file{init.el} or @file{.emacs} and is there a sample one? |
| 1412 | |
| 1413 The @file{init.el} or @file{.emacs} file is used to customize XEmacs to | |
| 1414 your tastes. Starting in 21.4, the preferred location for the init file | |
| 1415 is @file{~/.xemacs/init.el}; in previous versions, it was | |
| 1416 @file{~/.emacs}. 21.4 still accepts the old location, but the first | |
| 1417 time you run it, it will ask to migrate your file to the new location. | |
| 1418 If you answer yes, the file will be moved, and a "compatibility" | |
| 1419 @file{.emacs} file will be placed in the old location so that you can | |
| 1420 still run older versions of XEmacs, and versions of GNU Emacs, which | |
| 1421 expect the old location. The @file{.emacs} file present is just a stub | |
| 1422 that loads the real file in @file{~/.xemacs/init.el}. | |
| 1423 | |
| 1424 No two init files are alike, nor are they expected to be alike, but | |
| 1425 that's the point. The XEmacs distribution contains an excellent starter | |
| 1426 example in the @file{etc/} directory called @file{sample.init.el} | |
| 1427 (starting in 21.4) or @file{sample.emacs} in older versions. Copy this | |
| 1428 file from there to @file{~/.xemacs/init.el} (starting in 21.4) or | |
| 1429 @file{~/.emacs} in older versions, where @samp{~} means your home | |
| 1430 directory, of course. Then edit it to suit. | |
| 1431 | |
| 1432 You may bring the @file{sample.init.el} or @file{sample.emacs} file into | |
| 1433 an XEmacs buffer from the menubar. (The menu entry for it is always | |
| 1434 under the @samp{Help} menu, but its location under that has changed in | |
| 1435 various versions. Recently, look under the @samp{Samples} submenu.) To | |
| 1436 determine the location of the @file{etc/} directory type the command | |
| 1437 @kbd{C-h v data-directory @key{RET}}. | |
| 1438 | |
| 1439 @node Q1.3.2, Q1.3.3, Q1.3.1, Introduction | |
| 1440 @unnumberedsubsec Q1.3.2: Where do I put my @file{init.el} file? | |
| 1441 | |
| 1442 @file{init.el} is the name of the init file starting with 21.4, and is | |
| 1443 located in the subdirectory @file{.xemacs/} of your home directory. In | |
| 1444 prior versions, the init file is called @file{.emacs} and is located in | |
| 1445 your home directory. | |
| 1446 | |
| 1447 Your home directory under Windows is determined by the @samp{HOME} | |
| 1448 environment variable. If this is not set, it defaults to @samp{C:\}. | |
| 1449 To set this variable, modify @file{AUTOEXEC.BAT} under Windows 95/98, or | |
| 1450 select @samp{Control Panel->System->Advanced->Environment Variables...} | |
| 1451 under Windows NT/2000. | |
| 1452 | |
| 1453 @node Q1.3.3, Q1.3.4, Q1.3.2, Introduction | |
| 1454 @unnumberedsubsec Q1.3.3: Can I use the same @file{init.el} with the other Emacs? | |
| 1455 | |
| 1456 Yes. The sample @file{init.el} included in the XEmacs | |
| 1457 distribution will show you how to handle different versions and flavors | |
| 1458 of Emacs. | |
| 1459 | |
| 1460 @node Q1.3.4, Q1.3.5, Q1.3.3, Introduction | |
| 1461 @unnumberedsubsec Q1.3.4: Any good XEmacs tutorials around? | |
| 1462 | |
| 1463 There's the XEmacs tutorial available from the Help Menu under | |
| 1464 @samp{Help->Tutorials}, or by typing @kbd{C-h t}. To check whether | |
| 1465 it's available in a non-english language, type @kbd{C-u C-h t TAB}, type | |
| 1466 the first letters of your preferred language, then type @key{RET}. | |
| 1467 | |
| 1468 @comment There's an Emacs Lisp tutorial at | |
| 1469 @comment | |
| 1470 @comment @example | |
| 1471 @comment @uref{ftp://prep.ai.mit.edu/pub/gnu/emacs-lisp-intro-1.04.tar.gz}. | |
| 1472 @comment @end example | |
| 1473 @comment | |
| 1474 @comment @email{erik@@petaxp.rug.ac.be, Erik Sundermann} has made a tutorial web | |
| 1475 @comment page at | |
| 1476 @comment @iftex | |
| 1477 @comment @* | |
| 1478 @comment @end iftex | |
| 1479 @comment @uref{http://petaxp.rug.ac.be/~erik/xemacs/}. | |
| 1480 | |
| 1481 @node Q1.3.5, Q1.3.6, Q1.3.4, Introduction | |
| 1482 @unnumberedsubsec Q1.3.5: May I see an example of a useful XEmacs Lisp function? | |
| 1483 | |
| 1484 The following function does a little bit of everything useful. It does | |
| 1485 something with the prefix argument, it examines the text around the | |
| 1486 cursor, and it's interactive so it may be bound to a key. It inserts | |
| 1487 copies of the current word the cursor is sitting on at the cursor. If | |
| 1488 you give it a prefix argument: @kbd{C-u 3 M-x double-word} then it will | |
| 1489 insert 3 copies. | |
| 1490 | |
| 1491 @lisp | |
| 1492 (defun double-word (count) | |
| 1493 "Insert a copy of the current word underneath the cursor" | |
| 1494 (interactive "*p") | |
| 1495 (let (here there string) | |
| 1496 (save-excursion | |
| 1497 (forward-word -1) | |
| 1498 (setq here (point)) | |
| 1499 (forward-word 1) | |
| 1500 (setq there (point)) | |
| 1501 (setq string (buffer-substring here there))) | |
| 1502 (while (>= count 1) | |
| 1503 (insert string) | |
| 1504 (decf count)))) | |
| 1505 @end lisp | |
| 1506 | |
| 1507 The best way to see what is going on here is to let XEmacs tell you. | |
| 1508 Put the code into an XEmacs buffer, and do a @kbd{C-h f} with the cursor | |
| 1509 sitting just to the right of the function you want explained. Eg. move | |
| 1510 the cursor to the SPACE between @code{interactive} and @samp{"*p"} and | |
| 1511 hit @kbd{C-h f} to see what the function @code{interactive} does. Doing | |
| 1512 this will tell you that the @code{*} requires a writable buffer, and | |
| 1513 @code{p} converts the prefix argument to a number, and | |
| 1514 @code{interactive} allows you to execute the command with @kbd{M-x}. | |
| 1515 | |
| 1516 @node Q1.3.6, Q1.3.7, Q1.3.5, Introduction | |
| 1517 @unnumberedsubsec Q1.3.6: And how do I bind it to a key? | |
| 1518 | |
| 1519 To bind to a key do: | |
| 1520 | |
| 1521 @lisp | |
| 1522 (global-set-key "\C-cd" 'double-word) | |
| 1523 @end lisp | |
| 1524 | |
| 1525 Or interactively, @kbd{M-x global-set-key} and follow the prompts. | |
| 1526 | |
| 1527 @node Q1.3.7, Q1.3.8, Q1.3.6, Introduction | |
| 1528 @unnumberedsubsec Q1.3.7: What's the difference between a macro and a function? | |
| 1529 | |
| 1530 Quoting from the Lisp Reference (a.k.a @dfn{Lispref}) Manual: | |
| 1531 | |
| 1532 @dfn{Macros} enable you to define new control constructs and other | |
| 1533 language features. A macro is defined much like a function, but instead | |
| 1534 of telling how to compute a value, it tells how to compute another Lisp | |
| 1535 expression which will in turn compute the value. We call this | |
| 1536 expression the @dfn{expansion} of the macro. | |
| 1537 | |
| 1538 Macros can do this because they operate on the unevaluated expressions | |
| 1539 for the arguments, not on the argument values as functions do. They can | |
| 1540 therefore construct an expansion containing these argument expressions | |
| 1541 or parts of them. | |
| 1542 | |
| 1543 Do not confuse the two terms with @dfn{keyboard macros}, which are | |
| 1544 another matter, entirely. A keyboard macro is a key bound to several | |
| 1545 other keys. Refer to manual for details. | |
| 1546 | |
| 1547 @node Q1.3.8, Q1.4.1, Q1.3.7, Introduction | |
| 1548 @unnumberedsubsec Q1.3.8: What is @code{Custom}? | |
| 1549 | |
| 1550 @code{Custom} is a system for customizing XEmacs options. | |
| 1551 | |
| 1552 You can access @code{Advanced (Customize)} from the @code{Options} menu | |
| 1553 or invoking one of customize commands by typing eg. | |
| 1554 @kbd{M-x customize}, @kbd{M-x customize-face}, | |
| 1555 @kbd{M-x customize-variable} or @kbd{M-x customize-apropos}. | |
| 1556 | |
| 1557 There is also new @samp{browser} mode for Customize. | |
| 1558 Try it out with @kbd{M-x customize-browse} | |
| 1559 | |
| 1560 @unnumberedsec 1.4: Getting Help | |
| 1561 | |
| 1562 @node Q1.4.1, Q1.4.2, Q1.3.8, Introduction | |
| 1563 @unnumberedsubsec Q1.4.1: Where can I get help? | |
| 1564 | |
| 1565 Probably the easiest way, if everything is installed, is to use Info, by | |
| 1566 pressing @kbd{C-h i}, or looking for an Info item on the | |
| 1567 Help Menu. @kbd{M-x apropos} can be used to look for particular commands. | |
| 1568 | |
| 1569 For items not found in the manual, try reading this FAQ | |
| 1570 and reading the Usenet group comp.emacs.xemacs. | |
| 1571 | |
| 1572 If you choose to post to a newsgroup, @strong{please use | |
| 1573 comp.emacs.xemacs}. Please do not post XEmacs related questions to | |
| 1574 gnu.emacs.help. | |
| 1575 | |
| 1576 If you cannot post or read Usenet news, there is a corresponding mailing | |
| 1577 list @email{xemacs-news@@xemacs.org} which is available. It can be | |
| 1578 subscribed to via the Mailman Web interface or by sending mail to to | |
| 1579 @email{xemacs-news-request@@xemacs.org} with @samp{subscribe} in the | |
| 1580 body of the message. See also | |
| 1581 @uref{http://www.xemacs.org/Lists/#xemacs-news}. To cancel a | |
| 1582 subscription, you may use the @email{xemacs-news-request@@xemacs.org} | |
| 1583 address or the Web interface. Send a message with a subject of | |
| 1584 @samp{unsubscribe} to be removed. | |
| 1585 | |
| 1586 @node Q1.4.2, Q1.4.3, Q1.4.1, Introduction | |
| 1587 @unnumberedsubsec Q1.4.2: Which mailing lists are there? | |
| 1588 | |
| 1589 For complete, up-to-date info on the lists and how to subscribe, see | |
| 1590 @uref{http://www.xemacs.org/Lists/}. | |
| 1591 | |
| 1592 @table @samp | |
| 1593 | |
| 1594 @item comp.emacs.xemacs | |
| 1595 is a Usenet newsgroup | |
| 1596 for XEmacs users to discuss problems and issues that arise | |
| 1597 for them. It's not generally an appropriate place to ask | |
| 1598 about apparent bugs (use @samp{xemacs-beta}), or future plans | |
| 1599 (use @samp{xemacs-design}). | |
| 1600 | |
| 1601 @item xemacs-announce | |
| 1602 is a read-only, low | |
| 1603 volume list for announcements concerning the XEmacs project | |
| 1604 and new releases of the XEmacs software. | |
| 1605 | |
| 1606 @item xemacs-beta | |
| 2559 | 1607 is an open list for bug reports about beta versions of XEmacs. This |
| 1608 includes the bug reports themselves, by both users and developers, as | |
| 1609 well as queries, follow-ups, and discussions further determining their | |
| 1610 nature and status. This is the primary channel for this kind of | |
| 1611 discussion; related code changes will usually not be applied until | |
| 1612 they have been discussed here. When such discussions touch on | |
| 1613 significant changes to the code (in particular, structural changes), | |
| 1614 or on changes to API's or external functionality, they should be moved | |
| 1615 to @samp{xemacs-design}. Requests and proposals for non-bug-related | |
| 1616 changes do not belong on @samp{xemacs-beta}, and should be sent to | |
| 1617 @samp{xemacs-design} instead. | |
| 2537 | 1618 |
| 1619 @item xemacs-beta-ja | |
| 1620 is an open list for bug | |
| 1621 reports and design discussion related to Mule features, | |
| 1622 including Japanese handling, in beta versions of XEmacs. | |
| 1623 Japanese is the preferred language of discussion. For most | |
| 1624 timely presentation to reviewers, please consider sending | |
| 1625 appropriate discussion to @samp{xemacs-mule} or | |
| 1626 @samp{xemacs-design} in English when convenient for | |
| 1627 the participants in discussion. When possible, bug reports | |
| 1628 not related to Mule (including Japanese) should be reported on | |
| 1629 @samp{xemacs-beta} in English. | |
| 1630 | |
| 1631 @item xemacs-buildreports | |
| 1632 is an open list for | |
| 1633 submission of build-reports on beta versions of XEmacs. For | |
| 1634 information on what the build-reports should contain, please | |
| 1635 see the `etc/BETA' file which is included in each beta | |
| 1636 distribution. | |
| 1637 | |
| 1638 @item xemacs-cvs | |
| 1639 is a read-only list for notices | |
| 1640 and information on what has been committed to the XEmacs CVS | |
| 1641 trees, by whom, and for what. | |
| 1642 | |
| 1643 @item xemacs-design | |
| 1644 is an open list for | |
| 1645 discussing the design of XEmacs. This includes discussion | |
| 1646 about planned and ongoing changes to functionality and API | |
| 1647 changes and additions as well as requests for them. This is | |
| 1648 the primary channel for this kind of discussion; related code | |
| 1649 changes will usually not be applied until they have been | |
| 1650 discussed here. This does not include bug reports, which go | |
| 1651 to @samp{xemacs-beta}. | |
| 1652 | |
| 1653 @item xemacs-mule | |
| 1654 is an open mailing list for | |
| 1655 discussion of International extensions to XEmacs including | |
| 1656 Mule, XIM, I18n issues, etc, and is not confined to | |
| 1657 developmental issues. This list is not restricted to | |
| 1658 English, postings in all languages are welcome. | |
| 1659 | |
| 1660 @item xemacs-news | |
| 1661 is an open list for discussion | |
| 1662 and bug reporting for XEmacs. This mailing list is | |
| 1663 bi-directionally gatewayed with the USENET newsgroup | |
| 1664 comp.emacs.xemacs. | |
| 1665 | |
| 1666 @item xemacs-nt | |
| 1667 is a developers-only mailing | |
| 1668 list and is intended for people who wish to work actively on | |
| 1669 the porting of XEmacs to Microsoft Windows NT and Microsoft | |
| 1670 Windows '95. | |
| 1671 | |
| 1672 @item xemacs-patches | |
| 1673 is an open, moderated | |
| 1674 list for submission of patches to the XEmacs distribution | |
| 1675 and its packages. Anyone may subscribe or submit to | |
| 1676 xemacs-patches, but all submissions are reviewed by the list | |
| 1677 moderator before they are distributed to the | |
| 1678 list. Discussion is not appropriate on xemacs-patches. | |
| 1679 | |
| 1680 @item xemacs-users-ja | |
| 1681 is an open list for | |
| 1682 discussion and bug reporting for XEmacs. Japanese is the | |
| 1683 preferred language of discussion. It is not gated to | |
| 1684 comp.emacs.xemacs or the @samp{xemacs} list. For | |
| 1685 fastest response, bugs not specifically related to Japanese | |
| 1686 or Mule features should be reported on | |
| 1687 @samp{xemacs-beta} (in English). | |
| 1688 | |
| 1689 @item xemacs-users-ru | |
| 1690 is an open list for | |
| 1691 discussion and bug reporting for XEmacs. Russian is the | |
| 1692 preferred language of discussion. It is not gated to | |
| 1693 comp.emacs.xemacs or the @samp{xemacs} list. For | |
| 1694 fastest response, bugs not specifically related to Russian | |
| 1695 or Mule features should be reported on | |
| 1696 @samp{xemacs-beta} (in English). | |
| 1697 @end table | |
| 1698 | |
| 1699 @node Q1.4.3, Q1.4.4, Q1.4.2, Introduction | |
| 1700 @unnumberedsubsec Q1.4.3: Where are the mailing lists archived? | |
| 1701 | |
| 1702 The archives can be found at @uref{http://list-archive.xemacs.org} | |
| 1703 | |
| 1704 @node Q1.4.4, Q1.4.5, Q1.4.3, Introduction | |
| 1705 @unnumberedsubsec Q1.4.4: How can I get two instances of info? | |
| 1706 | |
| 1707 Before 21.4, you can't. The @code{info} package does not provide for | |
| 1708 multiple info buffers. In 21.4, this should be fixed. #### how? | |
| 1709 | |
| 1710 @node Q1.4.5, Q1.5.1, Q1.4.4, Introduction | |
| 1711 @unnumberedsubsec Q1.4.5: How do I add new Info directories? | |
| 1712 | |
| 1713 You use something like: | |
| 1714 | |
| 1715 @lisp | |
| 1716 (setq Info-directory-list (cons | |
| 1717 (expand-file-name "~/info") | |
| 1718 Info-default-directory-list)) | |
| 1719 @end lisp | |
| 1720 | |
| 1721 @email{davidm@@prism.kla.com, David Masterson} writes: | |
| 1722 | |
| 1723 @quotation | |
| 1724 Emacs Info and XEmacs Info do many things differently. If you're trying to | |
| 1725 support a number of versions of Emacs, here are some notes to remember: | |
| 1726 | |
| 1727 @enumerate | |
| 1728 @item | |
| 1729 Emacs Info scans @code{Info-directory-list} from right-to-left while | |
| 1730 XEmacs Info reads it from left-to-right, so append to the @emph{correct} | |
| 1731 end of the list. | |
| 1732 | |
| 1733 @item | |
| 1734 Use @code{Info-default-directory-list} to initialize | |
| 1735 @code{Info-directory-list} @emph{if} it is available at startup, but not | |
| 1736 all Emacsen define it. | |
| 1737 | |
| 1738 @item | |
| 1739 Emacs Info looks for a standard @file{dir} file in each of the | |
| 1740 directories scanned from #1 and magically concatenates them together. | |
| 1741 | |
| 1742 @item | |
| 1743 XEmacs Info looks for a @file{localdir} file (which consists of just the | |
| 1744 menu entries from a @file{dir} file) in each of the directories scanned | |
| 1745 from #1 (except the first), does a simple concatenation of them, and | |
| 1746 magically attaches the resulting list to the end of the menu in the | |
| 1747 @file{dir} file in the first directory. | |
| 1748 @end enumerate | |
| 1749 | |
| 1750 Another alternative is to convert the documentation to HTML with | |
| 1751 texi2html and read it from a web browser like Lynx or W3. | |
| 1752 @end quotation | |
| 1753 | |
| 1754 @unnumberedsec 1.5: Contributing to XEmacs | |
| 1755 | |
| 1756 @node Q1.5.1, Q1.5.2, Q1.4.5, Introduction | |
| 1757 @unnumberedsubsec Q1.5.1: How do I submit changes to the FAQ? | |
| 1758 | |
| 1759 The FAQ is actively maintained and modified regularly. All links should | |
| 1760 be up to date. Unfortunately, some of the information is out of date -- | |
| 1761 a situation which the FAQ maintainer is working on. All submissions are | |
| 1762 welcome, please e-mail submissions to @email{faq@@xemacs.org, XEmacs FAQ | |
| 1763 maintainers}. | |
| 1764 | |
| 1765 Please make sure that @samp{XEmacs FAQ} appears on the Subject: line. | |
| 1766 If you think you have a better way of answering a question, or think a | |
| 1767 question should be included, we'd like to hear about it. Questions and | |
| 1768 answers included into the FAQ will be edited for spelling and grammar | |
| 1769 and will be attributed. Answers appearing without attribution are | |
| 1770 either from versions of the FAQ dated before May 1996 or are from | |
| 1771 previous FAQ maintainers. Answers quoted from Usenet news articles will | |
| 1772 always be attributed, regardless of the author. | |
| 1773 | |
| 1774 @node Q1.5.2, Q1.5.3, Q1.5.1, Introduction | |
| 1775 @unnumberedsubsec Q1.5.2: How do I become a beta tester? | |
| 1776 | |
| 1777 Send an email message to @email{xemacs-beta-request@@xemacs.org} with | |
| 1778 the line @samp{subscribe} in the body of the message. | |
| 1779 | |
| 1780 Be prepared to get your hands dirty, as beta testers are expected to | |
| 1781 identify problems as best they can. | |
| 1782 | |
| 2559 | 1783 @node Q1.5.3, Q1.5.4, Q1.5.2, Introduction |
| 2537 | 1784 @unnumberedsubsec Q1.5.3: How do I contribute to XEmacs itself? |
| 1785 | |
| 1786 It depends on the knowledge and time you possess. If you are able, by | |
| 1787 all means become a beta tester (@pxref{Q1.5.2}). If you are a | |
| 1788 programmer, try to build XEmacs and see if you can improve it. | |
| 1789 | |
| 1790 Otherwise, you can still help by using XEmacs as your everyday editor | |
| 1791 (for pre-built binary versions, @pxref{Q1.1.2}) and reporting bugs you | |
| 1792 find to the mailing list. | |
| 1793 | |
| 1794 Another area where we need help is the documentation: We need good | |
| 1795 documentation for building XEmacs and for using it. This FAQ is a | |
| 1796 small step in that direction. | |
| 1797 | |
| 1798 Ben Wing @email{ben@@xemacs.org} writes: | |
| 1799 | |
| 1800 @quotation | |
| 1801 BTW if you have a wish list of things that you want added, you have to | |
| 1802 speak up about it! More specifically, you can do the following if you | |
| 1803 want a feature added (in increasing order of usefulness): | |
| 1804 | |
| 1805 @itemize @bullet | |
| 1806 @item | |
| 1807 Make a posting about a feature you want added. | |
| 1808 | |
| 1809 @item | |
| 1810 Become a beta tester and make more postings about those same features. | |
| 1811 | |
| 1812 @item | |
| 1813 Convince us that you're going to use the features in some cool and | |
| 1814 useful way. | |
| 1815 | |
| 1816 @item | |
| 1817 Come up with a clear and well-thought-out API concerning the features. | |
| 1818 | |
| 1819 @item | |
| 1820 Write the code to implement a feature and send us a patch. | |
| 1821 @end itemize | |
| 1822 | |
| 1823 (not that we're necessarily requiring you to write the code, but we can | |
| 1824 always hope :) | |
| 1825 @end quotation | |
| 1826 | |
| 2559 | 1827 @node Q1.5.4, Q1.5.5, Q1.5.3, Introduction |
| 1828 @unnumberedsubsec Q1.5.4: How do I get started developing XEmacs? | |
| 1829 | |
| 1830 First, get yourself set up under CVS so that you can access the CVS | |
| 1831 repositories containing the XEmacs sources and the XEmacs packages. | |
| 1832 | |
| 1833 Next, set up your layout. This is important, as a good layout will | |
| 1834 facilitate getting things done efficiently, while a bad layout will could | |
| 1835 lead to disaster, as you can't figure out which code is the most recent, | |
| 1836 which can be thrown away, etc. We suggest the following layout: (feel free | |
| 1837 to make changes) | |
| 1838 | |
| 1839 @itemize @bullet | |
| 1840 @item | |
| 1841 Everything goes under @file{/src/xemacs} (use a different directory if | |
| 1842 you want). From now, instead of saying @file{/src/xemacs}, we use | |
| 1843 @file{<xsrc-top>}, to make it easier in case someone picked a | |
| 1844 different directory. | |
| 1845 | |
| 1846 @item | |
| 1847 Package source is in @file{<xsrc-top>/package-src}. | |
| 1848 | |
| 1849 @item | |
| 1850 Installed packages go under @file{<xsrc-top>/xemacs-packages}, and | |
| 1851 @file{<xsrc-top>/mule-packages}. | |
| 1852 | |
| 1853 @item | |
| 1854 A "workspace" is a complete copy of the sources, in which you do work of | |
| 1855 a particular kind. Workspaces can be differentiated by which branch of | |
| 1856 the source tree they extend off of -- usually either the stable or | |
| 1857 experimental, unless other branches have been created (for example, Ben | |
| 1858 created a branch for his Mule work because (1) the project was long-term | |
| 1859 and involved an enormous number of changes, (2) people wanted to be able | |
| 1860 to look at what his work in progress, and (3) he wanted to be able to | |
| 1861 check things in and in general use source-code control, since it was a | |
| 1862 long-term project). Workspaces are also differentiated in what their | |
| 1863 purpose is -- general working workspace, workspace for particular | |
| 1864 projects, workspace keeping the latest copy of the code in one of the | |
| 1865 branches without mods, etc. | |
| 1866 | |
| 1867 @item | |
| 1868 Various workspaces are subdirectories under @file{<xsrc-top>}, e.g.: | |
| 1869 | |
| 1870 @itemize @bullet | |
| 1871 @item | |
| 1872 @file{<xsrc-top>/working} (the workspace you're actively working on, | |
| 1873 periodically synched up with the latest trunk) | |
| 1874 | |
| 1875 @item | |
| 1876 @file{<xsrc-top>/stable} (for making changes to the stable version of | |
| 1877 XEmacs, which sits on a branch) | |
| 1878 | |
| 1879 @item | |
| 1880 @file{<xsrc-top>/unsigned-removal} (a workspace for a specific, difficult | |
| 1881 task that's going to affect lots of source and take a long time, and | |
| 1882 so best done in its own workspace without the interference of other | |
| 1883 work you're doing. Also, you can commit just this one large change, | |
| 1884 separate from all the other changes). | |
| 1885 | |
| 1886 @item | |
| 1887 @file{<xsrc-top>/latest} (a copy of the latest sources on the trunk, | |
| 1888 i.e. the experimental version of XEmacs, with no patches in it; | |
| 1889 either update it periodically, by hand, or set up a cron job to do it | |
| 1890 automatically). Set it up so it can be built, and build it so you | |
| 1891 have a working XEmacs. (Building it might also go into the cron job.) | |
| 1892 | |
| 1893 This workspace serves a number of purposes: | |
| 1894 @enumerate | |
| 1895 @item | |
| 1896 You always have a recent version of XEmacs you can compare | |
| 1897 against when something you're working on breaks. It's true | |
| 1898 that you can do this with cvs diff, but when you need to do | |
| 1899 some serious investigation, this method just fails. | |
| 1900 @item | |
| 1901 You (almost) always have a working, up-to-date executable that | |
| 1902 can be used when your executable is crashing and you need to | |
| 1903 keep developing it, or when you need an `xemacs' to build | |
| 1904 packages, etc. | |
| 1905 @item | |
| 1906 When creating new workspaces, you can just copy the `latest' | |
| 1907 workspace using GNU @code{cp -a}. You have all the .elc's built, | |
| 1908 everything else probably configured, any spare files in place | |
| 1909 (e.g. some annoying xpm.dll under Windows, etc.). | |
| 1910 @end enumerate | |
| 1911 | |
| 1912 @item | |
| 1913 @file{<xsrc-top>/latest-stable/} (equivalent to @file{<xsrc-top>/latest/}, but | |
| 1914 for the Stable branch of XEmacs, rather than the Experimental branch | |
| 1915 of XEmacs). This may or may not be necessary depending on how much | |
| 1916 development you do of the stable branch. | |
| 1917 @end itemize | |
| 1918 | |
| 1919 @item | |
| 1920 @file{<xsrc-top>/xemacsweb} is a workspace for working on the XEmacs | |
| 1921 web site. | |
| 1922 | |
| 1923 @item | |
| 1924 @file{<xsrc-top>/in-patches} for patches received from email and saved | |
| 1925 to files. | |
| 1926 | |
| 1927 @item | |
| 1928 @file{<xsrc-top>/out-patches} for locally-generated patches to be sent | |
| 1929 to @email{xemacs-patches@@xemacs.org}. Less useful now that the | |
| 1930 patcher util has been developed. | |
| 1931 | |
| 1932 @item | |
| 1933 @file{<xsrc-top>/build}, for build trees when compiling and testing XEmacs with | |
| 1934 various configuration options turned off and on. The scripts in | |
| 1935 xemacs-builds/ben (see below) can be used to automate building XEmacs | |
| 1936 workspaces with many different configuration options and automatically | |
| 1937 filtering out the normal output so that you see only the abnormal | |
| 1938 output. | |
| 1939 | |
| 1940 @item | |
| 1941 @file{<xsrc-top>/xemacs-builds}, for the xemacs-builds module, which you need | |
| 1942 to check out separately in CVS. This contains scripts used for building | |
| 1943 XEmacs, automating and simplifying using CVS, etc. Under various | |
| 1944 people's directories are their own build and other scripts. The | |
| 1945 currently most-maintained scripts are under ben/, where there are easily | |
| 1946 configurable scripts that can be used to easily build any workspace | |
| 1947 (esp. if you've more or less followed the layout presented above) | |
| 1948 unattended, with one or more configuration states (there's a | |
| 1949 pre-determined list of the most useful, but it's easy to change). The | |
| 1950 output is filtered and split up in various ways so that you can identify | |
| 1951 which output came from where, and you can see the output either full or | |
| 1952 with all "normal" output except occasional status messages filtered so | |
| 1953 that you only see the abnormal ones. | |
| 1954 @end itemize | |
| 1955 | |
| 1956 @node Q1.5.5, Q1.6.1, Q1.5.4, Introduction | |
| 1957 @unnumberedsubsec Q1.5.5: What's the basic layout of the code? | |
| 1958 | |
| 1959 The file @file{configure} is a shell script to acclimate XEmacs to the | |
| 1960 oddities of your processor and operating system. It will create a | |
| 1961 file named @file{Makefile} (a script for the @file{make} program), which helps | |
| 1962 automate the process of building and installing emacs. See INSTALL | |
| 1963 for more detailed information. | |
| 1964 | |
| 1965 The file @file{configure.in} is the input used by the autoconf program to | |
| 1966 construct the @file{configure} script. Since XEmacs has configuration | |
| 1967 requirements that autoconf can't meet, @file{configure.in} uses an unholy | |
| 1968 marriage of custom-baked configuration code and autoconf macros; it | |
| 1969 may be wise to avoid rebuilding @file{configure} from @file{configure.in} when | |
| 1970 possible. | |
| 1971 | |
| 1972 The file @file{Makefile.in} is a template used by @file{configure} to create | |
| 1973 @file{Makefile}. | |
| 1974 | |
| 1975 There are several subdirectories: | |
| 1976 | |
| 1977 @enumerate | |
| 1978 @item | |
| 1979 @file{src} holds the C code for XEmacs (the XEmacs Lisp interpreter and its | |
| 1980 primitives, the redisplay code, and some basic editing functions). | |
| 1981 @item | |
| 1982 @file{lisp} holds the XEmacs Lisp code for XEmacs (most everything else). | |
| 1983 @item | |
| 1984 @file{lib-src} holds the source code for some utility programs for use by | |
| 1985 or with XEmacs, like movemail and etags. | |
| 1986 @item | |
| 1987 @file{etc} holds miscellaneous architecture-independent data files | |
| 1988 XEmacs uses, like the tutorial text. The contents of the @file{lisp}, | |
| 1989 @file{info} and @file{man} subdirectories are architecture-independent too. | |
| 1990 @item | |
| 1991 @file{lwlib} holds the C code for the X toolkit objects used by XEmacs. | |
| 1992 @item | |
| 1993 @file{info} holds the Info documentation tree for XEmacs. | |
| 1994 @item | |
| 1995 @file{man} holds the source code for the XEmacs online documentation. | |
| 1996 @item | |
| 1997 @file{nt} holds files used compiling XEmacs under Microsoft Windows. | |
| 1998 @end enumerate | |
| 1999 | |
| 2537 | 2000 @unnumberedsec 1.6: Politics (XEmacs vs. GNU Emacs) |
| 2001 | |
| 2559 | 2002 @node Q1.6.1, Q1.6.2, Q1.5.5, Introduction |
| 2537 | 2003 @unnumberedsubsec Q1.6.1: What is GNU Emacs? |
| 2004 | |
| 2005 GNU Emacs and XEmacs are related open-source text editors. Both | |
| 2006 derive from GNU Emacs version 18; the split between the two happened | |
| 2007 in 1991 (for comparison, the oldest versions of GNU Emacs date from | |
| 2008 1984). For information on GNU Emacs, see | |
| 2009 @uref{http://www.gnu.org/software/emacs/emacs.html}. | |
| 2010 | |
| 2011 @node Q1.6.2, Q1.6.3, Q1.6.1, Introduction | |
| 2012 @unnumberedsubsec Q1.6.2: How does XEmacs differ from GNU Emacs? | |
| 428 | 2013 |
| 2014 For a detailed description of the differences between GNU Emacs and | |
| 2015 XEmacs and a detailed history of XEmacs, check out the | |
| 2016 @example | |
| 430 | 2017 @uref{http://www.xemacs.org/About/XEmacsVsGNUemacs.html, NEWS file} |
| 428 | 2018 @end example |
| 2019 | |
| 2417 | 2020 @table @strong |
| 2021 @item User-Visible Editing Features | |
| 2022 XEmacs in general tries hard to conform to exist user-interface | |
| 2023 standards, and to work "out-of-the-box" without the need for obscure | |
| 2024 customization changes. GNU Emacs, particularly version 21, has gotten | |
| 2025 better about this (in many cases by copying the XEmacs behavior!), but | |
| 2026 still has some weirdnesses. For example, the standard method of | |
| 2027 selecting text using the Shift key works out-of-the-box in XEmacs. | |
| 2028 | |
| 2029 XEmacs has a built-in toolbar. Four toolbars can actually be configured | |
| 2030 simultaneously: top, bottom, left, and right toolbars. | |
| 2031 | |
| 2032 XEmacs has vertical and horizontal scrollbars. Unlike in GNU Emacs 19 | |
| 2033 (which provides a primitive form of vertical scrollbar), these are true | |
| 2034 toolkit scrollbars. A look-alike Motif scrollbar is provided for those | |
| 2035 who don't have Motif. (Even for those who do, the look-alike may be | |
| 2036 preferable as it is faster.) | |
| 2037 | |
| 2038 XEmacs has buffer tabs along the top of the frame (although the | |
| 2039 position can be changed) that make it very easy to switch buffers. | |
| 2040 | |
| 2041 The menubar under XEmacs is better-designed, with more thought put into | |
| 2042 it. | |
| 2043 | |
| 2044 XEmacs can ask questions using popup dialog boxes. Any command executed | |
| 2045 from a menu will ask yes/no questions with dialog boxes, while commands | |
| 2046 executed via the keyboard will use the minibuffer. | |
| 2047 | |
| 2048 XEmacs under MS Windows provides uses the standard file-dialog box for | |
| 2049 opening and saving files. Standard menu-accelerator behavior can easily | |
| 2050 be enabled using the Options menu, and integrates well into the existing | |
| 2051 keymap. | |
| 2052 | |
| 2053 XEmacs has (still experimental) support for widgets of various sorts -- | |
| 2054 buttons, text boxes, sliders, progress bars, etc. A progress bar is | |
| 2055 used in font lock to show the progress. | |
| 2056 | |
| 2057 Experimental support for drag-and-drop protocols is provided from | |
| 2058 XEmacs 21. | |
| 2059 | |
| 2060 @item General Platform Support | |
| 2061 If you're running on a machine with audio hardware, you can specify | |
| 2062 sound files for XEmacs to play instead of the default X beep. See the | |
| 2063 documentation of the function load-sound-file and the variable | |
| 2064 sound-alist. XEmacs also supports the network sound protocols NAS and | |
| 2065 EsounD. | |
| 2066 | |
| 2067 XEmacs 21 supports database protocols with LISP bindings, currently | |
| 2068 including Berkeley DB, LDAP, and PostgreSQL (21.2 only). | |
| 2069 | |
| 2070 XEmacs 20 and 21 support the Canna, Wnn, and SJ3 Japanese input method | |
| 2071 servers directly, as well as through the X Input Method (XIM) | |
| 2072 protocol. GNU Emacs 20 supports only the XIM protocol. Both Emacsen | |
| 2073 support the Quail family of input methods (implemented in LISP) for many | |
| 2074 languages. | |
| 2075 | |
| 2076 XEmacs provides support for ToolTalk on systems that have | |
| 2077 it. | |
| 2078 | |
| 2079 @item Packaged LISP Libraries | |
| 2080 Many more packages are provided standard with XEmacs than with GNU Emacs | |
| 2081 19 or 20. | |
| 2082 | |
| 2083 XEmacs 21 supports an integrated package management system which uses | |
| 2084 EFS to download, then automatically install prebuilt LISP | |
| 2085 libraries. This allows XEmacs users much more straightforward access to | |
| 2086 the "latest and greatest" version of any given library. | |
| 2087 | |
| 2088 We are working on a standard method for enabling, disabling and | |
| 2089 otherwise controlling packages, which should make them very easy to use. | |
| 2090 | |
| 2091 @item LISP Programming | |
| 2092 From XEmacs 20 on, characters are a separate type. Characters can be | |
| 2093 converted to integers (and many integers can be converted to | |
| 2094 characters), but characters are not integers. GNU Emacs 19, XEmacs 19, | |
| 2095 Mule 2.3 (an extensive patch to GNU Emacs 18.55 and 19.x), and GNU Emacs | |
| 2096 20 (incorporating Mule 3 and later Mule 4) represent them as integers. | |
| 2097 | |
| 2098 From XEmacs 20 on, the buffer is treated as an array of characters, and | |
| 2099 the representation of buffer text is not exposed to LISP. The GNU Emacs | |
| 2100 20 functions like buffer-as-multibyte are not supported. | |
| 2101 | |
| 2102 In XEmacs, events are first-class objects. GNU Emacs 19 represents them | |
| 2103 as integers, which obscures the differences between a key gesture and | |
| 2104 the ancient ASCII code used to represent a particular overlapping subset | |
| 2105 of them. | |
| 2106 | |
| 2107 In XEmacs, keymaps are first-class opaque objects. GNU Emacs 19 | |
| 2108 represents them as complicated combinations of association lists and | |
| 2109 vectors. If you use the advertised functional interface to manipulation | |
| 2110 of keymaps, the same code will work in XEmacs, GNU Emacs 18, and GNU | |
| 2111 Emacs 19; if your code depends on the underlying implementation of | |
| 2112 keymaps, it will not. | |
| 2113 | |
| 2114 XEmacs uses "extents" to represent all non-textual aspects of buffers; | |
| 2115 GNU Emacs 19 uses two distinct objects, "text properties" and | |
| 2116 "overlays", which divide up the functionality between them. Extents are | |
| 2117 a superset of the union of the functionality of the two GNU Emacs data | |
| 2118 types. The full GNU Emacs 19 interface to text properties and overlays | |
| 2119 is supported in XEmacs (with extents being the underlying | |
| 2120 representation). | |
| 2121 | |
| 2122 Extents can be made to be copied into strings, and then restored, by | |
| 2123 kill and yank. Thus, one can specify this behavior on either "extents" | |
| 2124 or "text properties", whereas in GNU Emacs 19 text properties always | |
| 2125 have this behavior and overlays never do. | |
| 2126 | |
| 2127 @item Window System Programming Interface | |
| 2128 XEmacs uses the MIT "Xt" toolkit instead of raw Xlib calls, which makes | |
| 2129 it be a more well-behaved X citizen (and also improves portability). A | |
| 2130 result of this is that it is possible to include other Xt "Widgets" in | |
| 2131 the XEmacs window. Also, XEmacs understands the standard Xt command-line | |
| 2132 arguments. | |
| 2133 | |
| 2134 XEmacs supports Motif applications, generic Xt (e.g. Athena) | |
| 2135 applications, and raw Xlib applications. An XEmacs variant which | |
| 2136 supports GTK+ is available (integration as an option in the XEmacs | |
| 2137 mainline is planned for XEmacs 22), although code to take advantage of | |
| 2138 the support is as yet scarce. | |
| 2139 | |
| 2140 An XEmacs frame can be placed within an "external client widget" managed | |
| 2141 by another application. This allows an application to use an XEmacs | |
| 2142 frame as its text pane rather than the standard Text widget that is | |
| 2143 provided with Motif or Athena. | |
| 2144 | |
| 2145 @item Community Participation | |
| 2459 | 2146 Joining the XEmacs development team is simple. Mail to |
| 2147 @email{xemacs-beta@@xemacs.org, XEmacs Developers}, and you're in! (If | |
| 2148 you want to be, of course. You're also welcome to just post | |
| 2149 development-related questions and bug reports.) The GNU Emacs | |
| 2417 | 2150 development team and internal mailing lists are still by invitation |
| 2151 only. | |
| 2152 | |
| 2153 The "bleeding edge" of mainline XEmacs development is available by | |
| 2154 anonymous CVS as are some subsidiary branches (check out the xemacs-gtk | |
| 2155 module for the latest in GUI features!) | |
| 2156 | |
| 2157 Development and maintenance of Lisp libraries is separated from the core | |
| 2158 editor development at a fairly low level. This provides better | |
| 2159 modularization and a better division of responsibility between external | |
| 2160 library maintainers and the XEmacs core development team. Even for | |
| 2161 packages the size of Gnus, XEmacs users normally have access to a | |
| 2162 pre-built version within a few weeks of a major release, and minor | |
| 2163 updates often within days. | |
| 2164 | |
| 2165 CVS commit authority is broadly dispersed. Recognized maintainers of | |
| 2166 LISP libraries who are willing to maintain XEmacs packaged versions | |
| 2167 automatically qualify for CVS accounts for their packages. | |
| 2168 @end table | |
| 2169 | |
| 2537 | 2170 @node Q1.6.3, Q1.6.4, Q1.6.2, Introduction |
| 2171 @unnumberedsubsec Q1.6.3: How much does XEmacs differ? | |
| 2417 | 2172 |
| 2173 RMS has asserted at times that XEmacs is merely a "patch" on top of | |
| 2537 | 2174 GNU Emacs (@pxref{Q1.6.4}). In fact, probably not more than 5% of the |
| 2417 | 2175 code, if that, remains unchanged, and nearly 14 years of work has gone |
| 2176 into XEmacs at this point. (GNU Emacs itself is only than 20 years | |
| 2177 old, and thus XEmacs has existed as a separate product for over 2/3 of | |
| 2178 the lifespan of GNU Emacs.) As a point of comparison, XEmacs 21.5 has | |
| 2179 perhaps 65,000 more lines of C code than GNU Emacs 21.2. | |
| 2180 | |
| 2181 However, the XEmacs developers strive to keep their code compatible with | |
| 2182 GNU Emacs, especially on the Lisp level. Much effort goes into | |
| 2183 "synching" the XEmacs Elisp code with recent GNU Emacs releases so as to | |
| 2184 benefit from GNU Emacs development work. (In contrast, almost no code | |
| 2185 from XEmacs has made it into GNU Emacs, and in fact the GNU Emacs | |
| 2186 developers are instructed by RMS not to even look at XEmacs source code! | |
| 2187 This stems from self-imposed licensing restrictions on the part of GNU | |
| 2188 Emacs -- and almost certainly out of hostility, as well.) | |
| 2189 | |
| 2537 | 2190 @node Q1.6.4, Q1.6.5, Q1.6.3, Introduction |
| 2191 @unnumberedsubsec Q1.6.4: Is XEmacs "GNU"? | |
| 2417 | 2192 |
| 2193 RMS insists on the term "GNU XEmacs" and maintains that | |
| 2194 | |
| 2195 @quotation | |
| 2196 XEmacs is GNU software because it's a modified version of a | |
| 2197 GNU program. And it is GNU software because the FSF is the copyright | |
| 2198 holder for most of it, and therefore the legal responsibility for | |
| 2199 protecting its free status falls on us whether we want it or not. This | |
| 2200 is why the term "GNU XEmacs" is legitimate. | |
| 2201 @end quotation | |
| 2202 | |
| 2203 In fact, FSF is @emph{not} the copyright holder for most of the code, | |
| 2537 | 2204 as very little unmodified FSF code remains (@pxref{Q1.6.3}). |
| 2417 | 2205 |
| 2206 Furthermore, RMS's assertion that XEmacs is "GNU" seems rather bizarre | |
| 2207 to the XEmacs developers given RMS's hostility and general lack of | |
| 2208 interest in cooperation. "GNU" software in general is part of the GNU | |
| 2209 Project, is distributed by it on their FTP site, and receives support | |
| 2210 (or at least cooperation), as well as implicit endorsement, from it. | |
| 2211 The GNU Project, however, has never supported XEmacs and never | |
| 2212 distributed XEmacs, and RMS's hostility is the farthest thing possible | |
| 2213 from an endorsement. In fact, the GNU Project distributes a number of | |
| 2214 non-GNU software projects on the FSF web site, but again XEmacs is not | |
| 2215 one of them. | |
| 2216 | |
| 2537 | 2217 @node Q1.6.5, Q1.6.6, Q1.6.4, Introduction |
| 2218 @unnumberedsubsec Q1.6.5: What is the correct way to refer to XEmacs and GNU Emacs? | |
| 2417 | 2219 |
| 2220 Unfortunately even the naming of these two applications has become | |
| 2221 politicized. Much of this stems from RMS, who has a history of | |
| 2222 politicizing similar issues. (Compare the controversy over "Lignux" | |
| 2223 and "GNU/Linux".) We would prefer that the terms "XEmacs" and "GNU | |
| 2224 Emacs" be used, which are neutral and acceptable to most people. RMS, | |
| 2225 however, is not willing to accept these terms. He insists that, if | |
| 2226 his product is called "GNU Emacs", then ours must be called "GNU | |
| 2537 | 2227 XEmacs". (For our opinion of this term, @xref{Q1.6.4}.) On the other |
| 2417 | 2228 hand, if our product is to be called "XEmacs", as we prefer, then his |
| 2229 product must simply be called "Emacs". The intent of this seems | |
| 2230 clear: RMS wants to make sure the names reflect his view that his | |
| 2231 version is the "real" Emacs and ours is merely a derivative, | |
| 2537 | 2232 second-class product (@pxref{Q1.6.3}). |
| 2417 | 2233 |
| 2234 The XEmacs developers hope that you will use the neutral terms | |
| 2235 "XEmacs" and "GNU Emacs" for these two specific products. "Emacs", on | |
| 2236 the other hand, is a generic term for a class of programmable text | |
| 2237 editors with a similar look-and-feel, and usually a Lisp-based | |
| 2238 extension language. These trace themselves back to early editors such | |
| 2239 as EINE, ZWEI, ZMACS and Multics Emacs. @xref{A History of Emacs,,, | |
| 2240 internals, XEmacs Internals Manual}. | |
| 2241 | |
| 2242 We also call upon RMS, in the spirit of furthering cooperation, to | |
| 2243 stop politicizing this issue and use the neutral terms "XEmacs" and | |
| 2244 "GNU Emacs". We have already acceded to RMS' wishes in this respect, | |
| 2245 and we expect him to do the same. (In the past, the XEmacs developers | |
| 2246 often used the terms "FSF Emacs" or "FSFmacs" or "RMSmacs" in | |
| 2247 reference to GNU Emacs; these terms were apparently modeled after RMS' | |
| 2248 own usage of "Gosmacs" and "Gosling Emacs" in reference to Unipress | |
| 2249 Emacs, produced by James Gosling. RMS, however, considers such terms | |
| 2250 to be insulting, so we refrain from using them as much as possible in | |
| 2251 preference to GNU Emacs.) | |
| 2252 | |
| 2537 | 2253 @node Q1.6.6, Q1.7.1, Q1.6.5, Introduction |
| 2254 @unnumberedsubsec Q1.6.6: Why haven't XEmacs and GNU Emacs merged? | |
| 2417 | 2255 |
| 2256 There are currently irreconcilable differences in the views about | |
| 2257 technical, programming, design, organizational and legal matters | |
| 2258 between Richard Stallman (RMS), the author and leader of the GNU Emacs | |
| 2259 project, and the XEmacs development team which provide little hope for | |
| 2260 a merge to take place in the short-term future. There have been | |
| 2261 repeated attempts at merging by all of the major XEmacs developers, | |
| 2262 starting from the early days of Lucid Emacs (in 1991), but they have | |
| 2263 all failed. RMS has very strong views about how GNU Emacs should be | |
| 2264 structured and how his project should be run, and during the repeated | |
| 2265 merge efforts has never demonstrated any realistic interest in | |
| 2266 sufficiently compromising or ceding control to allow a middle ground | |
| 2267 to be found. The basic problem seems to be the very different goals | |
| 2268 of RMS and the XEmacs project. The primary goals of the XEmacs | |
| 2269 project are technical and organizational -- we want to create the best | |
| 2270 editor possible, and to make it as easy as possible for people around | |
| 2271 the world to contribute. The primary goals of RMS, on the other hand, | |
| 2272 are political, and GNU Emacs, and any potential merge efforts with | |
| 2273 XEmacs, are strictly subservient to these goals. In fact, in many | |
| 2274 ways RMS sees GNU Emacs as the "poster child" of his aims, the one | |
| 2275 program in the GNU project that above all others must set an example | |
| 2276 to the world. (This has to do with the fact that GNU Emacs was the | |
| 2277 first program in the GNU project, and the only one that he is still | |
| 2278 personally involved with on a day-to-day basis.) Given his goals, his | |
| 2279 position is completely reasonable -- but unfortunately, makes any | |
| 2280 merge impossible. | |
| 2281 | |
| 2282 From the XEmacs perspective, the most intractable issues appear to be | |
| 2283 legal and organizational, specifically: | |
| 428 | 2284 |
| 2285 @itemize @bullet | |
| 2286 @item | |
| 2417 | 2287 RMS requires "legal papers" to be signed for all contributions of code |
| 2288 to GNU Emacs over 10 lines or so, transferring the copyright and all | |
| 2289 legal rights to the code to the Free Software Foundation. XEmacs does | |
| 2290 not and has never required this, since it has the practical effect of | |
| 2291 discouraging individual and in particular corporate contributions -- | |
| 2292 corporations will almost never sign away their legal rights to code | |
| 2293 since it makes it impossible to reuse the code in any product that | |
| 2294 whose license is not compatible with the GNU General Public License. | |
| 2295 Since RMS has shown no inclination to compromise on this issue, a | |
| 2296 merge would require that most of the existing XEmacs code would need | |
| 2297 to be thrown away and rewritten -- something the XEmacs developers are | |
| 2298 understandably reluctant to do. | |
| 2299 | |
| 2300 @item | |
| 2301 A repeated stumbling block in the merge talks has been the issue of | |
| 2302 organizational control over the resulting product. RMS has made it | |
| 2303 clear that he intends to have final say over design issues in a merged | |
| 2304 Emacs. Unfortunately, RMS and the XEmacs developers have repeatedly | |
| 2305 clashed over design decisions, and RMS' insistence on getting his way | |
| 2306 in such disagreements was the very reason for the split in the first | |
| 2307 place. This same issue has come up again and again in merge talks and | |
| 2308 we have never been able to come to a satisfactory resolution. To the | |
| 2309 extent that RMS is willing to compromise at all, it appears to be of a | |
| 2310 purely political rather than technical nature -- "If we support this | |
| 2311 feature of yours, we also get to support this other feature of mine." | |
| 2312 The XEmacs developers cannot see how such a process would lead to | |
| 2313 anything but a mess of incompatible things hodgepodged together. | |
| 2314 | |
| 2315 @item | |
| 2316 Because of the years of separate development, distinct and | |
| 2317 incompatible interfaces have developed and merging would be extremely | |
| 2318 difficult even with the above non-technical issues resolved. The | |
| 2319 problem has been exacerbated by the issue of legal papers -- because | |
| 2320 XEmacs code is not "kosher" from RMS' perspective, he discourages | |
| 2321 developers from even looking at it out of legal concerns. Although it | |
| 2322 is still possible to read the XEmacs documentation and run the | |
| 2323 program, the practical effect of this prohibition has been to strongly | |
| 2324 discourage code-sharing and cooperative development -- although a | |
| 2325 great deal of GNU Emacs code has been incorporated into XEmacs, | |
| 2326 practically none has gone the other direction. | |
| 428 | 2327 @end itemize |
| 2328 | |
| 2329 If you have a comment to add regarding the merge, it is a good idea to | |
| 2417 | 2330 avoid posting to the newsgroups, because of the very heated flamewars |
| 2331 that often result. Mail your questions to | |
| 2332 @email{xemacs-beta@@xemacs.org} and @email{emacs-devel@@gnu.org}. | |
| 2333 | |
| 2537 | 2334 @unnumberedsec 1.7: External Packages |
| 2335 | |
| 2559 | 2336 @node Q1.7.1, Q1.7.2, Q1.6.6, Introduction |
| 2337 @unnumberedsubsec Q1.7.1: What is the package system? | |
| 2338 | |
| 2339 In order to reduce the size and increase the maintainability of | |
| 2340 XEmacs, the majority of the Elisp packages that came with previous | |
| 2341 releases have been unbundled. They have been replaced by the package | |
| 2342 system. Each elisp add-on (or groups of them when they are small) now | |
| 2343 comes in its own tarball that contains a small search hierarchy. | |
| 2344 | |
| 2345 You select just the ones you need. Install them by untarring them into | |
| 2346 the right place. On startup XEmacs will find them, set up the load | |
| 2347 path correctly, install autoloads, etc, etc. | |
| 2348 | |
| 2349 @xref{Q2.1.1}, for more info on how to download and install the packages. | |
| 2350 | |
| 2351 @node Q1.7.2, Q1.7.3, Q1.7.1, Introduction | |
| 2352 @unnumberedsubsec Q1.7.2: Which external packages are there? | |
| 2537 | 2353 |
| 2354 @subheading Normal Packages | |
| 2355 | |
| 2356 A very broad collection of elisp packages. | |
| 2417 | 2357 |
| 2358 @table @asis | |
| 2537 | 2359 @item Sun |
| 2360 Support for Sparcworks. | |
| 2361 | |
| 2362 @item ada | |
| 2363 Ada language support. | |
| 2364 | |
| 2365 @item apel | |
| 2366 A Portable Emacs Library. Used by XEmacs MIME support. | |
| 2367 | |
| 2368 @item auctex | |
| 2369 Basic TeX/LaTeX support. | |
| 2370 | |
| 2371 @item bbdb | |
| 2372 The Big Brother Data Base: a rolodex-like database program. | |
| 2373 | |
| 2374 @item build | |
| 2375 Build XEmacs from within (UNIX, Windows). | |
| 2376 | |
| 2377 @item c-support | |
| 2378 Basic single-file add-ons for editing C code. | |
| 2379 | |
| 2380 @item calc | |
| 2381 Emacs calculator. | |
| 2382 | |
| 2383 @item calendar | |
| 2384 Calendar and diary support. | |
| 2385 | |
| 2386 @item cc-mode | |
| 2387 C, C++, Objective-C, Java, CORBA IDL, Pike and AWK language support. | |
| 2388 | |
| 2389 @item clearcase | |
| 2390 New Clearcase Version Control for XEmacs (UNIX, Windows). | |
| 2391 | |
| 2392 @item clearcase | |
| 2393 Support for the Clearcase version control system. | |
| 2394 | |
| 2395 @item cookie | |
| 2396 "Fortune cookie"-style messages. Includes Spook (suspicious phrases) | |
| 2397 and Yow (Zippy quotes). | |
| 2398 | |
| 2399 @item crisp | |
| 2400 Crisp/Brief emulation. | |
| 2401 | |
| 2402 @item debug | |
| 2403 GUD, gdb, dbx debugging support. | |
| 2404 | |
| 2405 @item dictionary | |
| 2406 Interface to RFC2229 dictionary servers. | |
| 2407 | |
| 2408 @item dired | |
| 2409 The DIRectory EDitor is for manipulating, and running commands on | |
| 2410 files in a directory. | |
| 2411 | |
| 2412 @item docbookide | |
| 2413 DocBook editing support. | |
| 2414 | |
| 2415 @item ecb | |
| 2416 Emacs source code browser. | |
| 2417 | |
| 2418 @item ecrypto | |
| 2419 Crypto functionality in Emacs Lisp. | |
| 2420 | |
| 2421 @item edebug | |
| 2422 An Emacs Lisp debugger. | |
| 2423 | |
| 2424 @item ediff | |
| 2425 Interface over GNU patch. | |
| 2426 | |
| 2427 @item edit-utils | |
| 2428 Miscellaneous editor extensions, you probably need this. | |
| 2429 | |
| 2430 @item edt | |
| 2431 DEC EDIT/EDT emulation. | |
| 2432 | |
| 2433 @item efs | |
| 2434 Treat files on remote systems the same as local files. | |
| 2435 | |
| 2436 @item eieio | |
| 2437 Enhanced Implementation of Emacs Interpreted Objects. | |
| 2438 | |
| 2439 @item elib | |
| 2440 Portable Emacs Lisp utilities library. | |
| 2441 | |
| 2442 @item emerge | |
| 2443 Another interface over GNU patch. | |
| 2444 | |
| 2445 @item erc | |
| 2446 ERC is an Emacs InternetRelayChat client. | |
| 2447 | |
| 2448 @item escreen | |
|
5384
3889ef128488
Fix misspelled words, and some grammar, across the entire source tree.
Jerry James <james@xemacs.org>
parents:
5028
diff
changeset
|
2449 Multiple editing sessions within a single frame (like screen). |
| 2537 | 2450 |
| 2451 @item eshell | |
| 2452 Command shell implemented entirely in Emacs Lisp. | |
| 2453 | |
| 2454 @item ess | |
| 2455 ESS: Emacs Speaks Statistics. | |
| 2456 | |
| 2457 @item eterm | |
| 2458 Terminal emulation. | |
| 2459 | |
| 2460 @item eudc | |
| 2461 Emacs Unified Directory Client (LDAP, PH). | |
| 2462 | |
| 2463 @item footnote | |
| 2464 Footnoting in mail message editing modes. | |
| 2465 | |
| 2466 @item forms | |
| 2467 Forms editing support (obsolete, use Widget instead). | |
| 2468 | |
| 2469 @item fortran-modes | |
| 2470 Fortran support. | |
| 2471 | |
| 2472 @item fortran-modes | |
| 2473 Fortran language support. | |
| 2474 | |
| 2475 @item frame-icon | |
| 2476 Set up mode-specific icons for each frame under XEmacs. | |
| 2477 | |
| 2478 @item fsf-compat | |
| 2479 GNU Emacs compatibility files. | |
| 2480 | |
| 2481 @item games | |
| 2482 Tetris, Sokoban, and Snake. | |
| 2483 | |
| 2484 @item general-docs | |
| 2485 General documentation. Presently, empty. | |
| 2486 | |
| 2487 @item gnats | |
| 2488 XEmacs bug reports. | |
| 2489 | |
| 2490 @item gnus | |
| 2491 The Gnus Newsreader and Mailreader. | |
| 2492 | |
| 2493 @item haskell-mode | |
| 2494 Haskell editing support. | |
| 2495 | |
| 2496 @item hm--html-menus | |
| 2497 HTML editing. | |
| 2498 | |
| 2499 @item hyperbole | |
| 2500 Hyperbole: The Everyday Info Manager. | |
| 2501 | |
| 2502 @item ibuffer | |
| 2503 Advanced replacement for buffer-menu. | |
| 2504 | |
| 2505 @item idlwave | |
| 2506 Editing and Shell mode for the Interactive Data Language. | |
| 2507 | |
| 2508 @item igrep | |
| 2509 Enhanced front-end for Grep. | |
| 2510 | |
| 2511 @item ilisp | |
| 2512 Front-end for interacting with Inferior Lisp (external lisps). | |
| 2513 | |
| 2514 @item ispell | |
| 2515 Spell-checking with GNU ispell. | |
| 2516 | |
| 2517 @item jde | |
| 2518 Integrated Development Environment for Java. | |
| 2519 | |
| 2520 @item liece | |
| 2521 IRC (Internet Relay Chat) client for Emacs. Note, this package is | |
| 2522 deprecated and will be removed, use riece instead. | |
| 2523 | |
| 2524 @item mail-lib | |
| 2525 Fundamental lisp files for providing email support. | |
| 2526 | |
| 2527 @item mailcrypt | |
| 2528 Support for messaging encryption with PGP. | |
| 2529 | |
| 2530 @item mew | |
| 2531 Messaging in an Emacs World; a MIME-based email program. | |
| 2532 | |
| 2533 @item mh-e | |
| 2534 The XEmacs Interface to the MH Mail System. | |
| 2535 | |
| 2536 @item mine | |
| 2537 Elisp implementation of the game 'Minehunt'. | |
| 2538 | |
| 2539 @item misc-games | |
| 2540 Other amusements and diversions. | |
| 2541 | |
| 2542 @item mmm-mode | |
| 2543 Support for Multiple Major Modes within a single buffer. | |
| 2544 | |
| 2545 @item net-utils | |
| 2546 Miscellaneous Networking Utilities. | |
| 2547 | |
| 2548 @item ocaml | |
| 2549 Objective Caml editing support. | |
| 2550 | |
| 2551 @item oo-browser | |
| 2552 OO-Browser: The Multi-Language Object-Oriented Code Browser. | |
| 2553 | |
| 2554 @item ocaml | |
| 2555 Objective Caml editing support. | |
| 2556 | |
| 2557 @item os-utils | |
| 2558 Miscellaneous single-file O/S utilities, for printing, archiving, | |
| 2559 compression, remote shells, etc. | |
| 2560 | |
| 2561 @item pc | |
| 2562 PC style interface emulation. | |
| 2563 | |
| 2564 @item pcl-cvs | |
| 2565 CVS frontend. | |
| 2566 | |
| 2567 @item pcomplete | |
| 2568 Provides programmatic completion. | |
| 2569 | |
| 2570 @item perl-modes | |
| 2571 Perl support. | |
| 2572 | |
| 2573 @item pgg | |
| 2574 Emacs interface to various PGP implementations. | |
| 2575 | |
| 2576 @item prog-modes | |
| 2577 Support for various programming languages. | |
| 2578 | |
| 2579 @item ps-print | |
| 2580 Printing functions and utilities. | |
| 2581 | |
| 2582 @item psgml | |
| 2583 Validated HTML/SGML editing. | |
| 2584 | |
| 2585 @item psgml-dtds | |
| 2586 A collection of DTDs for psgml. Note that this package is deprecated | |
| 2587 and will be removed in the future, most likely Q2/2003. Instead of using | |
| 2588 this, you should install needed DTDs yourself. | |
| 2589 | |
| 2590 @item python-modes | |
| 2591 Python language support. | |
| 2592 | |
| 2593 @item reftex | |
| 2594 Emacs support for LaTeX cross-references, citations. | |
| 2595 | |
| 2596 @item riece | |
| 2597 IRC (Internet Relay Chat) client for Emacs. | |
| 2598 | |
| 2599 @item rmail | |
| 2600 An obsolete Emacs mailer. If you do not already use it don't start. | |
| 2601 | |
| 2602 @item ruby-modes | |
| 2603 Ruby support. | |
| 2604 | |
| 2605 @item sasl | |
| 2606 Simple Authentication and Security Layer (SASL) library. | |
| 2607 | |
| 2608 @item scheme | |
| 2609 Front-end support for Inferior Scheme. | |
| 2610 | |
| 2611 @item semantic | |
| 2612 Semantic bovinator (Yacc/Lex for XEmacs). Includes Senator. | |
| 2613 | |
| 2614 @item sgml | |
| 2615 SGML/Linuxdoc-SGML editing. | |
| 2616 | |
| 2617 @item sh-script | |
| 2618 Support for editing shell scripts. | |
| 2619 | |
| 2620 @item sieve | |
| 2621 Manage Sieve email filtering scripts. | |
| 2622 | |
| 2623 @item slider | |
| 2624 User interface tool. | |
| 2625 | |
| 2626 @item sml-mode | |
| 2627 SML editing support. | |
| 2628 | |
| 2629 @item sounds-au | |
| 2630 XEmacs Sun sound files. | |
| 2631 | |
| 2632 @item sounds-wav | |
| 2633 XEmacs Microsoft sound files. | |
| 2634 | |
| 2635 @item speedbar | |
| 2636 Provides a separate frame with convenient references. | |
| 2637 | |
| 2638 @item strokes | |
| 2639 Mouse enhancement utility. | |
| 2640 | |
| 2641 @item supercite | |
| 2642 An Emacs citation tool for News & Mail messages. | |
| 2643 | |
| 2644 @item texinfo | |
| 2645 XEmacs TeXinfo support. | |
| 2646 | |
| 2647 @item text-modes | |
| 2648 Miscellaneous support for editing text files. | |
| 2649 | |
| 2650 @item textools | |
| 2651 Miscellaneous TeX support. | |
| 2652 | |
| 2653 @item time | |
| 2654 Display time & date on the modeline. | |
| 2655 | |
| 2656 @item tm | |
| 2657 Emacs MIME support. Not needed for gnus >= 5.8.0. | |
| 2658 | |
| 2659 @item tooltalk | |
| 2660 Support for building with Tooltalk. | |
| 2661 | |
| 2662 @item tpu | |
| 2663 DEC EDIT/TPU support. | |
| 2664 | |
| 2665 @item tramp | |
| 2666 Remote shell-based file editing. This is similar to EFS or Ange-FTP, | |
| 2667 but works with rsh/ssh and rcp/scp. | |
| 2668 | |
| 2669 @item vc | |
| 2670 Version Control for Free systems. | |
| 2671 | |
| 2672 @item vc-cc | |
| 2673 Version Control for ClearCase (UnFree) systems. | |
| 2674 | |
| 2675 @item vhdl | |
| 2676 Support for VHDL. | |
| 2677 | |
| 2678 @item view-process | |
| 2679 A Unix process browsing tool. | |
| 2680 | |
| 2681 @item viper | |
| 2682 VI emulation support. | |
| 2683 | |
| 2684 @item vm | |
| 2685 An Emacs mailer. | |
| 2686 | |
| 2687 @item w3 | |
| 2688 A Web browser. | |
| 2689 | |
| 2690 @item x-symbol | |
| 2691 Semi WYSIWYG for LaTeX, HTML, etc, using additional fonts. | |
| 2692 | |
| 2693 @item xemacs-base | |
| 2694 Fundamental XEmacs support, you almost certainly need this. | |
| 2695 | |
| 2696 @item xemacs-devel | |
| 2697 XEmacs Lisp developer support. This package contains utilities for | |
| 2698 supporting Lisp development. It is a single-file package so it may be | |
| 2699 tailored. | |
| 2700 | |
| 2701 @item xlib | |
| 2702 Emacs interface to X server. | |
| 2703 | |
| 2704 @item xslide | |
| 2705 XSL editing support. | |
| 2706 | |
| 2707 @item xslt-process | |
| 2708 A minor mode for (X)Emacs which allows running an XSLT processor on a | |
| 2709 buffer. | |
| 2710 | |
| 2711 @item xwem | |
| 2712 X Emacs Window Manager. | |
| 2713 | |
| 2714 @item zenirc | |
| 2715 ZENIRC IRC Client. | |
| 2417 | 2716 @end table |
| 2717 | |
| 2537 | 2718 @subheading Mule Support (mule) |
| 2719 | |
| 2720 MULti-lingual Enhancement. Support for world scripts such as | |
| 2721 Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc. | |
| 2722 To use these packages your XEmacs must be compiled with Mule | |
| 2723 support. | |
| 2724 | |
| 2725 @table @asis | |
| 2726 @item edict | |
| 2727 MULE: Lisp Interface to EDICT, Kanji Dictionary. | |
| 2728 | |
| 2729 @item egg-its | |
| 2730 MULE: Wnn (4.2 and 6) support. SJ3 support. | |
| 2731 | |
| 2732 @item latin-unity | |
| 2733 MULE: find single ISO 8859 character set to encode a buffer. | |
| 2734 | |
| 2735 @item latin-unity | |
| 2736 Unify character sets in a buffer. When characters belong to disjoint | |
| 2737 character sets, this attempts to translate the characters so | |
| 2738 that they belong to one character set. If the buffer coding system is | |
| 2739 not sufficient, this suggests different coding systems. | |
| 2740 | |
| 2741 @item leim | |
| 2742 MULE: Quail. All non-English and non-Japanese language support. | |
| 2743 | |
| 2744 @item locale | |
| 2745 MULE: Localized menubars and localized splash screens. | |
| 2746 | |
| 2747 @item lookup | |
| 2748 Dictionary support. (This isn't an English dictionary program) | |
| 2749 | |
| 2750 @item mule-base | |
| 2751 MULE: Basic Mule support, required for building with Mule. | |
| 2752 | |
| 2753 @item mule-ucs | |
| 2754 MULE: Extended coding systems (including Unicode) for XEmacs. | |
| 2755 | |
| 2756 @item mule-ucs | |
| 2757 Extended coding systems (including Unicode) for XEmacs. | |
| 2758 | |
| 2759 @item skk | |
| 2760 Another Japanese Language Input Method. Can be used without a | |
| 2761 separate process running as a dictionary server. | |
| 2762 @end table | |
| 2763 | |
| 2559 | 2764 @node Q1.7.3, Q1.7.4, Q1.7.2, Introduction |
| 2765 @unnumberedsubsec Q1.7.3: Do I need to have the packages to run XEmacs? | |
| 2766 | |
| 2767 Strictly speaking, no. XEmacs will build and install just fine without | |
| 2768 any packages installed. However, only the most basic editing functions | |
| 2769 will be available with no packages installed, so installing packages is | |
| 2770 an essential part of making your installed XEmacs _useful_. | |
| 2771 | |
| 2772 @node Q1.7.4, Q1.8.1, Q1.7.3, Introduction | |
| 2773 @unnumberedsubsec Q1.7.4: Is there a way to find which package has particular functionality? | |
| 2774 | |
| 2775 If you want to find out which package contains the functionality you | |
| 2776 are looking for, use @kbd{M-x package-get-package-provider}, and give it a | |
| 2777 symbol that is likely to be in that package. | |
| 2778 | |
| 2779 For example, if some code you want to use has a @code{(require 'thingatpt)} | |
| 2780 in it: | |
| 2781 | |
| 2782 @example | |
| 2783 M-x package-get-package-provider RET thingatpt RET | |
| 2784 @end example | |
| 2785 | |
| 2786 which will return something like: @samp{(fsf-compat "1.08").} | |
| 2787 | |
| 2537 | 2788 @unnumberedsec 1.8: Internationalization |
| 2789 | |
| 2559 | 2790 @node Q1.8.1, Q1.8.2, Q1.7.4, Introduction |
| 2537 | 2791 @unnumberedsubsec Q1.8.1: What is the status of internationalization support aka MULE (including Asian language support)? |
| 442 | 2792 |
| 2793 Both the stable and development versions of XEmacs include | |
| 1135 | 2794 internationalization support (aka MULE). MULE currently (21.4) works on |
| 2795 UNIX and Linux systems. It is possible to build with MULE on Windows | |
| 2796 systems, but if you really need MULE on Windows, it is recommended that | |
| 2797 you build and use the development (21.5) version, and deal with the | |
| 2798 instability of the development tree. Binaries compiled without MULE | |
| 2799 support run faster than MULE capable XEmacsen. | |
| 428 | 2800 |
| 2537 | 2801 @node Q1.8.2, Q1.8.3, Q1.8.1, Introduction |
| 2802 @unnumberedsubsec Q1.8.2: How can I help with internationalization? | |
| 430 | 2803 |
| 2804 If you would like to help, you may want to join the | |
| 2805 @email{xemacs-mule@@xemacs.org} mailing list. Especially needed are | |
| 2806 people who speak/write languages other than English, who are willing to | |
| 2807 use XEmacs/MULE regularly, and have some experience with Elisp. | |
| 428 | 2808 |
| 1135 | 2809 Translations of the TUTORIAL and man page are welcome, and XEmacs does |
| 2810 support multilingual menus, but we have few current translations. | |
| 2811 | |
| 2537 | 2812 @xref{Q1.5.2, How do I become a Beta Tester?}. |
| 2813 | |
| 2814 @node Q1.8.3, Q1.8.4, Q1.8.2, Introduction | |
| 2815 @unnumberedsubsec Q1.8.3: How do I type non-ASCII characters? | |
| 2417 | 2816 |
| 2459 | 2817 @xref{Q3.0.6, How can you type in special characters in XEmacs?}, in |
| 2417 | 2818 part 3 of this FAQ, for some simple methods that also work in non-MULE |
| 2819 builds of XEmacs (but only for one-octet coded character sets, and | |
| 2820 mostly for ISO 8859/1). Many of the methods available for Cyrillic | |
| 2537 | 2821 (@pxref{Q1.8.7, How about Cyrillic modes?}) work without MULE. MULE |
| 2822 has more general capabilities. @xref{Q1.8.5, Please explain the | |
| 2417 | 2823 various input methods in MULE/XEmacs}. |
| 2824 | |
| 2459 | 2825 @xref{Q4.0.8, How do I display non-ASCII characters?}, which covers |
| 2417 | 2826 display of non-ASCII characters. |
| 2827 | |
| 2537 | 2828 @node Q1.8.4, Q1.8.5, Q1.8.3, Introduction |
| 2829 @unnumberedsubsec Q1.8.4: Can XEmacs messages come out in a different language? | |
| 428 | 2830 |
| 1135 | 2831 The message-catalog support was written but is badly bit-rotted. XEmacs |
| 2832 20 and 21 did @emph{not} support it, and early releases of XEmacs 22 | |
| 2833 will not either. | |
| 2834 | |
| 2835 However, menubar localization @emph{does} work. To enable it, add to | |
| 2836 your @file{Emacs} file entries like this: | |
| 428 | 2837 |
| 2838 @example | |
| 440 | 2839 Emacs*XlwMenu.resourceLabels: True |
| 2840 Emacs*XlwMenu.file.labelString: Fichier | |
| 442 | 2841 Emacs*XlwMenu.openInOtherWindow.labelString: In anderem Fenster oeffnen |
| 428 | 2842 @end example |
| 2843 | |
| 2844 The name of the resource is derived from the non-localized entry by | |
| 2845 removing punctuation and capitalizing as above. | |
| 2846 | |
| 2537 | 2847 @node Q1.8.5, Q1.8.6, Q1.8.4, Introduction |
| 2848 @unnumberedsubsec Q1.8.5: Please explain the various input methods in MULE/XEmacs | |
| 428 | 2849 |
| 1135 | 2850 Mule supports a wide variety of input methods. There are three basic |
| 2851 classes: Lisp implementations, generic platform support, and library | |
| 2852 interfaces. | |
| 2853 | |
| 2854 @emph{Lisp implementations} include Quail, which provides table-driven input | |
| 2855 methods for almost all the character sets that Mule supports (including | |
| 2856 all of the ISO 8859 family, the Indic languages, Thai, and so on), and | |
| 2857 SKK, for Japanese. (SKK also supports an interface to an external | |
| 2858 "dictionary server" process.) Quail supports both typical "dead-key" | |
| 2859 methods (eg, in the "latin-1-prefix" method, @kbd{" a} produces ä, LATIN | |
| 2860 SMALL LETTER A WITH DIAERESIS), and the complex dictionary-based phonetic | |
| 2861 methods used for Asian ideographic languages like Chinese. | |
| 2862 | |
| 2863 Lisp implementations can be less powerful (but they are not perceptibly | |
| 2864 inefficient), and of course are not portable to non-Emacs applications. | |
| 2865 The incompatibility can be very annoying. On the other hand, they | |
| 2866 require no special platform support or external libraries, so if you can | |
| 2867 display the characters, Mule can input them for you and you can edit, | |
| 2868 anywhere. | |
| 2869 | |
| 2870 @emph{Generic platform support} is currently limited to the X Input | |
| 2871 Method (XIM) framework, although support for MSIME (for MS Windows) is | |
| 2872 planned, and IIIMF (Sun's Internet-Intranet Input Method Framework) | |
| 2873 support is extremely desirable. XIM is enabled at build time by use of | |
| 2874 the @samp{--with-xim} flag to @code{configure}. For use of XIM, see | |
| 2875 your platform documentation. However, normally the input method you use | |
| 2876 is specified via the @samp{LANG} and @samp{XMODIFIERS} environment | |
| 2877 variables. | |
| 2878 | |
| 2879 Of course, input skills are portable across most applications. However, | |
| 2880 especially in modern GUI systems the habit of using bucky bits has | |
| 2881 fallen into sad disuse, and many XIM systems are poorly configured for | |
| 2882 use with Emacs. For example, the kinput2 input manager (a separate | |
| 2883 process providing an interface between Japanese dictionary servers such | |
| 2884 as Canna and Wnn, and the application) tends to gobble up keystrokes | |
| 2885 generating Meta characters. This means that to edit while using an XIM | |
| 2886 input method, you must toggle the input method off every time you want | |
| 2887 to use @kbd{M-f}. Your mileage may vary. | |
| 2888 | |
| 2889 @emph{Library interfaces} are most common for Japanese, although Wnn | |
| 2890 supports Chinese (traditional and simplified) and Korean. There are | |
| 2891 Chinese and Korean input servers available, but we do not know of any | |
| 2892 patches for XEmacs to use them directly. You can use them via | |
| 2893 IM-enabled terminals, by manipulating the terminal coding systems. We | |
| 2894 describe only the Japanese-oriented systems here. The advantage of | |
| 2895 these systems is that they are very powerful, and on platforms where | |
| 2896 they are available there is typically a wide range of applications that | |
| 2897 support them. Thus your input skills are portable across applications. | |
| 2898 | |
| 2899 Mule provides built-in interfaces to the following input methods: Wnn4, | |
| 2900 Wnn6, Canna, and SJ3. These can be configured at build time. There are | |
| 2901 patches available (no URL, sorry) to support the SKK server, as well. | |
| 2902 Wnn and SJ3 use the @code{egg} user interface. The interface for Canna | |
| 2903 is specialized to Canna. | |
| 428 | 2904 |
| 2905 Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto | |
| 1135 | 2906 University. It is a powerful and complex system. Wnn4 is free and Wnn6 |
| 2907 is not. Wnn uses grammatical hints and probability of word association, | |
| 2908 so in principle Wnn can be cleverer than other methods. | |
| 2909 | |
| 2910 Canna, made by NEC, supports only Japanese. It is a simple and powerful | |
| 2911 system. Canna uses only grammar, but its grammar and dictionary are | |
| 2912 quite sophisticated. So for standard modern Japanese, Canna seems | |
| 2913 cleverer than Wnn4. In addition, the UNIX version of Canna is free (now | |
| 2914 there is a Microsoft Windows version). | |
| 2915 | |
| 2916 SJ3, by Sony, supports only Japanese. | |
| 428 | 2917 |
| 2918 Egg consists of following parts: | |
| 2919 | |
| 2920 @enumerate | |
| 2921 @item | |
| 2922 Input character Translation System (ITS) layer. | |
| 2923 It translates ASCII inputs to Kana/PinYin/Hangul characters. | |
| 2924 | |
| 2925 @item | |
| 2926 Kana/PinYin/Hangul to Kanji transfer layer. | |
| 1135 | 2927 The interface layer to network Kana-Kanji server (Wnn and Sj3). |
| 428 | 2928 @end enumerate |
| 2929 | |
| 1135 | 2930 These input methods are modal. They have a raw (alphabet) mode, a |
| 2931 phonetic input mode, and Kana-Kanji transfer mode. However there are | |
| 2932 mode-less input methods for Egg and Canna. @samp{boiled-egg} is a | |
| 2933 mode-less input method running on Egg. For Canna, @samp{canna.el} has a | |
| 2934 tiny boiled-egg-like command, @code{(canna-boil)}, and there are some | |
| 2935 boiled-egg-like utilities. | |
| 2936 | |
| 2937 Much of this information was provided by @email{morioka@@jaist.ac.jp, | |
| 2938 MORIOKA Tomohiko}. | |
| 428 | 2939 |
| 2537 | 2940 @node Q1.8.6, Q1.8.7, Q1.8.5, Introduction |
| 2941 @unnumberedsubsec Q1.8.6: How do I portably code for MULE/XEmacs? | |
| 428 | 2942 |
| 1135 | 2943 MULE has evolved rapidly over the last few years, and the original third |
| 2944 party patch (for GNU Emacs 19), GNU Emacs 20+, and XEmacs 20+ have quite | |
| 2945 different implementations. The APIs also vary although recent versions | |
| 2946 of XEmacs have tended to converge to the GNU Emacs standard. | |
| 2947 | |
| 2948 MULE implementations are going to continue to evolve. Both GNU Emacs | |
| 2949 and XEmacs are working hard on Unicode support, which will involve new | |
| 2950 APIs and probably variations on old ones. For XEmacs 22, the old ISO | |
| 2951 2022-based system for recognizing encodings will be replaced by a much | |
| 2952 more flexible system, which should improve accuracy of automatic coding | |
| 2953 detections, but will also involve new APIs. | |
| 2954 | |
| 428 | 2955 @email{morioka@@jaist.ac.jp, MORIOKA Tomohiko} writes: |
| 2956 | |
| 2957 @quotation | |
| 1135 | 2958 The application implementor must write separate code for these mule |
| 2959 variants. [Please don't hesitate to report these variants to us; they | |
| 2960 are not, strictly speaking, bugs, but they give third-party developers | |
| 2961 the same kind of creepy-crawly feeling. We'll do what we can. -- Ed.] | |
| 428 | 2962 |
| 2963 MULE and the next version of Emacs are similar but the symbols are very | |
| 2964 different---requiring separate code as well. | |
| 2965 | |
| 2966 Namely we must support 3 kinds of mule variants and 4 or 5 or 6 kinds of | |
| 2967 emacs variants... (;_;) I'm shocked, so I wrote a wrapper package called | |
| 1135 | 2968 @code{emu} to provide a common interface. [There is an XEmacs package |
| 2969 of APEL which provides much more comprehensive coverage. Be careful, | |
| 2970 however; APEL has problems of its own. -- Ed.] | |
| 428 | 2971 |
| 2972 I have the following suggestions about dealing with mule variants: | |
| 2973 | |
| 2974 @itemize @bullet | |
| 2975 @item | |
| 2976 @code{(featurep 'mule)} @code{t} on all mule variants | |
| 2977 | |
| 2978 @item | |
| 2979 @code{(boundp 'MULE)} is @code{t} on only MULE. Maybe the next version | |
| 2980 of Emacs will not have this symbol. | |
| 2981 | |
| 2982 @item | |
| 2983 MULE has a variable @code{mule-version}. Perhaps the next version of | |
| 2984 Emacs will have this variable as well. | |
| 2985 @end itemize | |
| 2986 | |
| 2987 Following is a sample to distinguish mule variants: | |
| 2988 | |
| 2989 @lisp | |
| 2990 (if (featurep 'mule) | |
| 2991 (cond ((boundp 'MULE) | |
| 2992 ;; for original Mule | |
| 2993 ) | |
| 440 | 2994 ((string-match "XEmacs" emacs-version) |
| 2995 ;; for XEmacs with Mule | |
| 2996 ) | |
| 2997 (t | |
| 2998 ;; for next version of Emacs | |
| 2999 )) | |
| 428 | 3000 ;; for old emacs variants |
| 3001 ) | |
| 3002 @end lisp | |
| 3003 @end quotation | |
| 3004 | |
| 2537 | 3005 @node Q1.8.7, Q1.8.8, Q1.8.6, Introduction |
| 3006 @unnumberedsubsec Q1.8.7: How about Cyrillic modes? | |
| 428 | 3007 |
| 3008 @email{ilya@@math.ohio-state.edu, Ilya Zakharevich} writes: | |
| 3009 | |
| 3010 @quotation | |
| 3011 There is a cyrillic mode in the file @file{mysetup.zip} in | |
| 3012 @iftex | |
| 3013 @* | |
| 3014 @end iftex | |
| 3015 @uref{ftp://ftp.math.ohio-state.edu/pub/users/ilya/emacs/}. This is a | |
| 3016 modification to @email{ava@@math.jhu.ed, Valery Alexeev's} @file{russian.el} | |
| 3017 which can be obtained from | |
| 3018 @end quotation | |
| 3019 | |
| 871 | 3020 @uref{http://www.math.uga.edu/~valery/russian.el}. |
| 428 | 3021 |
| 3022 @email{d.barsky@@ee.surrey.ac.uk, Dima Barsky} writes: | |
| 3023 | |
| 3024 @quotation | |
| 3025 There is another cyrillic mode for both GNU Emacs and XEmacs by | |
| 3026 @email{manin@@camelot.mssm.edu, Dmitrii | |
| 3027 (Mitya) Manin} at | |
| 3028 @iftex | |
| 3029 | |
| 3030 @end iftex | |
| 3031 @uref{http://kulichki-lat.rambler.ru/centrolit/manin/cyr.el}. | |
| 3032 @c Link above, <URL:http://camelot.mssm.edu/~manin/cyr.el> was dead. | |
| 3033 @c Changed to russian host instead | |
| 3034 @end quotation | |
| 3035 | |
| 3036 @email{rebecca.ore@@op.net, Rebecca Ore} writes: | |
| 3037 | |
| 3038 @quotation | |
| 3039 The fullest resource I found on Russian language use (in and out of | |
| 661 | 3040 XEmacs) is @uref{http://www.ibiblio.org/sergei/Software/Software.html} |
| 428 | 3041 @end quotation |
| 3042 | |
| 2537 | 3043 @node Q1.8.8, Q1.8.9, Q1.8.7, Introduction |
| 3044 @unnumberedsubsec Q1.8.8: Does XEmacs support Unicode? | |
| 2417 | 3045 |
| 3046 To get Unicode support, you need a Mule-enabled XEmacs. | |
| 3047 | |
| 3048 21.5 has internal support for Unicode and supports it fully, although we | |
| 3049 don't yet use it as the internal encoding. | |
| 3050 | |
| 3051 21.4 supports Unicode partially -- as an external encoding for files, | |
| 2537 | 3052 processes, and terminals, but without font support. @xref{Q1.8.9, How |
| 2417 | 3053 does XEmacs display Unicode?}. To get Unicode support in 21.4, |
| 3054 install Mule-UCS from packages in the usual way, and put | |
| 745 | 3055 |
| 1616 | 3056 @example |
| 745 | 3057 (require 'un-define) |
| 3058 (set-coding-priority-list '(utf-8)) | |
| 1616 | 3059 (set-coding-category-system 'utf-8 'utf-8) |
| 3060 @end example | |
| 3061 | |
| 3062 in your init file to enable the UTF-8 coding system. You may wish to | |
| 3063 view the documentation of @code{set-coding-priority-list} if you find | |
| 3064 that files that are not UTF-8 are being mis-recognized as UTF-8. | |
| 745 | 3065 |
| 2417 | 3066 Install standard national fonts (not Unicode fonts) for all character |
| 2537 | 3067 sets you use. @xref{Q1.8.9, How does XEmacs display Unicode??}. |
| 745 | 3068 |
| 3069 Mule-UCS also supports 16-bit forms of Unicode (UTF-16). It does not | |
| 3070 support 31-bit forms of Unicode (UTF-32 or UCS-4). | |
| 3071 | |
| 2537 | 3072 @node Q1.8.9, , Q1.8.8, Introduction |
| 3073 @unnumberedsubsec Q1.8.9: How does XEmacs display Unicode? | |
| 745 | 3074 |
| 3075 Mule doesn't have a Unicode charset internally, so there's nothing to | |
| 3076 bind a Unicode registry to. It would not be straightforward to create, | |
| 3077 either, because Unicode is not ISO 2022-compatible. You'd have to | |
| 3078 translate it to multiple 96x96 pages. | |
| 3079 | |
| 3080 This means that Mule-UCS uses ordinary national fonts for display. This | |
| 3081 is not really a problem, except for those languages that use the Unified | |
| 3082 Han characters. The problem here is that Mule-UCS maps from Unicode | |
| 3083 code points to national character sets in a deterministic way. By | |
| 3084 default, this means that Japanese fonts are tried first, then Chinese, | |
| 3085 then Korean. To change the priority ordering, use the command | |
| 3086 `un-define-change-charset-order'. | |
| 3087 | |
| 3088 It also means you can't use Unicode fonts directly, at least not without | |
| 3089 extreme hackery. You can run -nw with (set-terminal-coding-system | |
| 3090 'utf-8) if you really want a Unicode font for some reason. | |
| 3091 | |
| 3092 Real Unicode support will be introduced in XEmacs 22.0. | |
| 3093 | |
| 2459 | 3094 @node Installation, Editing, Introduction, Top |
| 2417 | 3095 @unnumbered 2 Installation and Troubleshooting |
| 428 | 3096 |
| 3097 This is part 2 of the XEmacs Frequently Asked Questions list. This | |
| 2417 | 3098 section is devoted to Installation, Maintenance and Troubleshooting. |
| 428 | 3099 |
| 3100 @menu | |
| 2559 | 3101 2.0: Installation (General) |
| 3102 * Q2.0.1:: How do I build and install XEmacs? | |
| 3103 * Q2.0.2:: Where do I find external libraries? | |
| 3104 * Q2.0.3:: How do I specify the paths that XEmacs uses for finding files? | |
| 3105 * Q2.0.4:: Running XEmacs without installing | |
| 3106 * Q2.0.5:: XEmacs is too big | |
| 3107 | |
| 3108 2.1: Package Installation | |
| 3109 * Q2.1.1:: How do I install the packages? | |
| 3110 * Q2.1.2:: Can I install the packages individually? | |
| 3111 * Q2.1.3:: Can I install the packages automatically? | |
| 3112 * Q2.1.4:: Can I upgrade or remove packages? | |
| 3113 * Q2.1.5:: Which packages to install? | |
| 3114 * Q2.1.6:: Can you describe the package location process in more detail? | |
| 3115 * Q2.1.7:: EFS fails with "500 AUTH not understood" | |
| 3116 | |
| 3117 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) | |
| 3118 * Q2.2.1:: Libraries in non-standard locations | |
| 3119 * Q2.2.2:: Why can't I strip XEmacs? | |
| 3404 | 3120 * Q2.2.3:: X11/bitmaps/gray (or other X11-related file) not found. |
| 2559 | 3121 |
| 3122 2.3: Windows Installation (Windows, Cygwin, MinGW) | |
| 3123 * Q2.3.1:: What exactly are all the different ways to build XEmacs under Windows? | |
| 3124 * Q2.3.2:: What compiler/libraries do I need to compile XEmacs? | |
| 3125 * Q2.3.3:: How do I compile the native port? | |
| 3126 * Q2.3.4:: What do I need for Cygwin? | |
| 3127 * Q2.3.5:: How do I compile under Cygwin? | |
| 3128 * Q2.3.6:: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 3129 * Q2.3.7:: How do I compile with X support? | |
| 3130 * Q2.3.8:: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 3131 | |
| 3132 2.4: General Troubleshooting | |
| 3133 * Q2.4.1:: How do I deal with bugs or with problems building, installing, or running? | |
| 3134 * Q2.4.2:: Help! XEmacs just crashed on me! | |
| 3135 * Q2.4.3:: XEmacs crashes and I compiled it myself. | |
| 3136 * Q2.4.4:: How to debug an XEmacs problem with a debugger | |
| 3137 * Q2.4.5:: I get a cryptic error message when trying to do something. | |
| 3138 * Q2.4.6:: XEmacs hangs when I try to do something. | |
| 3139 * Q2.4.7:: I get an error message when XEmacs is running in batch mode. | |
| 3140 * Q2.4.8:: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 3141 * Q2.4.9:: @kbd{C-g} doesn't work for me. Is it broken? | |
| 3142 * Q2.4.10:: How do I debug process-related problems? | |
| 3143 * Q2.4.11:: XEmacs is outputting lots of X errors. | |
| 3144 * Q2.4.12:: After upgrading, XEmacs won't do `foo' any more! | |
| 3145 | |
| 3146 2.5: Startup-Related Problems | |
| 3147 * Q2.5.1:: XEmacs cannot connect to my X Terminal! | |
| 3148 * Q2.5.2:: Startup problems related to paths or package locations. | |
|
4658
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
3149 * Q2.5.3:: XEmacs won't start without network, or starts slowly. |
| 2559 | 3150 * Q2.5.4:: Startup warnings about deducing proper fonts? |
| 3151 * Q2.5.5:: Warnings from incorrect key modifiers. | |
| 3152 * Q2.5.6:: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? | |
|
5390
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
3153 * Q2.5.7:: XEmacs issues messages about ``auto-autoloads already loaded.'' |
| 428 | 3154 @end menu |
| 3155 | |
| 2559 | 3156 @unnumberedsec 2.0: Installation (General) |
| 2417 | 3157 |
| 428 | 3158 @node Q2.0.1, Q2.0.2, Installation, Installation |
| 2559 | 3159 @unnumberedsubsec Q2.0.1: How do I build and install XEmacs? |
| 3160 | |
| 3161 See the file @file{etc/NEWS} for information on new features and other | |
| 3162 user-visible changes since the last version of XEmacs. | |
| 3163 | |
| 3164 The file @file{INSTALL} in the top-level directory says how to bring | |
| 3165 up XEmacs on Unix and Cygwin, once you have loaded the entire subtree | |
| 3166 of this directory. | |
| 3167 | |
| 3168 See the file @file{nt/README} for instructions on building XEmacs for | |
| 3169 Microsoft Windows. | |
| 3170 | |
| 3171 @xref{Q2.1.1}, for the installation of (essential) add on packages. | |
| 2417 | 3172 |
| 3173 @node Q2.0.2, Q2.0.3, Q2.0.1, Installation | |
| 2559 | 3174 @unnumberedsubsec Q2.0.2: Where do I find external libraries? |
| 2417 | 3175 |
| 2459 | 3176 All external libraries used by XEmacs can be found on the XEmacs web |
| 2417 | 3177 site |
| 3178 @iftex | |
| 3179 @* | |
| 3180 @end iftex | |
| 2459 | 3181 @uref{http://www.xemacs.org/Download/optLibs.html}. |
| 2417 | 3182 |
| 3183 The library versions available here are known to work with XEmacs. | |
| 3184 (Newer versions will probably work as well but we can't guarantee it.) | |
| 3185 We try to keep the libraries up-to-date but may not always succeed. | |
| 2459 | 3186 Check the above page for the canonical locations of the external libraries, |
| 3187 allowing you to download the latest, bleeding-edge versions. | |
| 2417 | 3188 |
| 2559 | 3189 @node Q2.0.3, Q2.0.4, Q2.0.2, Installation |
| 3190 @unnumberedsubsec Q2.0.3: How do I specify the paths that XEmacs uses for finding files? | |
| 2417 | 3191 |
| 3192 You can specify what paths to use by using a number of different flags | |
| 3193 when running configure. See the section MAKE VARIABLES in the top-level | |
| 3194 file INSTALL in the XEmacs distribution for a listing of those flags. | |
| 3195 | |
| 3196 Most of the time, however, the simplest fix is: @strong{do not} specify | |
| 3197 paths as you might for GNU Emacs. XEmacs can generally determine the | |
| 3198 necessary paths dynamically at run time. The only path that generally | |
| 3199 needs to be specified is the root directory to install into. That can | |
| 3200 be specified by passing the @code{--prefix} flag to configure. For a | |
| 3201 description of the XEmacs install tree, please consult the @file{NEWS} | |
| 3202 file. | |
| 3203 | |
| 2559 | 3204 @node Q2.0.4, Q2.0.5, Q2.0.3, Installation |
| 3205 @unnumberedsubsec Q2.0.4: Running XEmacs without installing | |
| 442 | 3206 |
| 3207 How can I just try XEmacs without installing it? | |
| 428 | 3208 |
| 3209 XEmacs will run in place without requiring installation and copying of | |
| 3210 the Lisp directories, and without having to specify a special build-time | |
| 3211 flag. It's the copying of the Lisp directories that requires so much | |
| 3212 space. XEmacs is largely written in Lisp. | |
| 3213 | |
| 3214 A good method is to make a shell alias for xemacs: | |
| 3215 | |
| 3216 @example | |
| 2459 | 3217 alias xemacs=/src/xemacs-21.5/src/xemacs |
| 428 | 3218 @end example |
| 3219 | |
| 3220 (You will obviously use whatever directory you downloaded the source | |
| 2459 | 3221 tree to instead of @file{/src/xemacs-21.5}). |
| 428 | 3222 |
| 3223 This will let you run XEmacs without massive copying. | |
| 3224 | |
| 2559 | 3225 @node Q2.0.5, Q2.1.1, Q2.0.4, Installation |
| 3226 @unnumberedsubsec Q2.0.5: XEmacs is too big | |
| 428 | 3227 |
| 442 | 3228 The space required by the installation directories can be |
| 428 | 3229 reduced dramatically if desired. Gzip all the .el files. Remove all |
| 442 | 3230 the packages you'll never want to use. Remove the TexInfo manuals. |
| 428 | 3231 Remove the Info (and use just hardcopy versions of the manual). Remove |
| 3232 most of the stuff in etc. Remove or gzip all the source code. Gzip or | |
| 3233 remove the C source code. Configure it so that copies are not made of | |
| 1138 | 3234 the support lisp. |
| 428 | 3235 |
| 3236 These are all Emacs Lisp source code and bytecompiled object code. You | |
| 3237 may safely gzip everything named *.el here. You may remove any package | |
| 3238 you don't use. @emph{Nothing bad will happen if you delete a package | |
| 3239 that you do not use}. You must be sure you do not use it though, so be | |
| 3240 conservative at first. | |
| 3241 | |
| 1648 | 3242 Any package with the possible exceptions of xemacs-base, and EFS are |
| 3243 candidates for removal. Ask yourself, @emph{Do I ever want to use this | |
| 3244 package?} If the answer is no, then it is a candidate for removal. | |
| 428 | 3245 |
| 3246 First, gzip all the .el files. Then go about package by package and | |
| 3247 start gzipping the .elc files. Then run XEmacs and do whatever it is | |
| 1648 | 3248 you normally do. If nothing bad happens, then remove the package. You |
| 3249 can remove a package via the PUI interface | |
| 3250 (@code{M-x pui-list-packages}, then press @kbd{d} to mark the packages | |
| 3251 you wish to delete, and then @kbd{x} to delete them. | |
| 3252 | |
| 3253 Another method is to do @code{M-x package-get-delete-package}. | |
| 428 | 3254 |
| 2559 | 3255 @unnumberedsec 2.1: Package Installation |
| 3256 | |
| 3257 @node Q2.1.1, Q2.1.2, Q2.0.5, Installation | |
| 3258 @unnumberedsubsec Q2.1.1: How do I install the packages? | |
| 3259 | |
| 3260 There are three ways to install the packages. | |
| 3261 | |
| 3262 @enumerate | |
| 3263 @item | |
| 3264 Manually, all at once, using the 'Sumo Tarball'. | |
| 3265 @item | |
| 3266 Manually, using individual package tarballs. | |
| 3267 @item | |
| 3268 Automatically, using the package tools from XEmacs. | |
| 3269 @end enumerate | |
| 3270 | |
| 3271 If you don't want to mess with the packages, it is easiest to just | |
| 3272 grab them manually, all at once. (For the other two ways, | |
| 3273 @xref{Q2.1.2}, and @xref{Q2.1.3}.) Download the file | |
| 3274 | |
| 3275 @file{xemacs-sumo.tar.gz} | |
| 3276 | |
| 3277 For an XEmacs compiled with Mule you also need | |
| 3278 | |
| 3279 @file{xemacs-mule-sumo.tar.gz} | |
| 3280 | |
| 3281 These are in the @file{packages} directory on your XEmacs mirror | |
| 3282 archive: @uref{ftp://ftp.xemacs.org/pub/xemacs/packages} or its | |
| 3283 mirrors. N.B. They are called 'Sumo Tarballs' for good reason. They | |
| 3284 are currently about 19MB and 4.5MB (gzipped) respectively. | |
| 3285 | |
| 3286 Install them on Unix and Mac OS X using the shell/Terminal command | |
| 3287 | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3288 @code{cd $prefix/share/xemacs ; gunzip -c <tarballname> | tar xf -} |
| 2559 | 3289 |
| 3290 Where @samp{$prefix} is what you gave to the @samp{--prefix} flag to | |
| 3291 @file{configure}, and defaults to @file{/usr/local}. | |
| 3292 | |
| 3293 If you have GNU tar you can use: | |
| 3294 | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3295 @code{cd $prefix/share/xemacs ; tar zxvf <tarballname>} |
| 2559 | 3296 |
| 3018 | 3297 If you have the packages somewhere nonstandard and don't want to bother |
| 3298 with @samp{$prefix} (for example, you're a developer and are compiling | |
| 3299 the packages yourself, and want your own private copy of everything), | |
| 3300 you can also directly specify this using @file{configure}. To do this | |
| 3179 | 3301 with 21.5 and above use the @samp{--with-late-packages} parameter to |
| 3018 | 3302 specify the directory under which you untarred the above tarballs. |
| 3303 Under 21.4 and previous you need to use @samp{--package-path}. Using | |
| 3304 these options looks something like this: | |
| 2559 | 3305 |
| 3306 @example | |
| 3307 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ... | |
| 3308 @end example | |
| 3309 | |
| 3310 Under Windows, you need to place the above @samp{tar.gz} files in the | |
| 3311 directory specified using the @samp{PACKAGE_PREFIX} value in | |
| 3312 @file{nt/config.inc} and by default is @file{\Program Files\XEmacs}. | |
| 3313 (To untar a @samp{tar.gz} file you will need to use a utility such as | |
| 3314 WinZip, unless you have Cygwin or a similar environment installed, in | |
| 3315 which case the above Unix shell command should work fine.) If you want | |
| 3316 the packages somewhere else, just change @samp{PACKAGE_PREFIX}. | |
| 3317 | |
| 3318 Note that XEmacs finds the packages automatically anywhere underneath | |
| 3319 the directory tree where it expects to find the packages. All you | |
| 3320 need to do is put stuff there; you don't need to run any program to | |
| 4311 | 3321 tell XEmacs to find the packages, or do anything of that sort. |
| 2559 | 3322 |
| 3323 However, XEmacs will only notice newly installed packages when it | |
| 3324 starts up, so you will have to restart if you are already running | |
| 3325 XEmacs. | |
| 3326 | |
| 3327 For more details, @xref{Startup Paths,,,xemacs, the XEmacs User's | |
| 3328 Manual}, and @xref{Packages,,,xemacs, the XEmacs User's Manual}. | |
| 3329 | |
| 3330 As the Sumo tarballs are not regenerated as often as the individual | |
| 3331 packages, it is recommended that you use the automatic package tools | |
| 3332 afterwards to pick up any recent updates. | |
| 3333 | |
| 3334 @emph{NOTE}: For detailed information about how the package | |
| 3335 hierarchies work, @xref{Package Overview,,,lispref, the XEmacs Lisp | |
| 3336 Reference Manual}. | |
| 3337 | |
| 3338 @node Q2.1.2, Q2.1.3, Q2.1.1, Installation | |
| 3339 @unnumberedsubsec Q2.1.2: Can I install the packages individually? | |
| 3340 | |
| 3341 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. | |
| 3342 | |
| 3343 Note: If you are upgrading packages already installed, it's best to | |
| 3344 remove the old package first (@pxref{Q2.1.4}). | |
| 3345 | |
| 3346 For example if we are installing the @samp{xemacs-base} | |
| 3347 package (version 1.48): | |
| 3348 | |
| 3349 @example | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3350 mkdir $prefix/share/xemacs/xemacs-packages RET # if it does not exist yet |
|
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3351 cd $prefix/share/xemacs/xemacs-packages RET |
| 2559 | 3352 gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET |
| 3353 @end example | |
| 3354 | |
| 3355 Or if you have GNU tar, the last step can be: | |
| 3356 | |
| 3357 @example | |
| 3358 tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET | |
| 3359 @end example | |
| 3360 | |
| 3361 For MULE related packages, it is best to untar into the @samp{mule-packages} | |
| 3362 hierarchy, i.e. for the @samp{mule-base} package, version 1.37: | |
| 3363 | |
| 3364 @example | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3365 mkdir $prefix/share/xemacs/mule-packages RET # if it does not exist yet |
|
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3366 cd $prefix/share/xemacs/mule-packages RET |
| 2559 | 3367 gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET |
| 3368 @end example | |
| 3369 | |
| 3370 Or if you have GNU tar, the last step can be: | |
| 3371 | |
| 3372 @example | |
| 3373 tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET | |
| 3374 @end example | |
| 3375 | |
| 3376 @node Q2.1.3, Q2.1.4, Q2.1.2, Installation | |
| 3377 @unnumberedsubsec Q2.1.3: Can I install the packages automatically? | |
| 3378 | |
| 3379 XEmacs comes with some tools to make the periodic updating and | |
| 3380 installing easier. It will notice if new packages or versions are | |
| 3381 available and will fetch them from the FTP site. | |
| 3382 | |
| 3383 Unfortunately this requires that a few packages are already in place. | |
| 3384 You will have to install them by hand as above or use a SUMO tarball. | |
| 3385 This requirement will hopefully go away in the future. The packages | |
| 3386 you need are: | |
| 3387 | |
| 3388 @example | |
| 3389 efs - To fetch the files from the FTP site or mirrors. | |
| 3390 xemacs-base - Needed by efs. | |
| 3391 @end example | |
| 3392 | |
| 3393 and optionally: | |
| 3394 | |
| 3395 @example | |
| 3396 mailcrypt - For PGP verification of the package-index file. | |
| 3397 @end example | |
| 3398 | |
| 3399 After installing these by hand, fire up XEmacs and follow these | |
| 3400 steps. | |
| 3401 | |
| 3402 @enumerate | |
| 3403 @item | |
| 3404 Choose a download site. | |
| 3405 @itemize @bullet | |
| 3406 @item | |
| 3407 via menu: Tools -> Packages -> Set Download Site | |
| 3408 @item | |
| 3409 via keyb: M-x customize-variable RET package-get-remote RET | |
| 3410 (put in the details of remote host and directory) | |
| 3411 @end itemize | |
| 3412 | |
| 3413 If the package tarballs _AND_ the package-index file are in a | |
| 3414 local directory, you can: M-x pui-set-local-package-get-directory RET | |
| 3415 | |
| 3416 @item | |
| 3417 Obtain a list of packages and display the list in a buffer named | |
| 3418 "*Packages*". | |
| 3419 @itemize @bullet | |
| 3420 @item | |
| 3421 menu: Tools -> Packages -> List & Install | |
| 3422 @item | |
| 3423 keyb: M-x pui-list-packages RET | |
| 3424 @end itemize | |
| 3425 | |
| 3426 XEmacs will now connect to the remote site and download the | |
| 3427 latest package-index file. | |
| 3428 | |
| 3429 The resulting buffer, "*Packages*" has brief instructions at the | |
| 3430 end of the buffer. | |
| 3431 | |
| 3432 @item | |
| 3433 Choose the packages you wish to install. | |
| 3434 @itemize @bullet | |
| 3435 @item | |
| 3436 mouse: Click button 2 on the package name. | |
| 3437 @item | |
| 3438 keyb: RET on the package name | |
| 3439 @end itemize | |
| 3440 | |
| 3441 @item | |
| 3442 Make sure you have everything you need. | |
| 3443 @itemize @bullet | |
| 3444 @item | |
| 3445 menu: Packages -> Add Required | |
| 3446 @item | |
| 3447 keyb: r | |
| 3448 @end itemize | |
| 3449 | |
| 3450 XEmacs will now search for packages that are required by the | |
| 3451 ones that you have chosen to install and offer to select | |
| 3452 those packages also. | |
| 3453 | |
| 3454 For novices and gurus alike, this step can save your bacon. | |
| 3455 It's easy to forget to install a critical package. | |
| 3456 | |
| 3457 @item | |
| 3458 Download and install the packages. | |
| 3459 @itemize @bullet | |
| 3460 @item | |
| 3461 menu: Packages -> Install/Remove Selected | |
| 3462 @item | |
| 3463 keyb: x | |
| 3464 @end itemize | |
| 3465 @end enumerate | |
| 3466 | |
| 3467 @node Q2.1.4, Q2.1.5, Q2.1.3, Installation | |
| 3468 @unnumberedsubsec Q2.1.4: Can I upgrade or remove packages? | |
| 3469 | |
| 3470 As the exact files and their locations contained in a package may | |
| 3471 change it is recommended to remove a package first before installing a | |
| 4311 | 3472 new version. In order to facilitate removal each package contains a |
| 3473 pkginfo/MANIFEST.pkgname file which lists all the files belonging to | |
| 3474 the package. M-x package-admin-delete-binary-package RET can be used | |
| 3475 to remove a package using this file. | |
| 2559 | 3476 |
| 3477 Note that the interactive package tools included with XEmacs already do | |
| 3478 this for you. | |
| 3479 | |
| 3480 @node Q2.1.5, Q2.1.6, Q2.1.4, Installation | |
| 3481 @unnumberedsubsec Q2.1.5: Which packages to install? | |
| 3482 | |
| 3483 Unless you are an advanced user, just install everything. | |
| 3484 | |
| 3485 If you really want to install only what's absolutely needed, a good | |
| 3486 minimal set of packages for XEmacs-latin1 would be | |
| 3487 | |
| 3488 @example | |
| 3489 xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs, | |
| 3490 edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes, | |
| 3491 text-modes, time, mailcrypt | |
| 3492 @end example | |
| 3493 | |
| 3494 If you are using the XEmacs package tools, don't forget to do: | |
| 3495 | |
| 3496 @example | |
| 3497 Packages -> Add Required | |
| 3498 @end example | |
| 3499 | |
| 3500 To make sure you have everything that the packages you have chosen to | |
| 3501 install need. | |
| 3502 | |
| 3503 @xref{Q1.7.2}, for a description of the various packages. | |
| 3504 | |
| 3505 @node Q2.1.6, Q2.1.7, Q2.1.5, Installation | |
| 3506 @unnumberedsubsec Q2.1.6: Can you describe the package location process in more detail? | |
| 3507 | |
| 3508 On startup XEmacs looks for packages in so-called package hierarchies. | |
| 3509 Normally, there are three system wide hierarchies, like this: | |
| 3510 | |
| 3511 @example | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3512 $prefix/sahre/xemacs/xemacs-packages/ |
| 2559 | 3513 Normal packages go here. |
| 3514 | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3515 $prefix/share/xemacs/mule-packages/ |
| 2559 | 3516 Mule packages go here and are only searched by MULE-enabled XEmacsen. |
| 3517 | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3518 $prefix/share/xemacs/site-packages/ |
| 2559 | 3519 Local and 3rd party packages go here. |
| 3520 @end example | |
| 3521 | |
| 3522 This is what you get when you untar the SUMO tarballs under | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3523 @file{$prefix/share/xemacs}. |
| 2559 | 3524 |
| 3525 @file{$prefix} is specified using the @samp{--prefix} parameter to | |
| 3526 @file{configure}, and defaults to @file{usr/local}. | |
| 3527 | |
| 3528 If the package path is not explicitly specified, XEmacs looks for the | |
| 3529 package directory @file{xemacs-packages} (and @file{mule-packages} and | |
| 3530 @file{site-packages}) first under @samp{~/.xemacs}, then for a sister | |
| 3531 directory @file{lib/xemacs-VERSION} of the directory in which the | |
| 3532 XEmacs executable is located, then for a sister directory | |
| 3533 @file{lib/xemacs}. The XEmacs executable (under Unix at least) is | |
| 3534 installed by default in @file{/usr/local/bin}; this explains why | |
| 3535 XEmacs in its default installation will find packages that you put | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3536 under @file{/usr/local/share/xemacs}. |
| 2559 | 3537 |
| 3538 You can specify where exactly XEmacs looks for packages by using the | |
| 3179 | 3539 @samp{--with-user-packages} (an alias for @samp{--with-early-packages}) |
| 3540 or @samp{--with-system-packages} (an alias for | |
| 3541 @samp{--with-late-packages}) or @samp{--with-legacy-packages} | |
| 3542 (an alias for @samp{--with-last-packages}) | |
| 3543 parameters to @file{configure} (or the equivalent settings in | |
| 3544 @file{config.inc}, under Windows), or setting the | |
| 3545 @samp{EMACSEARLYPACKAGES}, @samp{EMACSLATEPACKAGES}, and | |
| 3546 @samp{EMACSLASTPACKAGES} environment variables (which have the same | |
| 3547 format as the configure options). @xref{Q2.1.1}. | |
| 2559 | 3548 |
| 3549 See @file{configure.usage} for more info about the format of these | |
| 3550 @file{configure} parameters. | |
| 3551 | |
| 3552 In addition to the system wide packages, each user can have his own | |
| 3553 packages installed under @file{~/.xemacs/}. If you want to install | |
| 3554 packages there using the interactive tools, you need to set | |
| 3555 @code{package-get-install-to-user-init-directory} to @code{t}. | |
| 3556 | |
| 3557 The site-packages hierarchy replaces the old @file{site-lisp} | |
| 3558 directory. XEmacs no longer looks into a @file{site-lisp} directly by | |
| 3559 default. A good place to put @file{site-start.el} would be in | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
3560 @file{$prefix/share/xemacs/site-packages/lisp/}. |
| 2559 | 3561 |
| 3562 @node Q2.1.7, Q2.2.1, Q2.1.6, Installation | |
| 3563 @unnumberedsubsec Q2.1.7: EFS fails with "500 AUTH not understood" (NEW) | |
| 2417 | 3564 |
| 3565 A typical error: FTP Error: USER request failed; 500 AUTH not understood. | |
| 3566 | |
| 4311 | 3567 Thanks to Giacomo Boffi @email{giacomo.boffi@@polimi.it} who recommends |
| 2417 | 3568 on comp.emacs.xemacs: |
| 3569 | |
| 3570 tell your ftp client to not attempt AUTH authentication (or do not | |
| 3571 use FTP servers that don't understand AUTH) | |
| 3572 | |
| 3573 and notes that you need to add an element (often "-u") to | |
| 3574 `efs-ftp-program-args'. Use M-x customize-variable, and verify the | |
| 3575 needed flag with `man ftp' or other local documentation. | |
| 3576 | |
| 2559 | 3577 @unnumberedsec 2.2: Unix/Mac OS X Installation (Also Relevant to Cygwin, MinGW) |
| 3578 | |
| 3579 @node Q2.2.1, Q2.2.2, Q2.1.7, Installation | |
| 3580 @unnumberedsubsec Q2.2.1: Libraries in non-standard locations | |
| 428 | 3581 |
| 2459 | 3582 If your libraries are in a non-standard location, you can specify the location |
| 3018 | 3583 using the following flags to @file{configure}. Under 21.4 or earlier: |
| 2459 | 3584 |
| 3585 @example | |
| 3586 --site-libraries=WHATEVER | |
| 3587 --site-includes=WHATEVER | |
| 3588 @end example | |
| 3589 | |
| 3018 | 3590 Under 21.5 or later: |
| 3591 | |
| 3592 @example | |
| 3593 --with-site-libraries=WHATEVER | |
| 3594 --with-site-includes=WHATEVER | |
| 3595 @end example | |
| 3596 | |
| 2459 | 3597 If you have multiple paths to specify, use the following syntax: |
| 428 | 3598 |
| 3599 @example | |
| 3600 --site-libraries='/path/one /path/two /path/etc' | |
| 3601 @end example | |
| 3602 | |
| 3018 | 3603 If the libraries and headers reside in the directories @samp{lib} and |
| 3604 @samp{include} of a common root (say @samp{/sw}) then both can be | |
| 3605 specified with a single option: | |
| 3606 | |
| 3607 @example | |
| 3608 --site-prefixes=WHATEVER | |
| 3609 @end example | |
| 3610 | |
| 3611 or for 21.5: | |
| 3612 | |
| 3613 @example | |
| 3614 --with-site-prefixes=WHATEVER | |
| 3615 @end example | |
| 3616 | |
| 3404 | 3617 @node Q2.2.2, Q2.2.3, Q2.2.1, Installation |
| 2559 | 3618 @unnumberedsubsec Q2.2.2: Why can't I strip XEmacs? |
| 428 | 3619 |
| 3620 @email{cognot@@fronsac.ensg.u-nancy.fr, Richard Cognot} writes: | |
| 3621 | |
| 3622 @quotation | |
| 3623 Because of the way XEmacs (and every other Emacsen, AFAIK) is built. The | |
| 3624 link gives you a bare-boned emacs (called temacs). temacs is then run, | |
| 3625 preloading some of the lisp files. The result is then dumped into a new | |
| 3626 executable, named xemacs, which will contain all of the preloaded lisp | |
| 3627 functions and data. | |
| 3628 | |
| 3629 Now, during the dump itself, the executable (code+data+symbols) is | |
| 3630 written on disk using a special unexec() function. This function is | |
| 3631 obviously heavily system dependent. And on some systems, it leads to an | |
| 3632 executable which, although valid, cannot be stripped without damage. If | |
| 3633 memory serves, this is especially the case for AIX binaries. On other | |
| 462 | 3634 architectures it might work OK. |
| 428 | 3635 |
| 3636 The Right Way to strip the emacs binary is to strip temacs prior to | |
| 3637 dumping xemacs. This will always work, although you can do that only if | |
| 3638 you install from sources (as temacs is @file{not} part of the binary | |
| 3639 kits). | |
| 3640 @end quotation | |
| 3641 | |
| 3642 @email{nat@@nataa.fr.eu.org, Nat Makarevitch} writes: | |
| 3643 | |
| 3644 @quotation | |
| 3645 Here is the trick: | |
| 3646 | |
| 3647 @enumerate | |
| 3648 @item | |
| 3649 [ ./configure; make ] | |
| 3650 | |
| 3651 @item | |
| 3652 rm src/xemacs | |
| 3653 | |
| 3654 @item | |
| 3655 strip src/temacs | |
| 3656 | |
| 3657 @item | |
| 3658 make | |
| 3659 | |
| 3660 @item | |
| 3661 cp src/xemacs /usr/local/bin/xemacs | |
| 3662 | |
| 3663 @item | |
| 3664 cp lib-src/DOC-19.16-XEmacs | |
| 3665 @iftex | |
| 3666 \ @* | |
| 3667 @end iftex | |
| 3668 /usr/local/lib/xemacs-19.16/i586-unknown-linuxaout | |
| 3669 @end enumerate | |
| 3670 @end quotation | |
| 3671 | |
| 3404 | 3672 @node Q2.2.3, Q2.3.1, Q2.2.2, Installation |
| 3673 @unnumberedsubsec Q2.2.3: X11/bitmaps/gray (or other X11-related file) not found. | |
| 3674 | |
| 3675 The X11R6 distribution was monolithic, but the X11R7 distribution is | |
| 3676 much more modular. Many OS distributions omit these bitmaps (assuming | |
| 3677 nobody uses them, evidently). Your OS distribution should have a | |
| 3678 developer's package containing these files, probably with a name | |
| 3679 containing the string "bitmap". Known package names (you may need to | |
| 3680 add an extension such as .deb or .rpm) include x11/xbitmaps (Ubuntu) | |
| 3681 and xorg-x11-xbitmaps (Fedora Core 5). | |
| 3682 | |
| 2559 | 3683 @unnumberedsec 2.3: Windows Installation (Windows, Cygwin, MinGW) |
| 3684 | |
| 3404 | 3685 @node Q2.3.1, Q2.3.2, Q2.2.3, Installation |
| 2559 | 3686 @unnumberedsubsec Q2.3.1: What exactly are all the different ways to build XEmacs under Windows? |
| 2417 | 3687 |
| 3688 XEmacs can be built in several ways in the MS Windows environment. | |
| 3689 | |
| 3690 The standard way is what we call the "native" port. It uses the Win32 | |
| 3691 API and has no connection with X whatsoever -- it does not require X | |
| 3692 libraries to build, nor does it require an X server to run. The native | |
| 3693 port is the most reliable version and provides the best graphical | |
| 3694 support. Almost all development is geared towards this version, and | |
| 3695 there is little reason not to use it. | |
| 3696 | |
| 3697 The second way to build is the Cygwin port. It takes advantage of | |
| 2537 | 3698 Cygnus emulation library under Win32. @xref{Q1.2.5, What are Cygwin |
| 2417 | 3699 and MinGW, and do I need them to run XEmacs?}, for more information. |
| 3700 | |
| 3701 A third way is the MinGW port. It uses the Cygwin environment to | |
| 2537 | 3702 build but does not require it at runtime. @xref{Q1.2.5, What are |
| 2417 | 3703 Cygwin and MinGW, and do I need them to run XEmacs?}, for more |
| 3704 information. | |
| 3705 | |
| 3706 Finally, you might also be able to build the non-Cygwin, non-MinGW "X" | |
| 3707 port. This was actually the first version of XEmacs that ran under MS | |
| 3708 Windows, and although the code is still in XEmacs, it's essentially | |
| 3709 orphaned and it's unlikely it will compile without a lot of work. If | |
| 3710 you want an MS Windows versin of XEmacs that supports X, use the Cygwin | |
| 3711 version. (The X support there is actively maintained, so that Windows | |
| 3712 developers can test the X support in XEmacs.) | |
| 3713 | |
| 2559 | 3714 @node Q2.3.2, Q2.3.3, Q2.3.1, Installation |
| 3715 @unnumberedsubsec Q2.3.2: What compiler/libraries do I need to compile XEmacs? | |
| 2417 | 3716 |
| 3717 You need Visual C++ 4.2, 5.0, or 6.0 for the native version. (We have | |
| 3718 some beta testers currently trying to compile with VC.NET, aka version | |
| 3719 7.0, but we can't yet report complete success.) For the Cygwin and | |
| 3720 MinGW versions, you need the Cygwin environment, which comes with GCC, | |
| 2537 | 3721 the compiler used for those versions. @xref{Q1.2.5, What are Cygwin |
| 2417 | 3722 and MinGW, and do I need them to run XEmacs?}, for more information on |
| 3723 Cygwin and MinGW. | |
| 3724 | |
| 2559 | 3725 @node Q2.3.3, Q2.3.4, Q2.3.2, Installation |
| 3726 @unnumberedsubsec Q2.3.3: How do I compile the native port? | |
| 2417 | 3727 |
| 3728 Please read the file @file{nt/README} in the XEmacs distribution, which | |
| 3729 contains the full description. | |
| 3730 | |
| 2559 | 3731 @node Q2.3.4, Q2.3.5, Q2.3.3, Installation |
| 3732 @unnumberedsubsec Q2.3.4: What do I need for Cygwin? | |
| 2417 | 3733 |
| 3734 You can find the Cygwin tools and compiler at: | |
| 3735 | |
| 3736 @uref{http://www.cygwin.com/} | |
| 3737 | |
| 3738 Click on the @samp{Install or update now!} link, which will download a | |
| 3739 file @file{setup.exe}, which you can use to download everything | |
| 3740 else. (You will need to pick a mirror site; @samp{mirrors.rcn.net} is | |
| 3741 probably the best.) You should go ahead and install everything -- | |
| 3742 you'll get various ancillary libraries that XEmacs needs or likes, | |
| 3743 e.g. XPM, PNG, JPEG, TIFF, etc. You can also get X Windows here, if you | |
| 3744 want to compile under X. | |
| 3745 | |
| 3746 If you want to compile without X, you will need the @file{xpm-nox} | |
| 3747 library, which must be specifically selected in the Cygwin netinstaller; | |
| 3748 it is not selected by default. The package has had various names. | |
| 3749 Currently it is called @file{cygXpm-noX4.dll}. | |
| 3750 | |
| 2559 | 3751 @node Q2.3.5, Q2.3.6, Q2.3.4, Installation |
| 3752 @unnumberedsubsec Q2.3.5: How do I compile under Cygwin? | |
| 2417 | 3753 |
| 3754 Similar as on Unix; use the usual `configure' and `make' process. | |
| 3755 Some problems to watch out for: | |
| 3756 | |
| 3757 @itemize @bullet | |
| 3758 @item | |
| 3759 make sure HOME is set. This controls where you | |
| 3760 @file{init.el} file comes from; | |
| 3761 | |
| 3762 @item | |
| 3763 @samp{CYGWIN} needs to be set to @samp{tty} for process support to work; | |
| 3764 | |
| 3765 @item | |
| 3766 picking up some other grep or other UNIX-like tools can kill configure; | |
| 3767 | |
| 3768 @item | |
| 3769 static heap too small, adjust @file{src/sheap-adjust.h} to a more positive | |
| 3770 number; | |
| 3771 | |
| 3772 @item | |
| 3773 (Unconfirmed) The Cygwin version doesn't understand | |
| 3774 @file{//machine/path} type paths so you will need to manually mount a | |
| 3775 directory of this form under a unix style directory for a build to work | |
| 3776 on the directory; | |
| 3777 | |
| 3778 @item | |
| 3779 If you're building @strong{WITHOUT} X11, don't forget to change symlinks | |
| 3780 @file{/usr/lib/libXpm.a} and @file{/usr/lib/libXpm.dll.a} to point to | |
| 3781 the non-X versions of these libraries. By default they point to the X | |
| 3782 versions. So: | |
| 3783 | |
| 3784 @example | |
| 3785 /usr/lib/libXpm.a -> /usr/lib/libXpm-noX.a | |
| 3786 /usr/lib/libXpm.dll.a -> /usr/lib/libXpm-noX.dll.a | |
| 3787 @end example | |
| 3788 | |
| 3789 (This advice may now be obsolete because of the availability of the | |
| 3790 cygXpm-noX4.dll package from Cygwin. Send confirmation to | |
| 3791 @email{faq@@xemacs.org}.) | |
| 3792 | |
| 3793 @item | |
| 3794 Other problems are listed in the @file{PROBLEMS} file, in the top-level | |
| 3795 directory of the XEmacs sources. | |
| 3796 | |
| 3797 @end itemize | |
| 3798 | |
| 3799 | |
| 2559 | 3800 @node Q2.3.6, Q2.3.7, Q2.3.5, Installation |
| 3801 @unnumberedsubsec Q2.3.6: How do I compile using MinGW (aka @samp{the -mno-cygwin flag to gcc})? | |
| 2417 | 3802 |
| 3803 Similar to the method for Unix. Things to remember: | |
| 3804 | |
| 3805 @itemize @bullet | |
| 3806 @item | |
| 3807 Specify the target host on the command line for @file{./configure}, e.g. | |
| 3808 @samp{./configure i586-pc-mingw32}. | |
| 3809 | |
| 3810 @item | |
| 3811 Be sure that your build directory is mounted such that it has the | |
| 3812 same path either as a cygwin path (@file{/build/xemacs}) or as a Windows | |
| 3813 path (@file{c:\build\xemacs}). | |
| 3814 | |
| 3815 @item | |
| 3816 Build @samp{gcc -mno-cygwin} versions of the extra libs, i.e. @file{libpng}, | |
| 3817 @file{compface}, etc. | |
| 3818 | |
| 3819 @item | |
| 3820 Specify the target location of the extra libs on the command line | |
| 3018 | 3821 to @file{configure}, e.g.for 21.4 or earlier |
| 3822 @samp{./configure --site-prefixes=/build/libs i586-pc-mingw32} and for | |
| 3823 21.5 or later | |
| 3824 @samp{./configure --with-site-prefixes=/build/libs i586-pc-mingw32}. | |
| 2417 | 3825 @end itemize |
| 3826 | |
| 2559 | 3827 @node Q2.3.7, Q2.3.8, Q2.3.6, Installation |
| 3828 @unnumberedsubsec Q2.3.7: How do I compile with X support? | |
| 2417 | 3829 |
| 3830 To compile under Cygwin, all you need to do is install XFree86, which | |
| 3831 is available as part of the standard Cygwin installation. | |
| 3832 @uref{http://www.cygwin.com/}. Once installed, @file{configure} | |
| 3833 should automatically find the X libraries and compile with X support. | |
| 3834 | |
| 3835 As noted above, the non-Cygwin X support is basically orphaned, and | |
| 3836 probably won't work. But if it want to try, it's described in | |
| 3837 @file{nt/README} in some detail. Basically, you need to get X11 | |
| 2459 | 3838 libraries from @uref{http://ftp.x.org}, and compile them. If the |
| 2417 | 3839 precompiled versions are available somewhere, we don't know of it. |
| 3840 | |
| 2559 | 3841 @node Q2.3.8, Q2.4.1, Q2.3.7, Installation |
| 3842 @unnumberedsubsec Q2.3.8: Cygwin XEmacs won't start -- cygXpm-noX4.dll was not found (NEW) | |
| 1058 | 3843 |
| 3844 The Cygwin binary distributed with the netinstaller uses an external DLL | |
| 3845 to handle XPM images (such as toolbar buttons). You may get an error like | |
| 3846 | |
| 2559 | 3847 @example |
| 3848 This application has failed to start because cygXpm-noX4.dll was not found. | |
| 3849 Re-installing the application may fix this problem. | |
| 3850 @end example | |
| 1058 | 3851 |
| 3852 Andy Piper <andy@@xemacs.org> sez: | |
| 3853 | |
| 2559 | 3854 @example |
| 3855 cygXpm-noX4 is part of the cygwin distribution under libraries or | |
| 3856 graphics, but is not installed by default. You need to run the | |
| 3857 cygwin setup again and select this package. | |
| 3858 @end example | |
| 1058 | 3859 |
| 3860 Ie, reinstalling XEmacs won't help because it is not part of the XEmacs | |
| 3861 distribution. | |
| 3862 | |
| 2559 | 3863 @unnumberedsec 2.4: General Troubleshooting |
| 3864 | |
| 3865 @node Q2.4.1, Q2.4.2, Q2.3.8, Installation | |
| 3866 @unnumberedsubsec Q2.4.1: How do I deal with bugs or with problems building, installing, or running? | |
| 3867 | |
| 3868 The file @file{PROBLEMS} contains information on many common problems that | |
| 3869 occur in building, installing and running XEmacs. | |
| 3870 | |
| 3871 Reports of bugs in XEmacs should be sent to | |
| 3872 @email{xemacs-beta@@xemacs.org}. You can also post to the newsgroup | |
| 3873 comp.emacs.xemacs (or equivalentlt, send to the mailing list | |
| 3874 @email{xemacs@@xemacs.org}), but it is less likely that the developers | |
| 3875 will see it in a timely fashion. @xref{Bugs,,, xemacs, the XEmacs | |
| 3876 User's Manual}, for more information on how to report bugs. | |
| 3877 @xref{Q1.4.2}, for more information on mailing lists relating to | |
| 3878 XEmacs. | |
| 3879 | |
| 3880 There are three ways to read the Bugs section. | |
| 3881 | |
| 3882 @enumerate | |
| 3883 @item | |
| 3884 In a printed copy of the XEmacs manual. | |
| 3885 | |
| 3886 @item | |
| 3887 With Info. First, start XEmacs. From the menu, select | |
| 3888 @samp{Help->Info (Online Docs)->Info Contents} to enter Info, then | |
| 3889 click on @samp{XEmacs}, then on @samp{Bugs}. Or, use the keyboard: do | |
| 3890 @kbd{C-h i} to enter Info, then @kbd{m XEmacs RET} to get to the Emacs | |
| 3891 manual, then @kbd{m Bugs RET} to get to the section on bugs. Or use | |
| 3892 standalone Info in a like manner. (Standalone Info is part of the | |
| 3893 Texinfo distribution, not part of the XEmacs distribution.) | |
| 3894 | |
| 3895 @item | |
| 3896 By hand. Do | |
| 3897 @example | |
| 3898 cat info/xemacs* | more "+/^File: xemacs.info, Node: Bugs," | |
| 3899 @end example | |
| 3900 @end enumerate | |
| 3901 | |
| 3902 @node Q2.4.2, Q2.4.3, Q2.4.1, Installation | |
| 3903 @unnumberedsubsec Q2.4.2: Help! XEmacs just crashed on me! | |
| 428 | 3904 |
| 3905 First of all, don't panic. Whenever XEmacs crashes, it tries extremely | |
| 3906 hard to auto-save all of your files before dying. (The main time that | |
| 3907 this will not happen is if the machine physically lost power or if you | |
| 3908 killed the XEmacs process using @code{kill -9}). The next time you try | |
| 3909 to edit those files, you will be informed that a more recent auto-save | |
| 3910 file exists. You can use @kbd{M-x recover-file} to retrieve the | |
| 3911 auto-saved version of the file. | |
| 3912 | |
| 462 | 3913 You can use the command @kbd{M-x recover-session} after a crash to pick |
| 3914 up where you left off. | |
| 428 | 3915 |
| 3916 Now, XEmacs is not perfect, and there may occasionally be times, or | |
| 3917 particular sequences of actions, that cause it to crash. If you can | |
| 3918 come up with a reproducible way of doing this (or even if you have a | |
| 3919 pretty good memory of exactly what you were doing at the time), the | |
| 2417 | 3920 maintainers would be very interested in knowing about it. The best |
| 3921 way to report a bug is using @kbd{M-x report-emacs-bug} (or by | |
| 3922 selecting @samp{Send Bug Report...} from the Help menu). If that | |
| 3923 won't work (e.g. you can't get XEmacs working at all), send ordinary | |
| 3924 mail to @email{xemacs-beta@@xemacs.org}. @emph{MAKE SURE} to include | |
| 3925 the output from the crash, especially including the Lisp backtrace, as | |
| 3926 well as the XEmacs configuration from @kbd{M-x describe-installation} | |
| 3927 (or equivalently, the file @file{Installation} in the top of the build | |
| 3928 tree). Note that the developers do @emph{not} usually follow | |
| 3929 @samp{comp.emacs.xemacs} on a regular basis; thus, this is better for | |
| 3930 general questions about XEmacs than bug reports. | |
| 428 | 3931 |
| 1183 | 3932 If at all possible, include a C stack backtrace of the core dump that |
| 2417 | 3933 was produced. This shows where exactly things went wrong, and makes |
| 3934 it much easier to diagnose problems. To do this under Unix and Mac OS | |
| 3935 X, you need to locate the core file (it's called @file{core}, and is | |
| 3936 usually sitting in the directory that you started XEmacs from, or your | |
| 3937 home directory if that other directory was not writable). Then, go to | |
| 3938 that directory and execute a command like: | |
| 428 | 3939 |
| 3940 @example | |
| 3941 gdb `which xemacs` core | |
| 3942 @end example | |
| 3943 | |
| 3944 and then issue the command @samp{where} to get the stack backtrace. You | |
| 3945 might have to use @code{dbx} or some similar debugger in place of | |
| 3946 @code{gdb}. If you don't have any such debugger available, complain to | |
| 3947 your system administrator. | |
| 3948 | |
| 2417 | 3949 It's possible that a core file didn't get produced or the stack trace |
| 3950 from gdb is garbage, in which case you're out of luck unless you can | |
| 3951 reproduce the bug. A nonexistent core file can happen in some | |
| 3952 circumstances on some operating systems, depending on what exactly | |
| 3953 triggered the crash. It's also possible, however, that your limits | |
| 3954 are set to turn them off. You may be able to reenable them using a | |
| 3955 command like @samp{unlimit coredumpsize} or @samp{ulimit -c}. (To find | |
| 3956 out how your limits are set, use the command @samp{limit}.) However, if | |
| 3957 you didn't explicitly set your limits this way, go complain to your | |
| 3958 system administrator and tell him not to disable core files by | |
| 3959 default. | |
| 3960 | |
| 3961 A garbaged stack trace can happen for various reasons. Some versions | |
| 3962 of gdb are broken on certain operating systems and aren't able to read | |
| 3963 the core file. It's also possible that the stack got overwritten | |
| 3964 during the crash. A very simple reason, however, is that your version | |
| 3965 of XEmacs was compiled without debugging information or had the | |
| 3966 debugging information stripped. A compilation with optimization can | |
| 3967 also result in partly or completely garbaged stack trace. In such | |
| 3968 cases, you will need to recompile XEmacs with debugging information | |
| 2559 | 3969 and without optimization; @xref{Q2.4.4, How to debug an XEmacs problem |
| 2417 | 3970 with a debugger}. Note also that core files currently don't work at |
| 3971 all under Cygwin, and the only way to get a backtrace is to run XEmacs | |
| 3972 from gdb. | |
| 3973 | |
| 3974 If you cannot get a backtrace from the core dump, but can reproduce | |
| 3975 the problem, try running XEmacs under gdb. The goal is to get clean C | |
| 3976 and Lisp backtraces and submit a bug report including full | |
| 3977 configuration information as described above, as this will greatly | |
| 3978 assist in the process of tracking down the bug. However, even partial | |
| 3979 information is better than none. The process of getting backtraces | |
| 2559 | 3980 from gdb is described in detail in @ref{Q2.4.4, How to debug an XEmacs |
| 2417 | 3981 problem with a debugger}. |
| 428 | 3982 |
| 1183 | 3983 If you're under Microsoft Windows, you're out of luck unless you happen |
| 3984 to have a debugging aid installed on your system, for example Visual | |
| 3985 C++. In this case, the crash will result in a message giving you the | |
| 3986 option to enter a debugger (for example, by pressing @samp{Cancel}). Do | |
| 3987 this and locate the stack-trace window. (If your XEmacs was built | |
| 3988 without debugging information, the stack trace may not be very useful.) | |
| 3989 | |
| 428 | 3990 When making a problem report make sure that: |
| 3991 | |
| 3992 @enumerate | |
| 3993 @item | |
| 3994 Report @strong{all} of the information output by XEmacs during the | |
| 3995 crash. | |
| 3996 | |
| 3997 @item | |
| 2417 | 3998 You mention what O/S and Hardware you are running XEmacs on. |
| 428 | 3999 |
| 4000 @item | |
| 4001 What version of XEmacs you are running. | |
| 4002 | |
| 4003 @item | |
| 4004 What build options you are using. | |
| 4005 | |
| 4006 @item | |
| 2417 | 4007 If the problem is related to graphics and you are running Unix or Mac |
| 4008 OS X, we will also need to know what version of the X Window System | |
| 4009 you are running, and what window manager you are using. | |
| 1183 | 4010 |
| 4011 @item | |
| 4012 If the problem happened on a TTY, please include the terminal type. | |
| 2417 | 4013 |
| 4014 @item | |
| 4015 Try very hard to get both C and Lisp backtraces, as described above. | |
| 428 | 4016 @end enumerate |
| 4017 | |
| 1135 | 4018 Much of the information above is automatically generated by @kbd{M-x |
| 4019 report-emacs-bug}. Even more, and often useful, information can be | |
| 4020 generated by redirecting the output of @code{make} and @code{make check} | |
| 4021 to a file (@file{beta.err} is the default used by @code{build-report}), | |
| 4022 and executing @kbd{M-x build-report}. | |
| 4023 | |
| 2417 | 4024 |
| 2559 | 4025 @node Q2.4.3, Q2.4.4, Q2.4.2, Installation |
| 4026 @unnumberedsubsec Q2.4.3: XEmacs crashes and I compiled it myself. | |
| 2417 | 4027 |
| 4028 There have been a variety of reports of crashes due to compilers with | |
| 4029 buggy optimizers. If you are compiling with optimization, consider | |
| 2559 | 4030 turning it off (@pxref{Q2.4.4, How to debug an XEmacs problem with a |
| 2417 | 4031 debugger}) and recompiling. |
| 4032 | |
| 4033 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in | |
| 4034 the top-level source directory) to read what it says about your | |
| 4035 platform. | |
| 4036 | |
|
5384
3889ef128488
Fix misspelled words, and some grammar, across the entire source tree.
Jerry James <james@xemacs.org>
parents:
5028
diff
changeset
|
4037 If you compiled XEmacs 21.4 or earlier using @samp{--use-union-type}, or |
| 3018 | 4038 21.5 or later using @samp{--enable-union-type} (or in either case used |
| 4039 the option @samp{USE_UNION_TYPE} in @file{config.inc} under Windows), | |
| 4040 try recompiling again without it. The union type has been known to | |
| 4041 trigger compiler errors in a number of cases. | |
| 2417 | 4042 |
| 2559 | 4043 @node Q2.4.4, Q2.4.5, Q2.4.3, Installation |
| 4044 @unnumberedsubsec Q2.4.4: How to debug an XEmacs problem with a debugger | |
| 428 | 4045 |
| 4046 If XEmacs does crash on you, one of the most productive things you can | |
| 4047 do to help get the bug fixed is to poke around a bit with the debugger. | |
| 4048 Here are some hints: | |
| 4049 | |
| 4050 @itemize @bullet | |
| 4051 @item | |
| 4052 First of all, if the crash is at all reproducible, consider very | |
| 563 | 4053 strongly recompiling your XEmacs with debugging symbols and with no |
| 4054 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} -- | |
| 4055 that's an "oh" followed by a zero), and with the configure options | |
| 3018 | 4056 @samp{--debug=yes} and @samp{--error-checking=all} |
| 4057 (@samp{--enable-debug=yes} and @samp{--enable-error-checking=all} on | |
| 4058 XEmacs 21.5 or later). This will make your XEmacs run somewhat slower, | |
| 4059 but you are a lot more likely to catch the problem earlier (closer to | |
| 4060 its source). It makes it a lot easier to determine what's going on with | |
| 4061 a debugger. The way to control the compiler flags is with the | |
| 4062 configuration option @samp{--cflags} (@samp{--with-cflags} in 21.5). If | |
| 4063 you have a recent version of 21.5, you should use | |
| 2417 | 4064 @samp{--without-optimization} in preference to directly setting |
| 4065 @samp{--cflags}. | |
| 1258 | 4066 |
| 4067 @item | |
| 4068 If it's not a true crash (@emph{i.e.}, XEmacs is hung, or a zombie | |
| 4069 process), or it's inconvenient to run XEmacs again because XEmacs is | |
| 4070 already running or is running in batch mode as part of a bunch of | |
| 4071 scripts, you may be able to attach to the existing process with your | |
| 2417 | 4072 debugger. Under Unix and Mac OS X, the typical way to do this is to |
| 4073 first use some variant of the @samp{ps} command to figure out the | |
| 4074 process ID of XEmacs, for example @samp{ps -auxww | grep xemacs} under | |
| 4075 a BSD variant, @samp{ps -elf | grep xemacs} under Linux or System V, | |
| 4076 or @samp{ps -aW | grep xemacs} under Cygwin. Then run | |
| 4077 | |
| 4078 @example | |
| 4079 gdb /path/to/xemacs/xemacs #### | |
| 4080 @end example | |
| 4081 | |
| 4082 Where @code{####} is the process id of your XEmacs. (If you're not | |
| 4083 sure, try using @samp{which xemacs}.) When gdb attaches, the xemacs | |
| 4084 will stop and you can type @samp{where} in gdb to get a stack trace as | |
| 4085 usual. To get things moving again, you can just type @samp{quit} in | |
| 4086 gdb. It'll tell you the program is running and ask if you want to | |
| 4087 quit anyways. Say @samp{y} and it'll quit and have your emacs | |
| 4088 continue from where it was at. | |
| 4089 | |
| 4090 If you're running another debugger, a similar method may work, or you | |
| 4091 may have to run the debugger first and then use the @code{attach} | |
| 4092 command or something similar. | |
| 4093 | |
| 4094 Under Microsoft Windows, use the menu item @samp{Build->Start | |
| 4095 Debug->Attach to Process...} and select the XEmacs process from the list | |
| 4096 given. | |
| 1258 | 4097 |
| 4098 @item | |
| 4099 If you're able to run XEmacs under a debugger and reproduce the crash, | |
| 4100 here are some things you can do: | |
| 428 | 4101 |
| 4102 @item | |
| 4103 If XEmacs is hitting an assertion failure, put a breakpoint on | |
| 4104 @code{assert_failed()}. | |
| 4105 | |
| 4106 @item | |
| 4107 If XEmacs is hitting some weird Lisp error that's causing it to crash | |
| 4108 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is | |
| 2417 | 4109 declared static in @file{eval.c}. |
| 428 | 4110 |
| 4111 @item | |
| 563 | 4112 If XEmacs is outputting lots of X errors, put a breakpoint on |
| 2417 | 4113 @code{x_error_handler()}; that will tell you which call is causing |
| 4114 them. Note that the result may not be very useful by default because | |
| 4115 X Windows normally operates asynchronously: A bunch of commands are | |
| 4116 buffered up and then sent to the server all at once. This greatly | |
| 4117 improves performance over a network but means that an error may not be | |
| 4118 reported until the server receives the commands, which can be long | |
| 4119 after XEmacs made the erroneous calls. For best results, you need to | |
| 4120 make the X server synchronous before getting the backtrace. This can | |
| 4121 be done by starting XEmacs with the @samp{-sync} option or executing | |
| 4122 the Lisp code @code{(x-debug-mode t)}. | |
| 563 | 4123 |
| 4124 @item | |
| 428 | 4125 Internally, you will probably see lots of variables that hold objects of |
| 1258 | 4126 type @code{Lisp_Object}. These are references to Lisp objects. |
| 4127 Printing them out with the debugger probably won't be too | |
| 4128 useful---you'll likely just see a number. To decode them, do this: | |
| 428 | 4129 |
| 4130 @example | |
| 2417 | 4131 call debug_print (OBJECT) |
| 428 | 4132 @end example |
| 4133 | |
| 4134 where @var{OBJECT} is whatever you want to decode (it can be a variable, | |
| 1258 | 4135 a function call, etc.). This uses the Lisp printing routines to out a |
| 4136 readable representation on the TTY from which the xemacs process was | |
| 4137 invoked. | |
| 428 | 4138 |
| 2417 | 4139 Under 21.5 and later, @code{dp} is defined as an easier-to-type equivalent |
| 4140 of @code{debug_print}. You can also try @code{dpa} if you can't see | |
| 4141 the output from @code{debug_print} (this will return a string containing | |
| 4142 the output), or use @code{debug_p3} if @code{debug_print} itself triggers | |
| 4143 a crash (this is a less comprehensive but super-safe way to print out | |
| 4144 a Lisp object). | |
| 4145 | |
| 428 | 4146 @item |
| 4147 If you want to get a Lisp backtrace showing the Lisp call | |
| 4148 stack, do this: | |
| 4149 | |
| 4150 @example | |
| 2417 | 4151 call debug_backtrace () |
| 428 | 4152 @end example |
| 4153 | |
| 2417 | 4154 Under 21.5 and later, @code{db} is defined as an easier-to-type equivalent |
| 4155 of @code{debug_backtrace}. | |
| 4156 | |
| 4157 @item | |
| 4158 Using @code{debug_print} and @code{debug_backtrace} has two | |
| 4159 disadvantages - they can only be used with a running (including hung | |
| 4160 or zombie) xemacs process, and they do not display the internal C | |
| 4161 structure of a Lisp Object. Even if all you've got is a core dump, | |
| 4162 all is not lost. | |
| 428 | 4163 |
| 4164 If you're using GDB, there are some macros in the file | |
| 438 | 4165 @file{src/.gdbinit} in the XEmacs source distribution that should make |
| 4166 it easier for you to decode Lisp objects. This file is automatically | |
| 4167 read by gdb if gdb is run in the directory where xemacs was built, and | |
| 4168 contains these useful macros to inspect the state of xemacs: | |
| 4169 | |
| 4170 @table @code | |
| 4171 @item pobj | |
| 4172 Usage: pobj lisp_object @* | |
| 4173 Print the internal C representation of a lisp object. | |
| 4174 | |
| 4175 @item xtype | |
| 4176 Usage: xtype lisp_object @* | |
| 4177 Print the Lisp type of a lisp object. | |
| 4178 | |
| 4179 @item lbt | |
| 4180 Usage: lbt @* | |
| 4181 Print the current Lisp stack trace. | |
| 1258 | 4182 Requires a running xemacs process. (It works by calling the db |
| 4183 routine described above.) | |
| 438 | 4184 |
| 4185 @item ldp | |
| 4186 Usage: ldp lisp_object @* | |
| 4187 Print a Lisp Object value using the Lisp printer. | |
| 1258 | 4188 Requires a running xemacs process. (It works by calling the dp |
| 4189 routine described above.) | |
| 438 | 4190 |
| 4191 @item run-temacs | |
| 4192 Usage: run-temacs @* | |
| 4193 Run temacs interactively, like xemacs. | |
| 4194 Use this with debugging tools (like purify) that cannot deal with dumping, | |
| 4195 or when temacs builds successfully, but xemacs does not. | |
| 4196 | |
| 4197 @item dump-temacs | |
| 4198 Usage: dump-temacs @* | |
| 4199 Run the dumping part of the build procedure. | |
| 4200 Use when debugging temacs, not xemacs! | |
| 4201 Use this when temacs builds successfully, but xemacs does not. | |
| 4202 | |
| 4203 @item check-xemacs | |
| 4204 Usage: check-xemacs @* | |
| 4205 Run the test suite. Equivalent to 'make check'. | |
| 4206 | |
| 4207 @item check-temacs | |
| 4208 Usage: check-temacs @* | |
| 4209 Run the test suite on temacs. Equivalent to 'make check-temacs'. | |
| 4210 Use this with debugging tools (like purify) that cannot deal with dumping, | |
| 4211 or when temacs builds successfully, but xemacs does not. | |
| 4212 @end table | |
| 428 | 4213 |
| 4214 If you are using Sun's @file{dbx} debugger, there is an equivalent file | |
| 438 | 4215 @file{src/.dbxrc}, which defines the same commands for dbx. |
| 428 | 4216 |
| 4217 @item | |
| 4218 If you're using a debugger to get a C stack backtrace and you're seeing | |
| 4219 stack traces with some of the innermost frames mangled, it may be due to | |
| 4220 dynamic linking. (This happens especially under Linux.) Consider | |
| 3018 | 4221 reconfiguring with @samp{--dynamic=no} (@samp{--with-dynamic=no} in 21.5 |
| 4222 or later). Also, sometimes (again under Linux), stack backtraces of | |
| 4223 core dumps will have the frame where the fatal signal occurred mangled; | |
| 4224 if you can obtain a stack trace while running the XEmacs process under a | |
| 4225 debugger, the stack trace should be clean. | |
| 428 | 4226 |
| 1183 | 4227 @email{1CMC3466@@ibm.mtsac.edu, Curtiss} suggests upgrading to ld.so |
| 4228 version 1.8 if dynamic linking and debugging is a problem on Linux. | |
| 428 | 4229 |
| 4230 @item | |
| 4231 If you're using a debugger to get a C stack backtrace and you're | |
| 4232 getting a completely mangled and bogus stack trace, it's probably due to | |
| 4233 one of the following: | |
| 4234 | |
| 4235 @enumerate a | |
| 4236 @item | |
| 4237 Your executable has been stripped. Bad news. Tell your sysadmin not to | |
| 4238 do this---it doesn't accomplish anything except to save a bit of disk | |
| 4239 space, and makes debugging much much harder. | |
| 4240 | |
| 4241 @item | |
| 4242 Your stack is getting trashed. Debugging this is hard; you have to do a | |
| 4243 binary-search type of narrowing down where the crash occurs, until you | |
| 4244 figure out exactly which line is causing the problem. Of course, this | |
| 1258 | 4245 only works if the bug is highly reproducible. Also, in many cases if |
| 4246 you run XEmacs from the debugger, the debugger can protect the stack | |
| 4247 somewhat. However, if the stack is being smashed, it is typically the | |
| 4248 case that there is a wild pointer somewhere in the program, often quite | |
| 4249 far from where the crash occurs. | |
| 428 | 4250 |
| 4251 @item | |
| 4252 If your stack trace has exactly one frame in it, with address 0x0, this | |
| 4253 could simply mean that XEmacs attempted to execute code at that address, | |
| 4254 e.g. through jumping to a null function pointer. Unfortunately, under | |
| 4255 those circumstances, GDB under Linux doesn't know how to get a stack | |
| 1183 | 4256 trace. (Yes, this is the fourth Linux-related problem I've mentioned. I |
| 428 | 4257 have no idea why GDB under Linux is so bogus. Complain to the GDB |
| 1183 | 4258 authors, or to comp.os.linux.development.system.) Again, you'll have to |
| 428 | 4259 use the narrowing-down process described above. |
| 4260 | |
| 4261 @item | |
| 462 | 4262 You will get a Lisp backtrace output when XEmacs crashes, so you'll have |
| 4263 something useful. | |
| 428 | 4264 |
| 4265 @end enumerate | |
| 4266 | |
| 4267 @item | |
| 4268 If you compile with the newer gcc variants gcc-2.8 or egcs, you will | |
| 438 | 4269 also need gdb 4.17 or above. Earlier releases of gdb can't handle the |
| 4270 debug information generated by the newer compilers. | |
| 428 | 4271 |
| 4272 @item | |
| 438 | 4273 In versions of XEmacs before 21.2.27, @file{src/.gdbinit} was named |
| 4274 @file{src/gdbinit}. This had the disadvantage of not being sourced | |
| 4275 automatically by gdb, so you had to set that up yourself. | |
| 428 | 4276 |
| 1183 | 4277 @item |
| 4278 If you are running Microsoft Windows, the the file @file{nt/README} for | |
| 4279 further information about debugging XEmacs. | |
| 4280 | |
| 428 | 4281 @end itemize |
| 4282 | |
| 2559 | 4283 @node Q2.4.5, Q2.4.6, Q2.4.4, Installation |
| 4284 @unnumberedsubsec Q2.4.5: I get a cryptic error message when trying to do something. | |
| 2417 | 4285 |
| 4286 When I try to use some particular option of some particular package, I | |
| 4287 get a cryptic error message in the minibuffer. | |
| 4288 | |
| 4289 If the message went by too quickly, use @samp{Help->Recent Messages} | |
| 4290 from the menubar (or type @kbd{C-h l}) to see recent messages. | |
| 4291 | |
| 4292 If you can't figure out what's going on, select | |
| 4293 @samp{Options->Troubleshooting->Debug on Error} from the menubar (or | |
| 4294 type @kbd{M-:} then @kbd{(setq debug-on-error t)}) then try and make | |
| 4295 the error happen again. This will put in the debugger (you can get | |
| 4296 out of this and continue what you were doing before by typing @kbd{c}) | |
| 4297 and give you a backtrace that may be enlightening. If not, try | |
| 4298 reading through this FAQ; if that fails, you could try posting to | |
| 4299 @samp{comp.emacs.xemacs} (making sure to include the backtrace) and | |
| 4300 someone may be able to help. If you can identify which XEmacs Lisp | |
| 4301 source file the error is coming from you can get a more detailed stack | |
| 4302 backtrace by doing the following: | |
| 428 | 4303 |
| 4304 @enumerate | |
| 4305 @item | |
| 2417 | 4306 Visit the .el file in an XEmacs buffer. |
| 4307 | |
| 4308 @item | |
| 4309 Issue the command @kbd{M-x eval-current-buffer}. | |
| 4310 | |
| 4311 @item | |
| 4312 Reproduce the error. | |
| 428 | 4313 @end enumerate |
| 4314 | |
| 2417 | 4315 For more information on debugging Lisp code, @xref{Debugging,,, |
| 4316 lispref, XEmacs Lisp Reference Manual}. | |
| 4317 | |
| 2559 | 4318 @node Q2.4.6, Q2.4.7, Q2.4.5, Installation |
| 4319 @unnumberedsubsec Q2.4.6: XEmacs hangs when I try to do something. | |
| 2417 | 4320 |
| 4321 XEmacs might just be slow; some operations take a long time. XEmacs | |
| 4322 may also be waiting on a response from the network, for example when | |
| 4323 you are trying to send mail. | |
| 4324 | |
| 4325 You can usually interrupt XEmacs by typing @kbd{C-g}. If not (for | |
| 4326 example, Lisp code explicitly disabled this by setting | |
| 4327 @code{inhibit-quit}), you can use the "critical quit" mechanism by | |
| 4328 typing @kbd{Control-Shift-G}. This should also pop you into the | |
| 4329 debugger and give you a backtrace, which can tell you where the | |
| 2559 | 4330 problem is (@pxref{Q2.4.4, How to debug an XEmacs problem with a |
| 2417 | 4331 debugger}). (Note that setting @code{debug-on-quit} or selecting |
| 4332 @samp{Options->Troubleshooting->Debug on Quit} will also cause regular | |
| 4333 @kbd{C-g} to enter the debugger and give you a backtrace.) | |
| 4334 | |
| 4335 If you can't interrupt XEmacs this way, or for some reason XEmacs is | |
| 4336 not talking to the keyboard, you can try sending the @samp{SIGINT} | |
| 4337 signal using the @samp{kill} command. | |
| 4338 | |
| 4339 If the Lisp backtrace isn't enlightening, or if XEmacs is so hung that | |
| 4340 you can't interrupt it at all, you could try attaching to the process | |
| 2559 | 4341 and getting a C stack backtrace. @xref{Q2.4.4, How to debug an XEmacs |
| 2417 | 4342 problem with a debugger}. |
| 4343 | |
| 2559 | 4344 @node Q2.4.7, Q2.4.8, Q2.4.6, Installation |
| 4345 @unnumberedsubsec Q2.4.7: I get an error message when XEmacs is running in batch mode. | |
| 2417 | 4346 |
| 4347 Typically this happens when you are trying to compile some Elisp code. | |
| 4348 If you are doing this as part of XEmacs or the XEmacs packages, you | |
| 4349 should automatically get a backtrace, which can help you determine the | |
| 4350 source of the problem. In other cases, you can get equivalent results | |
| 4351 by setting the environment variable @samp{XEMACSDEBUG} to @samp{(setq | |
| 4352 stack-trace-on-error t load-always-display-messages t | |
| 4353 load-ignore-out-of-date-elc-files t load-show-full-path-in-messages | |
| 4354 t)} (this needs to be all on one line; to set an environment variable, | |
| 4355 use @samp{export XEMACSDEBUG='FOO'} under @samp{bash}, @samp{zsh}, | |
| 4356 etc. or @samp{setenv XEMACSDEBUG 'FOO'} under @samp{csh} and | |
| 4357 @samp{tcsh}). @samp{XEMACSDEBUG} specifies Lisp code that will be | |
| 4358 executed at startup time. | |
| 4359 | |
| 4360 If the backtrace is not sufficiently useful in helping you diagnose | |
| 4361 the problem, you should consider using a debugger such as GDB. | |
| 2559 | 4362 @xref{Q2.4.4, How to debug an XEmacs problem with a debugger}. You |
| 2417 | 4363 probably want to set a breakpoint on @code{signal_1}. Since such |
| 4364 errors often occur during compiling, which is often triggered by a | |
| 4365 complex command run from a make suite, it may be easier to attach to | |
| 4366 the process once it's running. | |
| 4367 | |
| 3018 | 4368 Under Microsoft Windows (and perhaps other operating systems), there is |
| 4369 another useful trick you can do if you have configured with debugging | |
| 4370 support (configure option @samp{--debug} (@samp{--with-debug} in 21.5) | |
| 4371 or setting @samp{DEBUG_XEMACS} in @file{nt/config.inc}). Set the | |
| 4372 environment variable @samp{XEMACSDEBUG} (as described above) to | |
| 4373 @samp{(setq debug-on-error t)}. Then, when an error occurs | |
| 4374 noninteractively, instead of trying to invoke the Lisp debugger (which | |
| 4375 obviously won't work), XEmacs will break out to a C debugger using | |
| 2417 | 4376 @code{(force-debugging-signal t)}. @emph{NOTE}: This runs |
| 4377 @code{abort()}!!! (As well as and after executing INT 3 under MS | |
| 4378 Windows, which should invoke a debugger if it's active.) This is | |
| 4379 guaranteed to kill XEmacs! (But in this situation, XEmacs is about to | |
| 4380 die anyway, and if no debugger is present, this will usefully dump | |
| 4381 core.) | |
| 4382 | |
| 2559 | 4383 @node Q2.4.8, Q2.4.9, Q2.4.7, Installation |
| 4384 @unnumberedsubsec Q2.4.8: The keyboard or mouse is not working properly, or I have some other event-related problem. | |
| 2417 | 4385 |
| 4386 XEmacs has various facilities for debugging event handling. | |
| 4387 | |
| 4388 First, try setting the variable @code{debug-emacs-events} to non-zero. | |
| 4389 This will output various information showing which events are being | |
| 4390 received and how they are being translated. This may show you, for | |
| 4391 example, that a key command is getting intercepted using | |
| 4392 @code{key-translation-map}; this problem can otherwise be very tricky | |
| 4393 to debug. | |
| 4394 | |
| 4395 Under X, you can see exactly which events are being received from the | |
| 4396 window system by setting @code{x-debug-events} to non-zero. (The value | |
| 4397 @samp{1} gives you regular output, and @samp{2} gives you verbose | |
| 4398 output, including all parameters.) | |
| 4399 | |
| 4400 A similar facility exists under MS Windows: Set | |
| 4401 @code{debug-mswindows-events} to non-zero. (The value @samp{1} gives | |
| 4402 you regular output. The value @samp{2} gives you verbose output, | |
| 4403 including all parameters. The value @samp{3} gives you | |
| 4404 super-gorily-detailed output.) | |
| 4405 | |
| 2559 | 4406 @node Q2.4.9, Q2.4.10, Q2.4.8, Installation |
| 4407 @unnumberedsubsec Q2.4.9: @kbd{C-g} doesn't work for me. Is it broken? | |
| 2417 | 4408 |
| 4409 @kbd{C-g} does work for most people in most circumstances. If it | |
| 4410 doesn't, there are two possible explanations: | |
| 4411 | |
| 4412 @enumerate | |
| 4413 @item | |
| 4414 XEmacs is hung in a way that prevents @kbd{C-g} from working. This | |
| 4415 can happen when code is wrapped with a binding of @code{inhibit-quit} | |
| 4416 to @code{t}; you should still be able interrupt XEmacs using "critical | |
| 4417 quit". On the other hand, XEmacs may be seriously wedged. (If you're | |
| 4418 lucky, sending @samp{SIGINT} to the XEmacs process will interrupt it.) | |
| 2559 | 4419 @xref{Q2.4.6, XEmacs hangs when I try to do something.}. |
| 2417 | 4420 |
| 4421 @item | |
| 4422 @kbd{C-g} is indeed broken on your system. To test, try executing | |
| 4423 @code{(while t)} from the @samp{*scratch*} buffer. If @kbd{C-g} | |
| 4424 doesn't interrupt, then it's broken. This used to happen with systems | |
| 4425 where @samp{SIGIO} was broken, but @samp{BROKEN_SIGIO} wasn't defined. | |
| 4426 However, there may not be very many such systems nowadays. | |
| 4427 @end enumerate | |
| 4428 | |
| 2559 | 4429 @node Q2.4.10, Q2.4.11, Q2.4.9, Installation |
| 4430 @unnumberedsubsec Q2.4.10: How do I debug process-related problems? | |
| 2417 | 4431 |
| 4432 Under MS Windows, you can set the variable | |
| 4433 @code{debug-mswindows-process-command-lines} to non-@samp{nil} to get | |
| 4434 information on exactly what is getting passed to a process. This can | |
| 4435 be useful in determining problems with quoting. (Under Unix, a process | |
| 4436 receives each argument separately, but under MS Windows a single | |
| 4437 command line is received, and arguments with spaces or other special | |
| 4438 characters in them must be quoted. Unfortunately this means that each | |
| 4439 process, potentially at least, has its own quoting conventions, and | |
| 4440 the code to process quoting conventions in @file{cmd.exe}, the Visual | |
| 4441 C++ startup code and the like is baroque and poorly documented. | |
| 4442 XEmacs uses the variable | |
| 4443 @code{mswindows-construct-process-command-line-alist} to construct a | |
| 4444 command line from a list of arguments based on the command to be run, | |
| 4445 but it is (and cannot be) a perfect solution.) | |
| 4446 | |
| 2559 | 4447 @node Q2.4.11, Q2.4.12, Q2.4.10, Installation |
| 4448 @unnumberedsubsec Q2.4.11: XEmacs is outputting lots of X errors. | |
| 563 | 4449 |
| 4450 If this is happening, we would very much like to know what's causing | |
| 2559 | 4451 them. To find this out, see @ref{Q2.4.4, How to debug an XEmacs |
| 2417 | 4452 problem with a debugger}. Try to get both a C and Lisp backtrace, and |
| 4453 send them along with the full error output to | |
| 4454 @email{xemacs-beta@@xemacs.org}. | |
| 4455 | |
| 2559 | 4456 @node Q2.4.12, Q2.5.1, Q2.4.11, Installation |
| 4457 @unnumberedsubsec Q2.4.12: After upgrading, XEmacs won't do `foo' any more! | |
| 2417 | 4458 |
| 4459 You have been used to doing `foo', but now when you invoke it (or | |
| 4460 click the toolbar button or select the menu item), nothing (or an | |
| 4461 error) happens. The simplest explanation is that you are missing a | |
| 4462 package that is essential to you. You can either track it down and | |
| 4463 install it (there is a list of packages and brief descriptions of | |
| 4464 their contents in @file{etc/PACKAGES}), or install the `Sumo Tarball' | |
| 2559 | 4465 (@pxref{Q2.1.2, How do I figure out which packages to install?}). |
| 2417 | 4466 |
| 4467 @c #### should xref to XEmacs manual here | |
| 4468 | |
| 2559 | 4469 @unnumberedsec 2.5: Startup-Related Problems |
| 4470 | |
| 4471 @node Q2.5.1, Q2.5.2, Q2.4.12, Installation | |
| 4472 @unnumberedsubsec Q2.5.1: XEmacs cannot connect to my X Terminal! | |
| 2417 | 4473 |
| 4474 Help! I can not get XEmacs to display on my Envizex X-terminal! | |
| 4475 | |
| 4476 Try setting the @code{DISPLAY} variable using the numeric IP address of | |
| 4477 the host you are running XEmacs from. | |
| 4478 | |
| 2559 | 4479 @node Q2.5.2, Q2.5.3, Q2.5.1, Installation |
| 4480 @unnumberedsubsec Q2.5.2 Startup problems related to paths or package locations. | |
| 4481 | |
| 4482 First of all, if XEmacs can't find the packages, check to make sure | |
| 4483 that you put the packages in the right place, or that you told XEmacs | |
| 4484 where to look for the packages when you compiled it. @xref{Q2.1.1}. | |
| 4485 | |
| 4486 If something is still going wrong, or you get a startup warning about | |
| 4487 not being able to deduce some paths, you can get detailed information | |
| 4488 on the path-searching process at startup by setting the environment | |
| 4489 variable @samp{EMACSDEBUGPATHS} to a non-null value. One thing to | |
| 4490 look for if you're having package problems is the value of | |
| 4491 @samp{configure-package-path}. This corresponds to what was compiled | |
| 4492 into XEmacs using the @samp{--package-prefix} or @samp{--package-path} | |
| 4493 parameter (@pxref{Q2.1.1}). If this has the value of @samp{nil}, | |
| 4494 this means that no value was compiled into XEmacs using these parameters. | |
| 4495 | |
| 4496 @node Q2.5.3, Q2.5.4, Q2.5.2, Installation | |
|
4658
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4497 @unnumberedsubsec Q2.5.3: XEmacs won't start without network, or starts slowly. |
| 434 | 4498 |
| 4499 If XEmacs starts when you're on the network, but fails when you're not | |
| 4500 on the network, you may be missing a "localhost" entry in your | |
| 4501 @file{/etc/hosts} file. The file should contain an entry like: | |
| 4502 | |
| 4503 @example | |
| 4504 127.0.0.1 localhost | |
| 4505 @end example | |
| 4506 | |
|
4658
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4507 Add that line, and XEmacs will be happy. If your network is unreliable, |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4508 such as a Wifi network, you may experience delays but eventually XEmacs |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4509 starts up. This may be due to having the lookup order give precedence |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4510 to DNS over the hosts file (often lookup order is defined in one of the |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4511 files @file{/etc/host.conf}, @file{/etc/nsswitch.conf}, or |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4512 @file{/etc/resolv.conf}, depending on OS). See your system |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4513 documentation for this configuration. Note that changing the lookup |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4514 order is a workaround; there are good reasons to have DNS come earlier |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4515 by default. Make sure those reasons are less important to you than a |
|
fd2495d78aac
Add FAQ on network slows (lookup order of DNS and /etc/hosts).
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4625
diff
changeset
|
4516 quick XEmacs startup. |
| 434 | 4517 |
| 2559 | 4518 @node Q2.5.4, Q2.5.5, Q2.5.3, Installation |
| 4519 @unnumberedsubsec Q2.5.4: Startup warnings about deducing proper fonts? | |
| 2417 | 4520 |
| 4521 How can I avoid the startup warnings about deducing proper fonts? | |
| 4522 | |
| 4523 This is highly dependent on your installation, but try with the | |
| 4524 following font as your base font for XEmacs and see what it does: | |
| 4525 | |
| 4526 @format | |
| 4527 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
| 4528 @end format | |
| 4529 | |
| 4530 More precisely, do the following in your resource file: | |
| 4531 | |
| 4532 @format | |
| 4533 Emacs.default.attributeFont: \ | |
| 4534 -adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1 | |
| 4535 @end format | |
| 4536 | |
| 4537 If you just don't want to see the @samp{*Warnings*} buffer at startup | |
| 4538 time, you can set this: | |
| 428 | 4539 |
| 4540 @lisp | |
| 2417 | 4541 (setq display-warning-minimum-level 'error) |
| 428 | 4542 @end lisp |
| 4543 | |
| 2417 | 4544 The buffer still exists; it just isn't in your face. |
| 4545 | |
| 2559 | 4546 @node Q2.5.5, Q2.5.6, Q2.5.4, Installation |
| 4547 @unnumberedsubsec Q2.5.5: Warnings from incorrect key modifiers. | |
| 2417 | 4548 |
| 4549 The following information comes from the @file{PROBLEMS} file that comes | |
| 4550 with XEmacs. | |
| 4551 | |
| 4552 If you're having troubles with HP/UX it is because HP/UX defines the | |
| 4553 modifiers wrong in X. Here is a shell script to fix the problem; be | |
| 4554 sure that it is run after VUE configures the X server. | |
| 428 | 4555 |
| 4556 @example | |
| 2417 | 4557 #! /bin/sh |
| 4558 xmodmap 2> /dev/null - << EOF | |
| 4559 keysym Alt_L = Meta_L | |
| 4560 keysym Alt_R = Meta_R | |
| 4561 EOF | |
| 4562 | |
| 4563 xmodmap - << EOF | |
| 4564 clear mod1 | |
| 4565 keysym Mode_switch = NoSymbol | |
| 4566 add mod1 = Meta_L | |
| 4567 keysym Meta_R = Mode_switch | |
| 4568 add mod2 = Mode_switch | |
| 4569 EOF | |
| 428 | 4570 @end example |
| 4571 | |
|
5390
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4572 @node Q2.5.6, Q2.5.7, Q2.5.5, Installation |
| 2559 | 4573 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup. Has that been fixed? |
| 2417 | 4574 |
| 4575 Yes. | |
| 4576 | |
| 4577 The console was there because @file{temacs} (and in turn, @file{xemacs}) | |
| 4578 was a console application, and Windows typically creates a new | |
| 4579 console for a console process unless the creating process requests that | |
| 4580 one isn't created. This used to be fixed with @file{runemacs}, a small | |
| 4581 Windows application that existed merely to start @file{xemacs}, stating | |
| 4582 that it didn't want a console. | |
| 4583 | |
| 4584 XEmacs 21.4 fixes this cleanly by the virtue of being a true "GUI" | |
| 4585 application. The explanation of what that means is included for | |
| 4586 educational value. | |
| 4587 | |
| 4588 When building an application to be run in a Win32 environment, you must | |
| 4589 state which sub-system it is to run in. Valid subsystems include | |
| 4590 "console" and "gui". The subsystem you use affects the run time | |
| 4591 libraries linked into your application, the start up function that is | |
| 4592 run before control is handed over to your application, the entry point | |
| 4593 to your program, and how Windows normally invokes your program. (Console | |
| 4594 programs automatically get a console created for them at startup if | |
| 4595 their stdin/stdout don't point anywhere useful, which is the case when | |
| 4596 run from the GUI. This is a stupid design, of course -- instead, the | |
| 4597 console should get created only when the first I/O actually occurs! | |
| 4598 GUI programs have an equally stupid design: When called from | |
| 4599 @file{CMD.EXE}/@file{COMMAND.COM}, their stdin/stdout will be set to | |
| 4600 point nowhere useful, even though the command shell has its own | |
| 4601 stdin/stdout. It's as if someone who had learned a bit about stdio but | |
| 4602 had no actual knowledge of interprocess communication designed the | |
| 4603 scheme; unfortunately, the whole process-communication aspect of the | |
| 4604 Win32 API is equally badly designed.) For example, the entry point for a | |
| 4605 console app is "main" (which is what you'd expect for a C/C++ program), | |
| 4606 but the entry point for a "gui" app is "WinMain". This confuses and | |
| 4607 annoys a lot of programmers who've grown up on Unix systems, where the | |
| 4608 kernel doesn't really care whether your application is a gui program or | |
| 4609 not. | |
| 4610 | |
| 4611 For reasons not altogether clear, and are lost in the mists of time and | |
| 4612 tradition, XEmacs on Win32 started out as a console application, and | |
| 4613 therefore a console was automatically created for it. (It may have been | |
| 4614 made a console application partly because a console is needed in some | |
| 4615 circumstances, especially under Win95, to interrupt, terminate, or send | |
| 4616 signals to a child process, and because of the bogosity mentioned above | |
| 4617 with GUI programs and the standard command shell. Currently, XEmacs | |
| 4618 just creates and immediately hides a console when necessary, and | |
| 4619 works around the "no useful stdio" problem by creating its own console | |
| 4620 window as necessary to display messages in.) | |
| 4621 | |
|
5390
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4622 @node Q2.5.7, , Q2.5.6, Installation |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4623 @unnumberedsubsec Q2.5.7: XEmacs issues messages about ``auto-autoloads already loaded.'' |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4624 |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4625 On Sat, 05 Mar 2011 11:54:47 -0500, in Message-ID: |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4626 <4D726AD7.7020303@@gmail.com> on xemacs-beta, Raymond Toy reported: |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4627 |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4628 @quotation |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4629 [N]ow every time I start xemacs, I get 100+ error messages stating that |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4630 the auto-autoload for every package has already been loaded. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4631 @end quotation |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4632 |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4633 This occurs if you have duplicate packages installed on your load-path. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4634 To detect exactly which paths are duplicated, use @kbd{M-x |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4635 list-load-path-shadows}. If you have a small number of duplicated |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4636 libraries, it is probably one or more packages available both in the |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4637 XEmacs distribution and in third-party distributions. If you prefer the |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4638 third-party version, use @kbd{M-x list-packages} to get the package |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4639 management UI, and uninstall the particular packages. Removal of third |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4640 party packages must be done manually, if you wish to keep the version |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4641 distributed by XEmacs. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4642 |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4643 When you have many duplicate packages, a common cause is that XEmacs |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4644 finds @emph{package root directories} that are duplicates of each other. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4645 This can occur in some automounter configurations, or when the roots |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4646 share some subtrees via symlinks. In this case, you will get a warning |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4647 for @emph{all} of the packages you have installed. Although this is |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4648 basically a site configuration problem, please report these cases. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4649 XEmacs is already aware of many automounter artifacts, and automatically |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4650 adjusts for them. Code is being added to try to detect symlinks. We |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4651 may not be able to handle every case, but we'd like to know about them, |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4652 and where possible incorporate workarounds. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4653 |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4654 Package root directories are specified at configuration time via the |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4655 @code{--prefix}, @code{--exec-prefix}, and the @samp{--with-*-packages} |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4656 options; at runtime relative to the XEmacs binary (@file{../share} and |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4657 @file{..} (for run-in-place)); and at runtime via the |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4658 @samp{EMACS*PACKAGES} environment variables. Unless you have special |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4659 needs, it is best to install XEmacs and the packages (configuring with |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4660 @code{--with-prefix=$prefix} for XEmacs and by untarring the SUMOs in |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4661 @file{@code{$prefix}/share/xemacs/}. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4662 |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4663 Note that older versions of XEmacs (21.1, 21.4, and early releases of |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4664 21.5) by default expect the packages to be installed under |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4665 @file{@code{$prefix}/lib} rather than @file{@code{$prefix}/share}. See |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4666 the documentation for @file{configure} for how to point XEmacs at |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4667 @file{@code{$prefix}/share/xemacs/} if that is preferred, or older |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4668 XEmacsen need to share packages with recent versions. |
|
593d9f73a7e8
New FAQ Q2.5.7 on troubleshooting duplicate auto-autoloads.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
5384
diff
changeset
|
4669 |
| 2459 | 4670 @node Editing, Display, Installation, Top |
| 4671 @unnumbered 3 Editing Functions | |
| 2417 | 4672 |
| 4673 This is part 3 of the XEmacs Frequently Asked Questions list. This | |
| 2459 | 4674 section is devoted to the editing-related capabilities of XEmacs (the |
| 4675 keyboard, mouse, buffers, text selections, etc.) and how to customize | |
| 4676 them. | |
| 2417 | 4677 |
| 4678 @menu | |
| 4679 3.0: The Keyboard | |
| 2459 | 4680 * Q3.0.1:: How can I customize the keyboard? |
| 4681 * Q3.0.2:: How can I bind complex functions (or macros) to keys? | |
| 4682 * Q3.0.3:: How do I bind C-. and C-; to scroll one line up and down? | |
| 4683 * Q3.0.4:: Globally binding @kbd{Delete}? | |
| 4684 * Q3.0.5:: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 4685 * Q3.0.6:: How can you type in special characters in XEmacs? | |
| 4686 * Q3.0.7:: Can I turn on @dfn{sticky} modifier keys? | |
| 4687 * Q3.0.8:: How do I map the arrow keys? | |
| 4688 * Q3.0.9:: HP Alt key as Meta. | |
| 4689 * Q3.0.10:: Why does edt emulation not work? | |
| 4690 * 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
|
4691 * Q3.0.12:: Mac Alt/Option key as Meta. |
| 2417 | 4692 |
| 4693 3.1: The Mouse | |
| 4694 * Q3.1.1:: How can I turn off Mouse pasting? | |
| 4695 * Q3.1.2:: How do I set control/meta/etc modifiers on mouse buttons? | |
| 4696 * Q3.1.3:: Clicking the left button does not do anything in buffer list. | |
| 4697 * Q3.1.4:: How can I get a list of buffers when I hit mouse button 3? | |
| 2459 | 4698 * Q3.1.5:: How can I set XEmacs up so that it pastes where the text cursor is? |
| 4699 | |
| 4700 3.2: Buffers, Text Editing | |
| 4701 * Q3.2.1:: Can I have the end of the buffer delimited in some way? | |
| 4702 * Q3.2.2:: How do I insert today's date into a buffer? | |
| 4703 * Q3.2.3:: How do I get a single minibuffer frame? | |
| 4704 * Q3.2.4:: How can I enable auto-indent and/or Filladapt? | |
| 4705 * Q3.2.5:: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 4706 | |
| 4707 3.3: Text Selections | |
| 4708 * Q3.3.1:: How do I select a rectangular region? | |
| 4709 * Q3.3.2:: How can I turn off or change highlighted selections? | |
| 4710 * Q3.3.3:: How do I cause typing on an active region to remove it? | |
| 4711 * Q3.3.4:: Can I turn off the highlight during isearch? | |
| 4712 * Q3.3.5:: Why is killing so slow? | |
| 4713 * Q3.3.6:: Why does @kbd{M-w} take so long? | |
| 4714 | |
| 4715 3.4: Editing Source Code | |
| 4716 * Q3.4.1:: I do not like cc-mode. How do I use the old c-mode? | |
| 4717 * Q3.4.2:: How do you make XEmacs indent CL if-clauses correctly? | |
| 2417 | 4718 @end menu |
| 4719 | |
| 4720 @unnumberedsec 3.0: The Keyboard | |
| 4721 | |
| 2459 | 4722 @node Q3.0.1, Q3.0.2, Editing, Editing |
| 4723 @unnumberedsubsec Q3.0.1: How can I customize the keyboard? | |
| 4724 | |
| 4725 #### Write me. | |
| 4726 | |
| 4727 @node Q3.0.2, Q3.0.3, Q3.0.1, Editing | |
| 4728 @unnumberedsubsec Q3.0.2: How can I bind complex functions (or macros) to keys? | |
| 428 | 4729 |
| 4730 As an example, say you want the @kbd{paste} key on a Sun keyboard to | |
| 4731 insert the current Primary X selection at point. You can accomplish this | |
| 4732 with: | |
| 4733 | |
| 4734 @lisp | |
| 4735 (define-key global-map [f18] 'x-insert-selection) | |
| 4736 @end lisp | |
| 4737 | |
| 4738 However, this only works if there is a current X selection (the | |
| 4739 selection will be highlighted). The functionality I like is for the | |
| 4740 @kbd{paste} key to insert the current X selection if there is one, | |
| 4741 otherwise insert the contents of the clipboard. To do this you need to | |
| 4742 pass arguments to @code{x-insert-selection}. This is done by wrapping | |
| 4743 the call in a 'lambda form: | |
| 4744 | |
| 4745 @lisp | |
| 4746 (global-set-key [f18] | |
| 4747 (lambda () (interactive) (x-insert-selection t nil))) | |
| 4748 @end lisp | |
| 4749 | |
| 4750 This binds the f18 key to a @dfn{generic} functional object. The | |
| 4751 interactive spec is required because only interactive functions can be | |
| 4752 bound to keys. | |
| 4753 | |
| 4754 For the FAQ example you could use: | |
| 4755 | |
| 4756 @lisp | |
| 4757 (global-set-key [(control ?.)] | |
| 4758 (lambda () (interactive) (scroll-up 1))) | |
| 440 | 4759 (global-set-key [(control ?;)] |
| 4760 (lambda () (interactive) (scroll-up -1))) | |
| 428 | 4761 @end lisp |
| 4762 | |
| 4763 This is fine if you only need a few functions within the lambda body. | |
| 2417 | 4764 If you're doing more it's cleaner to define a separate function. |
| 2459 | 4765 @xref{Q3.0.3, How do I bind C-. and C-; to scroll one line up and |
| 2417 | 4766 down?}. |
| 4767 | |
| 2459 | 4768 @node Q3.0.3, Q3.0.4, Q3.0.2, Editing |
| 4769 @unnumberedsubsec Q3.0.3: How do I bind C-. and C-; to scroll one line up and down? | |
| 428 | 4770 |
| 4771 Add the following (Thanks to @email{mly@@adoc.xerox.com, Richard Mlynarik} and | |
| 4772 @email{wayne@@zen.cac.stratus.com, Wayne Newberry}) to @file{.emacs}: | |
| 4773 | |
| 4774 @lisp | |
| 4775 (defun scroll-up-one-line () | |
| 4776 (interactive) | |
| 4777 (scroll-up 1)) | |
| 4778 | |
| 4779 (defun scroll-down-one-line () | |
| 4780 (interactive) | |
| 4781 (scroll-down 1)) | |
| 4782 | |
| 4783 (global-set-key [(control ?.)] 'scroll-up-one-line) ; C-. | |
| 440 | 4784 (global-set-key [(control ?;)] 'scroll-down-one-line) ; C-; |
| 428 | 4785 @end lisp |
| 4786 | |
| 4787 The key point is that you can only bind simple functions to keys; you | |
| 2417 | 4788 can not bind a key to a function that you're also passing arguments |
| 2459 | 4789 to. (@pxref{Q3.0.2, How can I bind complex functions (or macros) to |
| 2417 | 4790 keys?} for a better answer). |
| 4791 | |
| 2459 | 4792 @node Q3.0.4, Q3.0.5, Q3.0.3, Editing |
| 4793 @unnumberedsubsec Q3.0.4: Globally binding @kbd{Delete}? | |
| 428 | 4794 |
| 4795 I cannot manage to globally bind my @kbd{Delete} key to something other | |
| 4796 than the default. How does one do this? | |
| 4797 | |
| 462 | 4798 Answer: The problem is that many modes explicitly bind @kbd{Delete}. To |
| 4799 get around this, try the following: | |
| 4800 | |
| 428 | 4801 @lisp |
| 4802 (defun foo () | |
| 4803 (interactive) | |
| 4804 (message "You hit DELETE")) | |
| 4805 | |
| 462 | 4806 (define-key key-translation-map 'delete 'redirected-delete) |
| 4807 (global-set-key 'redirected-delete 'foo) | |
| 428 | 4808 @end lisp |
| 4809 | |
| 2459 | 4810 @node Q3.0.5, Q3.0.6, Q3.0.4, Editing |
| 4811 @unnumberedsubsec Q3.0.5: How to map @kbd{Help} key alone on Sun type4 keyboard? | |
| 428 | 4812 |
| 4813 The following works in GNU Emacs 19: | |
| 4814 | |
| 4815 @lisp | |
| 4816 (global-set-key [help] 'help-command);; Help | |
| 4817 @end lisp | |
| 4818 | |
| 462 | 4819 The following works in XEmacs with the addition of shift: |
| 428 | 4820 |
| 4821 @lisp | |
| 4822 (global-set-key [(shift help)] 'help-command);; Help | |
| 4823 @end lisp | |
| 4824 | |
| 4825 But it doesn't work alone. This is in the file @file{PROBLEMS} which | |
| 4826 should have come with your XEmacs installation: @emph{Emacs ignores the | |
| 4827 @kbd{help} key when running OLWM}. | |
| 4828 | |
| 4829 OLWM grabs the @kbd{help} key, and retransmits it to the appropriate | |
| 4830 client using | |
| 4831 @iftex | |
| 4832 @* | |
| 4833 @end iftex | |
| 4834 @code{XSendEvent}. Allowing Emacs to react to synthetic | |
| 4835 events is a security hole, so this is turned off by default. You can | |
| 4836 enable it by setting the variable @code{x-allow-sendevents} to t. You | |
| 4837 can also cause fix this by telling OLWM to not grab the help key, with | |
| 4838 the null binding @code{OpenWindows.KeyboardCommand.Help:}. | |
| 4839 | |
| 2459 | 4840 @node Q3.0.6, Q3.0.7, Q3.0.5, Editing |
| 4841 @unnumberedsubsec Q3.0.6: How can you type in special characters in XEmacs? | |
| 428 | 4842 One way is to use the package @code{x-compose}. Then you can use |
| 4843 sequences like @kbd{Compose " a} to get ä, etc. | |
| 4844 | |
| 462 | 4845 Another way is to use the @code{iso-insert} package. Then you can use |
| 4846 sequences like @kbd{C-x 8 " a} to get ä, etc. | |
| 428 | 4847 |
| 4848 @email{glynn@@sensei.co.uk, Glynn Clements} writes: | |
| 4849 | |
| 4850 @quotation | |
| 4851 It depends upon your X server. | |
| 4852 | |
| 4853 Generally, the simplest way is to define a key as Multi_key with | |
| 4854 xmodmap, e.g. | |
| 4855 @c hey, show some respect, willya -- there's xkeycaps, isn't there? -- | |
| 4856 @c chr ;) | |
| 4857 @example | |
| 440 | 4858 xmodmap -e 'keycode 0xff20 = Multi_key' |
| 428 | 4859 @end example |
| 4860 | |
| 4861 You will need to pick an appropriate keycode. Use xev to find out the | |
| 4862 keycodes for each key. | |
| 4863 | |
| 4864 [NB: On a `Windows' keyboard, recent versions of XFree86 automatically | |
| 4865 define the right `Windows' key as Multi_key'.] | |
| 4866 | |
| 4867 Once you have Multi_key defined, you can use e.g. | |
| 4868 @example | |
| 440 | 4869 Multi a ' => á |
| 4870 Multi e " => ë | |
| 4871 Multi c , => ç | |
| 428 | 4872 @end example |
| 4873 | |
| 4874 etc. | |
| 4875 | |
| 4876 Also, recent versions of XFree86 define various AltGr-<key> | |
| 4877 combinations as dead keys, i.e. | |
| 4878 @example | |
| 440 | 4879 AltGr [ => dead_diaeresis |
| 4880 AltGr ] => dead_tilde | |
| 4881 AltGr ; => dead_acute | |
| 428 | 4882 @end example |
| 4883 etc. | |
| 4884 | |
| 4885 Running @samp{xmodmap -pk} will list all of the defined keysyms. | |
| 4886 @end quotation | |
| 4887 | |
| 1135 | 4888 For the related problem of @emph{displaying} non-ASCII characters in a |
| 2459 | 4889 non-Mule XEmacs, @xref{Q4.0.8, How do I display non-ASCII characters?}. |
| 4890 | |
| 4891 @node Q3.0.7, Q3.0.8, Q3.0.6, Editing | |
| 4892 @unnumberedsubsec Q3.0.7: Can I turn on @dfn{sticky} modifier keys? | |
| 428 | 4893 |
| 4894 Yes, with @code{(setq modifier-keys-are-sticky t)}. This will give the | |
| 4895 effect of being able to press and release Shift and have the next | |
| 4896 character typed come out in upper case. This will affect all the other | |
| 4897 modifier keys like Control and Meta as well. | |
| 4898 | |
| 4899 @email{ben@@xemacs.org, Ben Wing} writes: | |
| 4900 | |
| 4901 @quotation | |
| 4902 One thing about the sticky modifiers is that if you move the mouse out | |
| 4903 of the frame and back in, it cancels all currently ``stuck'' modifiers. | |
| 4904 @end quotation | |
| 4905 | |
| 2459 | 4906 @node Q3.0.8, Q3.0.9, Q3.0.7, Editing |
| 4907 @unnumberedsubsec Q3.0.8: How do I map the arrow keys? | |
| 428 | 4908 @c New |
| 4909 Say you want to map @kbd{C-@key{right}} to forward-word: | |
| 4910 | |
| 4911 @email{sds@@usa.net, Sam Steingold} writes: | |
| 4912 | |
| 4913 @quotation | |
| 4914 @lisp | |
| 4915 ; both XEmacs and Emacs | |
| 4916 (define-key global-map [(control right)] 'forward-word) | |
| 4917 @end lisp | |
| 4918 or | |
| 4919 @lisp | |
| 4920 ; Emacs only | |
| 4921 (define-key global-map [C-right] 'forward-word) | |
| 4922 @end lisp | |
| 4923 or | |
| 4924 @lisp | |
| 4925 ; ver > 20, both | |
| 4926 (define-key global-map (kbd "C-<right>") 'forward-word) | |
| 4927 @end lisp | |
| 4928 @end quotation | |
| 4929 | |
| 2459 | 4930 @node Q3.0.9, Q3.0.10, Q3.0.8, Editing |
| 4931 @unnumberedsubsec Q3.0.9: HP Alt key as Meta. | |
| 2417 | 4932 |
| 4933 How can I make XEmacs recognize the Alt key of my HP workstation as a | |
| 4934 Meta key? | |
| 4935 | |
| 4936 Put the following line into a file and load it with xmodmap(1) before | |
| 4937 starting XEmacs: | |
| 428 | 4938 |
| 4939 @example | |
| 2417 | 4940 remove Mod1 = Mode_switch |
| 428 | 4941 @end example |
| 4942 | |
| 2459 | 4943 @node Q3.0.10, Q3.0.11, Q3.0.9, Editing |
| 4944 @unnumberedsubsec Q3.0.10: Why does edt emulation not work? | |
| 2417 | 4945 |
| 4946 We don't know, but you can use tpu-edt emulation instead, which works | |
| 4947 fine and is a little fancier than the standard edt emulation. To do | |
| 4948 this, add the following line to your @file{init.el}: | |
| 4949 | |
| 4950 @lisp | |
| 4951 (tpu-edt) | |
| 4952 @end lisp | |
| 4953 | |
| 4954 If you don't want it to replace @kbd{C-h} with an edt-style help menu | |
| 4955 add this as well: | |
| 428 | 4956 |
| 4957 @lisp | |
| 2417 | 4958 (global-set-key [(control h)] 'help-for-help) |
| 428 | 4959 @end lisp |
| 4960 | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4961 @node Q3.0.11, Q3.0.12, Q3.0.10, Editing |
| 2459 | 4962 @unnumberedsubsec Q3.0.11: How can I emulate VI and use it as my default mode? |
| 2417 | 4963 |
| 4964 Our recommended VI emulator is viper. To make viper-mode the default, | |
| 4965 add this to your @file{init.el}: | |
| 428 | 4966 |
| 4967 @lisp | |
| 2417 | 4968 (viper-mode) |
| 428 | 4969 @end lisp |
| 4970 | |
| 2417 | 4971 @email{kifer@@CS.SunySB.EDU, Michael Kifer} writes: |
| 4972 | |
| 4973 @quotation | |
| 4974 This should be added as close to the top of @file{init.el} as you can get | |
| 4975 it, otherwise some minor modes may not get viper-ized. | |
| 4976 @end quotation | |
| 4977 | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4978 @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
|
4979 @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
|
4980 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4981 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
|
4982 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4983 Didier Verna suggests: |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4984 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4985 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
|
4986 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
|
4987 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4988 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
|
4989 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4990 @example |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4991 clear mod1 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4992 clear mod2 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4993 keycode 66 = Meta_L |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4994 keycode 63 = Mode_switch |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4995 add mod1 = Meta_L |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4996 @end example |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4997 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
4998 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
|
4999 |
|
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
5000 |
| 2417 | 5001 @unnumberedsec 3.1: The Mouse |
| 5002 | |
|
4625
4527fc976aa3
Meta on Mac. <87prh51rni.fsf@xemacs.org>
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4509
diff
changeset
|
5003 @node Q3.1.1, Q3.1.2, Q3.0.12, Editing |
| 2417 | 5004 @unnumberedsubsec Q3.1.1: How can I turn off Mouse pasting? |
| 428 | 5005 |
| 5006 I keep hitting the middle mouse button by accident and getting stuff | |
| 5007 pasted into my buffer so how can I turn this off? | |
| 5008 | |
| 5009 Here is an alternative binding, whereby the middle mouse button selects | |
| 5010 (but does not cut) the expression under the mouse. Clicking middle on a | |
| 5011 left or right paren will select to the matching one. Note that you can | |
| 5012 use @code{define-key} or @code{global-set-key}. | |
| 5013 | |
| 5014 @lisp | |
| 5015 (defun mouse-set-point-and-select (event) | |
| 5016 "Sets the point at the mouse location, then marks following form" | |
| 5017 (interactive "@@e") | |
| 5018 (mouse-set-point event) | |
| 5019 (mark-sexp 1)) | |
| 5020 (define-key global-map [button2] 'mouse-set-point-and-select) | |
| 5021 @end lisp | |
| 5022 | |
| 2459 | 5023 @node Q3.1.2, Q3.1.3, Q3.1.1, Editing |
| 2417 | 5024 @unnumberedsubsec Q3.1.2: How do I set control/meta/etc modifiers on mouse buttons? |
| 428 | 5025 |
| 5026 Use, for instance, @code{[(meta button1)]}. For example, here is a common | |
| 5027 setting for Common Lisp programmers who use the bundled @code{ilisp} | |
| 5028 package, whereby meta-button1 on a function name will find the file where | |
| 5029 the function name was defined, and put you at that location in the source | |
| 5030 file. | |
| 5031 | |
| 5032 [Inside a function that gets called by the lisp-mode-hook and | |
| 5033 ilisp-mode-hook] | |
| 5034 | |
| 5035 @lisp | |
| 5036 (local-set-key [(meta button1)] 'edit-definitions-lisp) | |
| 5037 @end lisp | |
| 5038 | |
| 2459 | 5039 @node Q3.1.3, Q3.1.4, Q3.1.2, Editing |
| 2417 | 5040 @unnumberedsubsec Q3.1.3: Clicking the left button does not do anything in buffer list. |
| 428 | 5041 |
| 5042 I do @kbd{C-x C-b} to get a list of buffers and the entries get | |
| 5043 highlighted when I move the mouse over them but clicking the left mouse | |
| 5044 does not do anything. | |
| 5045 | |
| 5046 Use the middle mouse button. | |
| 5047 | |
| 2459 | 5048 @node Q3.1.4, Q3.1.5, Q3.1.3, Editing |
| 2417 | 5049 @unnumberedsubsec Q3.1.4: How can I get a list of buffers when I hit mouse button 3? |
| 428 | 5050 |
| 5051 The following code will replace the default popup on button3: | |
| 5052 | |
| 5053 @lisp | |
| 5054 (global-set-key [button3] 'popup-buffer-menu) | |
| 5055 @end lisp | |
| 5056 | |
| 2459 | 5057 @node Q3.1.5, Q3.2.1, Q3.1.4, Editing |
| 5058 @unnumberedsubsec Q3.1.5: How can I set XEmacs up so that it pastes where the text cursor is? | |
| 428 | 5059 |
| 5060 By default XEmacs pastes X selections where the mouse pointer is. How | |
| 5061 do I disable this? | |
| 5062 | |
| 5063 Examine the function @code{mouse-yank}, by typing @kbd{C-h f mouse-yank | |
| 5064 @key{RET}}. | |
| 5065 | |
| 2417 | 5066 To get XEmacs to paste at the text cursor, add this your @file{init.el}: |
| 428 | 5067 |
| 5068 @lisp | |
| 5069 (setq mouse-yank-at-point t) | |
| 5070 @end lisp | |
| 5071 | |
| 2459 | 5072 You can also change this with Customize. Select from the |
| 5073 @code{Options} menu @code{Advanced | |
| 5074 (Customize)->Emacs->Editing->Mouse->Yank At Point...} or type @kbd{M-x | |
| 5075 customize @key{RET} mouse @key{RET}}. | |
| 5076 | |
| 5077 @unnumberedsec 3.2: Buffers, Text Editing | |
| 5078 | |
| 5079 @node Q3.2.1, Q3.2.2, Q3.1.5, Editing | |
| 5080 @unnumberedsubsec Q3.2.1: Can I have the end of the buffer delimited in some way? | |
| 5081 | |
| 5082 Say, with: @samp{[END]}? | |
| 5083 | |
| 5084 Try this: | |
| 5085 | |
| 5086 @lisp | |
| 5087 (let ((ext (make-extent (point-min) (point-max)))) | |
| 5088 (set-extent-property ext 'start-closed t) | |
| 5089 (set-extent-property ext 'end-closed t) | |
| 5090 (set-extent-property ext 'detachable nil) | |
| 5091 (set-extent-end-glyph ext (make-glyph [string :data "[END]"]))) | |
| 5092 @end lisp | |
| 5093 | |
| 5094 Since this is XEmacs, you can specify an icon to be shown on | |
| 5095 window-system devices. To do so, change the @code{make-glyph} call to | |
| 5096 something like this: | |
| 5097 | |
| 5098 @lisp | |
| 5099 (make-glyph '([xpm :file "~/something.xpm"] | |
| 5100 [string :data "[END]"])) | |
| 5101 @end lisp | |
| 5102 | |
| 5103 You can inline the @sc{xpm} definition yourself by specifying | |
| 5104 @code{:data} instead of @code{:file}. Here is such a full-featured | |
| 5105 version that works on both X and TTY devices: | |
| 5106 | |
| 5107 @lisp | |
| 5108 (let ((ext (make-extent (point-min) (point-max)))) | |
| 5109 (set-extent-property ext 'start-closed t) | |
| 5110 (set-extent-property ext 'end-closed t) | |
| 5111 (set-extent-property ext 'detachable nil) | |
| 5112 (set-extent-end-glyph ext (make-glyph '([xpm :data "\ | |
| 5113 /* XPM */ | |
| 5114 static char* eye = @{ | |
| 5115 \"20 11 7 2\", | |
| 5116 \"__ c None\" | |
| 5117 \"_` c #7f7f7f\", | |
| 5118 \"_a c #fefefe\", | |
| 5119 \"_b c #7f0000\", | |
| 5120 \"_c c #fefe00\", | |
| 5121 \"_d c #fe0000\", | |
| 5122 \"_e c #bfbfbf\", | |
| 5123 \"___________`_`_`___b_b_b_b_________`____\", | |
| 5124 \"_________`_`_`___b_c_c_c_b_b____________\", | |
| 5125 \"_____`_`_`_e___b_b_c_c_c___b___b_______`\", | |
| 5126 \"___`_`_e_a___b_b_d___b___b___b___b______\", | |
| 5127 \"_`_`_e_a_e___b_b_d_b___b___b___b___b____\", | |
| 5128 \"_`_`_a_e_a___b_b_d___b___b___b___b___b__\", | |
| 5129 \"_`_`_e_a_e___b_b_d_b___b___b___b___b_b__\", | |
| 5130 \"___`_`_e_a___b_b_b_d_c___b___b___d_b____\", | |
| 5131 \"_____`_`_e_e___b_b_b_d_c___b_b_d_b______\", | |
| 5132 \"_`_____`_`_`_`___b_b_b_d_d_d_d_b________\", | |
| 5133 \"___`_____`_`_`_`___b_b_b_b_b_b__________\", | |
| 5134 @} ;"] | |
| 5135 [string :data "[END]"])))) | |
| 5136 @end lisp | |
| 5137 | |
| 5138 Note that you might want to make this a function, and put it to a hook. | |
| 5139 We leave that as an exercise for the reader. | |
| 5140 | |
| 5141 @node Q3.2.2, Q3.2.3, Q3.2.1, Editing | |
| 5142 @unnumberedsubsec Q3.2.2: How do I insert today's date into a buffer? | |
| 2417 | 5143 |
| 5144 Like this: | |
| 428 | 5145 |
| 5146 @lisp | |
| 2459 | 5147 (insert (current-time-string)) |
| 2417 | 5148 @end lisp |
| 5149 | |
| 2459 | 5150 @node Q3.2.3, Q3.2.4, Q3.2.2, Editing |
| 5151 @unnumberedsubsec Q3.2.3: How do I get a single minibuffer frame? | |
| 5152 | |
| 5153 @email{acs@@acm.org, Vin Shelton} writes: | |
| 2417 | 5154 |
| 5155 @lisp | |
| 2459 | 5156 (setq initial-frame-plist '(minibuffer nil)) |
| 5157 (setq default-frame-plist '(minibuffer nil)) | |
| 5158 (setq default-minibuffer-frame | |
| 5159 (make-frame | |
| 5160 '(minibuffer only | |
| 5161 width 86 | |
| 5162 height 1 | |
| 5163 menubar-visible-p nil | |
| 5164 default-toolbar-visible-p nil | |
| 5165 name "minibuffer" | |
| 5166 top -2 | |
| 5167 left -2 | |
| 5168 has-modeline-p nil))) | |
| 5169 (frame-notice-user-settings) | |
| 2417 | 5170 @end lisp |
| 5171 | |
| 2459 | 5172 @strong{Please note:} The single minibuffer frame may not be to everyone's |
| 5173 taste, and there any number of other XEmacs options settings that may | |
| 5174 make it difficult or inconvenient to use. | |
| 5175 | |
| 5176 @node Q3.2.4, Q3.2.5, Q3.2.3, Editing | |
| 5177 @unnumberedsubsec Q3.2.4: How can I enable auto-indent and/or Filladapt? | |
| 5178 | |
| 5179 Put the following line in your @file{init.el}: | |
| 428 | 5180 |
| 5181 @lisp | |
| 2459 | 5182 (setq indent-line-function 'indent-relative-maybe) |
| 428 | 5183 @end lisp |
| 5184 | |
| 2459 | 5185 If you want to get fancy, try the @code{filladapt} package available |
| 5186 standard with XEmacs. Put this into your @file{init.el}: | |
| 428 | 5187 |
| 5188 @lisp | |
| 2459 | 5189 (require 'filladapt) |
| 5190 (setq-default filladapt-mode t) | |
| 5191 (add-hook 'c-mode-hook 'turn-off-filladapt-mode) | |
| 428 | 5192 @end lisp |
| 5193 | |
| 2459 | 5194 This will enable Filladapt for all modes except C mode, where it doesn't |
| 5195 work well. To turn Filladapt on only in particular major modes, remove | |
| 5196 the @code{(setq-default ...)} line and use | |
| 5197 @code{turn-on-filladapt-mode}, like this: | |
| 428 | 5198 |
| 5199 @lisp | |
| 2459 | 5200 (add-hook 'text-mode-hook 'turn-on-filladapt-mode) |
| 428 | 5201 @end lisp |
| 2417 | 5202 |
| 2459 | 5203 You can customize filling and adaptive filling with Customize. |
| 5204 Select from the @code{Options} menu | |
| 5205 @code{Advanced (Customize)->Emacs->Editing->Fill->Fill...} | |
| 5206 or type @kbd{M-x customize @key{RET} fill @key{RET}}. | |
| 5207 | |
| 5208 Note that well-behaving text-lookalike modes will run | |
| 5209 @code{text-mode-hook} by default (e.g. that's what Message does). For | |
| 5210 the nasty ones, you'll have to provide the @code{add-hook}s yourself. | |
| 5211 | |
| 5212 Please note that the @code{fa-extras} package is no longer useful. | |
| 5213 | |
| 5214 @node Q3.2.5, Q3.3.1, Q3.2.4, Editing | |
| 5215 @unnumberedsubsec Q3.2.5: How can I get XEmacs to come up in text/auto-fill mode by default? | |
| 5216 | |
| 5217 Try the following lisp in your @file{init.el}: | |
| 2417 | 5218 |
| 5219 @lisp | |
| 2459 | 5220 (setq default-major-mode 'text-mode) |
| 2769 | 5221 (add-hook 'text-mode-hook 'turn-on-auto-fill) |
| 2417 | 5222 @end lisp |
| 5223 | |
| 2459 | 5224 @strong{WARNING}: note that changing the value of |
| 5225 @code{default-major-mode} from @code{fundamental-mode} can break a large | |
| 5226 amount of built-in code that expects newly created buffers to be in | |
| 5227 @code{fundamental-mode}. (Changing from @code{fundamental-mode} to | |
| 5228 @code{text-mode} might not wreak too much havoc, but changing to | |
| 5229 something more exotic like a lisp-mode would break many Emacs packages). | |
| 5230 | |
| 5231 Note that Emacs by default starts up in buffer @code{*scratch*} in | |
| 5232 @code{initial-major-mode}, which defaults to | |
| 5233 @code{lisp-interaction-mode}. Thus adding the following form to your | |
| 5234 Emacs init file will cause the initial @code{*scratch*} buffer to be put | |
| 5235 into auto-fill'ed @code{text-mode}: | |
| 2417 | 5236 |
| 5237 @lisp | |
| 2459 | 5238 (setq initial-major-mode |
| 5239 (lambda () | |
| 5240 (text-mode) | |
| 5241 (turn-on-auto-fill))) | |
| 2417 | 5242 @end lisp |
| 5243 | |
| 2459 | 5244 Note that after your init file is loaded, if |
| 5245 @code{inhibit-startup-message} is @code{nil} (the default) and the | |
| 5246 startup buffer is @code{*scratch*} then the startup message will be | |
| 5247 inserted into @code{*scratch*}; it will be removed after a timeout by | |
| 5248 erasing the entire @code{*scratch*} buffer. Keep in mind this default | |
| 5249 usage of @code{*scratch*} if you desire any prior manipulation of | |
| 5250 @code{*scratch*} from within your Emacs init file. In particular, | |
| 5251 anything you insert into @code{*scratch*} from your init file will be | |
| 5252 later erased. Also, if you change the mode of the @code{*scratch*} | |
| 5253 buffer, be sure that this will not interfere with possible later | |
| 5254 insertion of the startup message (e.g. if you put @code{*scratch*} into | |
| 5255 a nonstandard mode that has automatic font lock rules, then the startup | |
| 5256 message might get fontified in a strange foreign manner, e.g. as code in | |
| 5257 some programming language). | |
| 5258 | |
| 5259 @unnumberedsec 3.3: Text Selections | |
| 5260 | |
| 5261 @node Q3.3.1, Q3.3.2, Q3.2.5, Editing | |
| 5262 @unnumberedsubsec Q3.3.1: How do I select a rectangular region? | |
| 2417 | 5263 |
| 5264 Just select the region normally, then use the rectangle commands (e.g. | |
| 5265 @code{kill-rectangle} on it. The region does not highlight as a | |
| 5266 rectangle, but the commands work just fine. | |
| 5267 | |
| 5268 To actually sweep out rectangular regions with the mouse you can use | |
| 5269 @code{mouse-track-do-rectangle} which is assigned to @kbd{M-button1}. | |
| 5270 Then use rectangle commands. | |
| 5271 | |
| 5272 You can also do the following to change default behavior to sweep out | |
| 5273 rectangular regions: | |
| 5274 | |
| 5275 @lisp | |
| 5276 (setq mouse-track-rectangle-p t) | |
| 5277 @end lisp | |
| 5278 | |
| 2459 | 5279 You can also change this with Customize. |
| 2417 | 5280 Select from the @code{Options} menu |
| 5281 @code{Advanced (Customize)->Emacs->Editing->Mouse->Track Rectangle...} or type | |
| 5282 @kbd{M-x customize @key{RET} mouse @key{RET}}. | |
| 5283 | |
| 5284 | |
| 5285 @example | |
| 5286 mouse-track-do-rectangle: (event) | |
| 5287 -- an interactive compiled Lisp function. | |
| 5288 Like `mouse-track' but selects rectangles instead of regions. | |
| 5289 @end example | |
| 5290 | |
| 2459 | 5291 @node Q3.3.2, Q3.3.3, Q3.3.1, Editing |
| 5292 @unnumberedsubsec Q3.3.2: How can I turn off or change highlighted selections? | |
| 428 | 5293 |
| 5294 The @code{zmacs} mode allows for what some might call gratuitous | |
| 5295 highlighting for selected regions (either by setting mark or by using | |
| 5296 the mouse). This is the default behavior. To turn off, add the | |
| 2417 | 5297 following line to your @file{init.el} file: |
| 428 | 5298 |
| 5299 @lisp | |
| 5300 (setq zmacs-regions nil) | |
| 5301 @end lisp | |
| 5302 | |
| 2417 | 5303 You can also change this with Customize. Select from the |
| 5304 @code{Options} menu | |
| 5305 @code{Advanced (Customize)->Emacs->Editing->Basics->Zmacs Regions} | |
| 5306 or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}. | |
| 5307 | |
| 5308 To change the face for selection, look at @code{Options->Advanced (Customize)} | |
| 5309 on the menubar. | |
| 5310 | |
| 2459 | 5311 @node Q3.3.3, Q3.3.4, Q3.3.2, Editing |
| 5312 @unnumberedsubsec Q3.3.3: How do I cause typing on an active region to remove it? | |
| 428 | 5313 |
| 5314 I want to change things so that if I select some text and start typing, | |
| 5315 the typed text replaces the selected text, similar to Motif. | |
| 5316 | |
| 5317 You want to use something called @dfn{pending delete}. Pending delete | |
| 5318 is what happens when you select a region (with the mouse or keyboard) | |
| 5319 and you press a key to replace the selected region by the key you typed. | |
| 5320 Usually backspace kills the selected region. | |
| 5321 | |
| 2164 | 5322 To get this behavior, ensure that you have the @file{pc} package |
| 5323 installed, and add the following lines to your | |
| 2417 | 5324 @file{init.el}: |
| 428 | 5325 |
| 5326 @lisp | |
| 438 | 5327 (cond |
| 5328 ((fboundp 'turn-on-pending-delete) | |
| 5329 (turn-on-pending-delete)) | |
| 5330 ((fboundp 'pending-delete-on) | |
| 5331 (pending-delete-on t))) | |
| 428 | 5332 @end lisp |
| 5333 | |
| 1138 | 5334 Note that this will work with both Backspace and Delete. This code is a |
| 438 | 5335 tad more complicated than it has to be for XEmacs in order to make it |
| 5336 more portable. | |
| 428 | 5337 |
| 2459 | 5338 @node Q3.3.4, Q3.3.5, Q3.3.3, Editing |
| 5339 @unnumberedsubsec Q3.3.4: Can I turn off the highlight during isearch? | |
| 428 | 5340 |
| 5341 I do not like my text highlighted while I am doing isearch as I am not | |
| 5342 able to see what's underneath. How do I turn it off? | |
| 5343 | |
| 2417 | 5344 Put the following in your @file{init.el}: |
| 428 | 5345 |
| 5346 @lisp | |
| 5347 (setq isearch-highlight nil) | |
| 5348 @end lisp | |
| 5349 | |
| 2459 | 5350 You can also change this with Customize. Type |
| 428 | 5351 @kbd{M-x customize-variable @key{RET} isearch-highlight @key{RET}}. |
| 5352 | |
| 5353 Note also that isearch-highlight affects query-replace and ispell. | |
| 5354 Instead of disabling isearch-highlight you may find that a better | |
| 5355 solution consists of customizing the @code{isearch} face. | |
| 5356 | |
| 2459 | 5357 @node Q3.3.5, Q3.3.6, Q3.3.4, Editing |
| 5358 @unnumberedsubsec Q3.3.5: Why is killing so slow? | |
| 892 | 5359 |
| 5360 This actually is an X Windows question, although you'll notice it with | |
| 5361 keyboard operations as well as while using the GUI. Basically, there | |
| 5362 are four ways to communicate interprogram via the X server: | |
| 5363 | |
| 5364 @table @strong | |
| 5365 @item Primary selection | |
| 5366 a transient selection that gets replaced every time a new selection is made | |
| 5367 | |
| 5368 @item Secondary selection | |
| 5369 for "exchanging" with the primary selection | |
| 5370 | |
| 5371 @item Cut buffers | |
| 5372 a clipboard internal to the X server (deprecated) | |
| 5373 | |
| 5374 @item Clipboard selection | |
| 5375 a selection with a notification protocol that allows a separate app to | |
| 5376 manage the clipboard | |
| 5377 @end table | |
| 5378 | |
| 5379 The cut buffers are deprecated because managing them is even more | |
| 5380 inefficient than the clipboard notification protocol. The primary | |
| 5381 selection works fine for many users and applications, but is not very | |
| 5382 robust under intensive or sophisticated use. | |
| 5383 | |
| 5384 In Motif and MS Windows, a clipboard has become the primary means for | |
| 5385 managing cut and paste. These means that "modern" applications tend to | |
| 5386 be oriented toward a true clipboard, rather than the primary selection. | |
| 5387 (On Windows, there is nothing equivalent to the primary selection.) | |
| 5388 It's not that XEmacs doesn't support the simple primary selection | |
| 5389 method, it's that more and more other applications don't. | |
| 5390 | |
| 5391 So the slowdown occurs because XEmacs now engages in the clipboard | |
| 5392 notification protocol on @emph{every} kill. This is especially slow on | |
| 5393 Motif. | |
| 5394 | |
| 5395 With most people running most clients and server on the same host, and | |
| 5396 many of the rest working over very fast communication, you may expect | |
| 5397 that the situation is not going to improve. | |
| 5398 | |
| 5399 There are a number of workarounds. The most effective is to use a | |
| 5400 special command to do selection ownership only when you intend to paste | |
| 5401 to another application. Useful commands are @code{kill-primary-selection} | |
| 5402 and @code{copy-primary-selection}. These work only on text selected | |
| 5403 with the mouse (probably; experiment), and are bound by default to the | |
| 5404 @kbd{Cut} and @kbd{Copy}, respectively, buttons on the toolbar. | |
| 5405 @code{copy-primary-selection} is also bound to @kbd{C-Insert}. You can | |
| 5406 yank the clipboard contents with @code{yank-primary-selection}, bound to | |
| 5407 the @kbd{Paste} toolbar button and @kbd{Sh-Insert}. | |
| 5408 | |
| 5409 If you are communicating by cut and paste with applications that use the | |
| 5410 primary selection, then you can customize | |
| 5411 @code{interprogram-cut-function} to @code{nil}, restoring the XEmacs | |
| 5412 version 20 behavior. How can you tell if a program will support this? | |
| 5413 Motifly-correct programs require the clipboard; you lose. For others, | |
| 5414 only by trying it. You also need to customize the complementary | |
| 5415 @code{interprogram-paste-function} to @code{nil}. (Otherwise | |
| 5416 XEmacs-to-XEmacs pastes will not work correctly.) | |
| 5417 | |
| 5418 You may get some relief on Motif by setting | |
| 5419 @code{x-selection-strict-motif-ownership} to nil, but this means you will | |
| 5420 only intermittently be able to paste XEmacs kills to Motif applications. | |
| 5421 | |
| 5422 Thanks to Jeff Mincy and Glynn Clements for corrections. | |
| 5423 | |
| 2459 | 5424 @node Q3.3.6, Q3.4.1, Q3.3.5, Editing |
| 5425 @unnumberedsubsec Q3.3.6: Why does @kbd{M-w} take so long? | |
| 2417 | 5426 |
| 5427 It actually doesn't. It leaves the region visible for a second so that | |
| 5428 you can see what area is being yanked. If you start working, though, it | |
| 5429 will immediately complete its operation. In other words, it will only | |
| 5430 delay for a second if you let it. | |
| 5431 | |
| 2459 | 5432 @unnumberedsec 3.4: Editing Source Code |
| 5433 | |
| 5434 @node Q3.4.1, Q3.4.2, Q3.3.6, Editing | |
| 5435 @unnumberedsubsec Q3.4.1: I do not like cc-mode. How do I use the old c-mode? | |
| 2417 | 5436 |
| 5437 Well, first off, consider if you really want to do this. cc-mode is | |
| 5438 much more powerful than the old c-mode. If you're having trouble | |
| 5439 getting your old offsets to work, try using @code{c-set-offset} instead. | |
| 5440 You might also consider using the package @code{cc-compat}. | |
| 5441 | |
| 5442 But, if you still insist, add the following lines to your @file{init.el}: | |
| 5443 | |
| 5444 @lisp | |
| 5445 (fmakunbound 'c-mode) | |
| 5446 (makunbound 'c-mode-map) | |
| 5447 (fmakunbound 'c++-mode) | |
| 5448 (makunbound 'c++-mode-map) | |
| 5449 (makunbound 'c-style-alist) | |
| 5450 (load-library "old-c-mode") | |
| 5451 (load-library "old-c++-mode") | |
| 5452 @end lisp | |
| 5453 | |
| 5454 This must be done before any other reference is made to either c-mode or | |
| 5455 c++-mode. | |
| 5456 | |
| 2459 | 5457 @node Q3.4.2, , Q3.4.1, Editing |
| 5458 @unnumberedsubsec Q3.4.2: How do you make XEmacs indent CL if-clauses correctly? | |
| 2417 | 5459 |
| 5460 I'd like XEmacs to indent all the clauses of a Common Lisp @code{if} the | |
| 5461 same amount instead of indenting the 3rd clause differently from the | |
| 5462 first two. | |
| 5463 | |
| 2459 | 5464 The package @code{cl-indent} that comes with XEmacs sets up this kind |
| 5465 of indentation by default. @code{cl-indent} also knows about many | |
| 5466 other CL-specific forms. To use @code{cl-indent}, one can do this: | |
| 2417 | 5467 |
| 5468 @lisp | |
| 2459 | 5469 (setq lisp-indent-function 'common-lisp-indent-function) |
| 2417 | 5470 @end lisp |
| 5471 | |
| 5472 One can also customize @file{cl-indent.el} so it mimics the default | |
| 5473 @code{if} indentation @code{then} indented more than the @code{else}. | |
| 5474 Here's how: | |
| 5475 | |
| 5476 @lisp | |
| 5477 (put 'if 'common-lisp-indent-function '(nil nil &body)) | |
| 5478 @end lisp | |
| 5479 | |
| 2459 | 5480 @node Display, External Subsystems, Editing, Top |
| 5481 @unnumbered 4 Display Functions | |
| 428 | 5482 |
| 5483 This is part 4 of the XEmacs Frequently Asked Questions list. This | |
| 2459 | 5484 section is devoted to the display-related capabilities of XEmacs |
| 5485 (fonts, colors, modeline, menubar, toolbar, scrollbar, etc.) and how | |
| 5486 to customize them. | |
| 5487 | |
| 5488 @menu | |
| 5489 4.0: Textual Fonts and Colors | |
| 5490 * Q4.0.1:: How do I specify a font? | |
| 5491 * Q4.0.2:: How do I set the text, menu and modeline fonts? | |
| 5492 * Q4.0.3:: How can I set color options from @file{init.el}? | |
| 5493 * Q4.0.4:: How can I set the colors when highlighting a region? | |
| 5494 * Q4.0.5:: How can I limit color map usage? | |
| 5495 * Q4.0.6:: My tty supports color, but XEmacs doesn't use them. | |
| 5496 * Q4.0.7:: Can I have pixmap backgrounds in XEmacs? | |
| 5497 * Q4.0.8:: How do I display non-ASCII characters? | |
| 5498 * Q4.0.9:: Font selections in don't get saved after @code{Save Options}. | |
| 5499 | |
| 5500 4.1: Syntax Highlighting (Font Lock) | |
| 5501 * Q4.1.1:: How can I do source code highlighting using font-lock? | |
| 5502 * Q4.1.2:: How do I get @samp{More} Syntax Highlighting on by default? | |
| 5503 | |
| 5504 4.2: The Modeline | |
| 5505 * Q4.2.1:: How can I make the modeline go away? | |
| 5506 * Q4.2.2:: How do you have XEmacs display the line number in the modeline? | |
| 5507 * Q4.2.3:: How do I get XEmacs to put the time of day on the modeline? | |
| 5508 * Q4.2.4:: How can I change the modeline color based on the mode used? | |
| 5509 | |
| 5510 4.3: The Cursor | |
| 5511 * Q4.3.1:: Is there a way to make the bar cursor thicker? | |
| 5512 * Q4.3.2:: Is there a way to get back the block cursor? | |
| 5513 * Q4.3.3:: Can I make the cursor blink? | |
| 5514 | |
| 5515 4.4: The Menubar | |
| 5516 * Q4.4.1:: How do I get rid of the menubar? | |
| 5517 * Q4.4.2:: How can I customize the menubar? | |
| 5518 * Q4.4.3:: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 5519 * Q4.4.4:: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 5520 * Q4.4.5:: Resources like @code{Emacs*menubar*font} are not working? | |
| 5521 | |
| 5522 4.5: The Toolbar | |
| 5523 * Q4.5.1:: How do I get rid of the toolbar? | |
| 5524 * Q4.5.2:: How can I customize the toolbar? | |
| 5525 * Q4.5.3:: How can I bind a key to a function to toggle the toolbar? | |
| 5526 * Q4.5.4:: @samp{Can't instantiate image error...} in toolbar | |
| 5527 | |
| 5528 4.6: Scrollbars and Scrolling | |
| 5529 * Q4.6.1:: How can I disable the scrollbar? | |
| 5530 * Q4.6.2:: How can I change the scrollbar width? | |
| 5531 * Q4.6.3:: How can I use resources to change scrollbar colors? | |
| 5532 * Q4.6.4:: Moving the scrollbar can move the point; can I disable this? | |
| 5533 * Q4.6.5:: Scrolling one line at a time. | |
| 5534 * Q4.6.6:: How can I turn off automatic horizontal scrolling in specific modes? | |
| 5535 * Q4.6.7:: I find auto-show-mode disconcerting. How do I turn it off? | |
| 5536 | |
| 5537 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 5538 * Q4.7.1:: How can I disable the gutter tabs? | |
| 5539 * Q4.7.2:: How can I disable the progress bar? | |
| 5540 * Q4.7.3:: There are bugs in the gutter or widgets. | |
| 5541 * Q4.7.4:: How can I customize the gutter or gutter tabs? | |
| 5542 @end menu | |
| 5543 | |
| 5544 @unnumberedsec 4.0: Textual Fonts and Colors | |
| 5545 | |
| 5546 @node Q4.0.1, Q4.0.2, Display, Display | |
| 5547 @unnumberedsubsec Q4.0.1: How do I specify a font? | |
| 5548 | |
| 5549 #### Update me. | |
| 5550 | |
| 5551 In 21.4 and above, you can use the @samp{Options} menu to change the font. | |
| 5552 You can also do it in your init file, e.g. like this (for MS Windows): | |
| 5553 | |
| 5554 @display | |
| 5555 (set-face-font 'default "Lucida Console:Regular:10") | |
| 5556 (set-face-font 'modeline "MS Sans Serif:Regular:10") | |
| 5557 @end display | |
| 5558 | |
| 5559 @node Q4.0.2, Q4.0.3, Q4.0.1, Display | |
| 5560 @unnumberedsubsec Q4.0.2: How do I set the text, menu and modeline fonts? | |
| 5561 | |
| 5562 #### Update me. | |
| 5563 | |
| 5564 Note that you should use @samp{Emacs.} and not @samp{Emacs*} when | |
| 5565 setting face values. | |
| 5566 | |
| 5567 In @file{.Xresources}: | |
| 5568 | |
| 5569 @example | |
| 5570 Emacs.default.attributeFont: -*-*-medium-r-*-*-*-120-*-*-m-*-*-* | |
| 5571 Emacs*menubar*font: fixed | |
| 5572 Emacs.modeline.attributeFont: fixed | |
| 5573 @end example | |
| 5574 | |
| 5575 This is confusing because @samp{default} and @samp{modeline} are face | |
| 5576 names, and can be found listed with all faces in the current mode by | |
| 5577 using @kbd{M-x set-face-font (enter) ?}. They use the face-specific | |
| 5578 resource @samp{attributeFont}. | |
| 5579 | |
| 5580 On the other hand, @samp{menubar} is a normal X thing that uses the | |
| 5581 resource @samp{font}. With Motif it @emph{may be} necessary to use | |
| 5582 @samp{fontList} @emph{instead of} @samp{font}. In @emph{non-Motif} | |
| 5583 configurations with Mule it @emph{is} necessary to use @samp{fontSet} | |
| 5584 instead of @samp{font}. (Sorry, there just is no simple recipe here.) | |
| 5585 | |
| 5586 @node Q4.0.3, Q4.0.4, Q4.0.2, Display | |
| 5587 @unnumberedsubsec Q4.0.3: How can I set color options from @file{init.el}? | |
| 5588 | |
| 5589 How can I set the most commonly used color options from my | |
| 5590 @file{init.el} instead of from my @file{.Xresources}? | |
| 5591 | |
| 5592 Like this: | |
| 5593 | |
| 5594 @lisp | |
| 5595 (set-face-background 'default "bisque") ; frame background | |
| 5596 (set-face-foreground 'default "black") ; normal text | |
| 5597 (set-face-background 'zmacs-region "red") ; When selecting w/ | |
| 5598 ; mouse | |
| 5599 (set-face-foreground 'zmacs-region "yellow") | |
| 5600 (set-face-font 'default "*courier-bold-r*120-100-100*") | |
| 5601 (set-face-background 'highlight "blue") ; Ie when selecting | |
| 5602 ; buffers | |
| 5603 (set-face-foreground 'highlight "yellow") | |
| 5604 (set-face-background 'modeline "blue") ; Line at bottom | |
| 5605 ; of buffer | |
| 5606 (set-face-foreground 'modeline "white") | |
| 5607 (set-face-font 'modeline "*bold-r-normal*140-100-100*") | |
| 5608 (set-face-background 'isearch "yellow") ; When highlighting | |
| 5609 ; while searching | |
| 5610 (set-face-foreground 'isearch "red") | |
| 5611 (setq x-pointer-foreground-color "black") ; Adds to bg color, | |
| 5612 ; so keep black | |
| 5613 (setq x-pointer-background-color "blue") ; This is color | |
| 5614 ; you really | |
| 5615 ; want ptr/crsr | |
| 5616 @end lisp | |
| 5617 | |
| 5618 @node Q4.0.4, Q4.0.5, Q4.0.3, Display | |
| 5619 @unnumberedsubsec Q4.0.4: How can I set the colors when highlighting a region? | |
| 5620 | |
| 5621 How can I set the background/foreground colors when highlighting a | |
| 5622 region? | |
| 5623 | |
| 5624 You can change the face @code{zmacs-region} either in your | |
| 5625 @file{.Xresources}: | |
| 5626 | |
| 5627 @example | |
| 5628 Emacs.zmacs-region.attributeForeground: firebrick | |
| 5629 Emacs.zmacs-region.attributeBackground: lightseagreen | |
| 5630 @end example | |
| 5631 | |
| 5632 or in your @file{init.el}: | |
| 5633 | |
| 5634 @lisp | |
| 5635 (set-face-background 'zmacs-region "red") | |
| 5636 (set-face-foreground 'zmacs-region "yellow") | |
| 5637 @end lisp | |
| 5638 | |
| 5639 @node Q4.0.5, Q4.0.6, Q4.0.4, Display | |
| 5640 @unnumberedsubsec Q4.0.5: How can I limit color map usage? | |
| 5641 | |
| 5642 I'm using Netscape (or another color grabber like XEmacs); | |
| 5643 is there any way to limit the number of available colors in the color map? | |
| 5644 | |
| 5645 Answer: No, but you can start Netscape before XEmacs, and it will use | |
| 5646 the closest available color if the colormap is full. You can also limit | |
| 5647 the number of colors Netscape uses, using the flags -mono, -ncols <#> or | |
| 5648 -install (for mono, limiting to <#> colors, or for using a private color | |
| 5649 map). | |
| 5650 | |
| 5651 If you have the money, another solution would be to use a truecolor or | |
| 5652 direct color video. | |
| 5653 | |
| 5654 @node Q4.0.6, Q4.0.7, Q4.0.5, Display | |
| 5655 @unnumberedsubsec Q4.0.6: My tty supports color, but XEmacs doesn't use them. | |
| 5656 | |
| 5657 XEmacs tries to automatically determine whether your tty supports color, | |
| 5658 but sometimes guesses wrong. In that case, you can make XEmacs Do The | |
| 5659 Right Thing using this Lisp code: | |
| 5660 | |
| 5661 @lisp | |
| 5662 (if (eq 'tty (device-type)) | |
| 5663 (set-device-class nil 'color)) | |
| 5664 @end lisp | |
| 5665 | |
| 5666 @node Q4.0.7, Q4.0.8, Q4.0.6, Display | |
| 5667 @unnumberedsubsec Q4.0.7: Can I have pixmap backgrounds in XEmacs? | |
| 5668 @c New | |
| 5669 @email{jvillaci@@wahnsinnig.extreme.indiana.edu, Juan Villacis} writes: | |
| 5670 | |
| 5671 @quotation | |
| 5672 There are several ways to do it. For example, you could specify a | |
| 5673 default pixmap image to use in your @file{~/.Xresources}, e.g., | |
| 5674 | |
| 5675 | |
| 5676 @example | |
| 5677 Emacs*EmacsFrame.default.attributeBackgroundPixmap: /path/to/image.xpm | |
| 5678 @end example | |
| 5679 | |
| 5680 | |
| 5681 and then reload ~/.Xresources and restart XEmacs. Alternatively, | |
| 5682 since each face can have its own pixmap background, a better way | |
| 5683 would be to set a face's pixmap within your XEmacs init file, e.g., | |
| 5684 | |
| 5685 @lisp | |
| 5686 (set-face-background-pixmap 'default "/path/to/image.xpm") | |
| 5687 (set-face-background-pixmap 'bold "/path/to/another_image.xpm") | |
| 5688 @end lisp | |
| 5689 | |
| 5690 and so on. You can also do this interactively via @kbd{M-x edit-faces}. | |
| 5691 | |
| 5692 @end quotation | |
| 5693 | |
| 5694 @node Q4.0.8, Q4.0.9, Q4.0.7, Display | |
| 5695 @unnumberedsubsec Q4.0.8: How do I display non-ASCII characters? | |
| 5696 @c New | |
| 5697 | |
| 5698 If you're using a Mule-enabled XEmacs, then display is automatic. If | |
| 5699 you're not seeing the characters you expect, either (1) you don't have | |
| 5700 appropriate fonts available or (2) XEmacs did not correctly detect the | |
| 5701 coding system (@pxref{Recognize Coding, , , xemacs}). In case (1), | |
| 5702 install fonts as is customary for your platform. In case (2), you | |
| 5703 need to tell XEmacs explicitly what coding systems you're using. | |
| 5704 @ref{Specify Coding, , , xemacs}. | |
| 5705 | |
| 5706 If your XEmacs is not Mule-enabled, and for some reason getting a | |
| 5707 Mule-enabled XEmacs seems like the wrong thing to do, all is not lost. | |
| 5708 You can arrange it by brute force. In @file{event-Xt.c} (suppress the | |
| 5709 urge to look in this file---play Doom instead, because you'll survive | |
| 5710 longer), it is written: | |
| 5711 | |
| 5712 @quotation | |
| 5713 In a non-Mule world, a user can still have a multi-lingual editor, by | |
| 5714 doing @code{(set-face-font "-*-iso8859-2" (current-buffer))} for all | |
| 5715 their Latin-2 buffers, etc. | |
| 5716 @end quotation | |
| 5717 | |
| 5718 For the related problem of @emph{inputting} non-ASCII characters in a | |
| 5719 non-Mule XEmacs, @xref{Q3.0.6, How can you type in special characters | |
| 5720 in XEmacs?}. | |
| 5721 | |
| 5722 @node Q4.0.9, Q4.1.1, Q4.0.8, Display | |
| 5723 @unnumberedsubsec Q4.0.9: Font selections in don't get saved after @code{Save Options}. | |
| 5724 | |
| 5725 @email{mannj@@ll.mit.edu, John Mann} writes: | |
| 5726 | |
| 5727 @quotation | |
| 5728 You have to go to @samp{Options->Menubars} and unselect | |
| 5729 @samp{Frame-Local Font Menu}. If this option is selected, font changes | |
| 5730 are only applied to the @emph{current} frame and do @emph{not} get saved | |
| 5731 when you save options. | |
| 5732 @end quotation | |
| 5733 | |
| 5734 Also, set the following in your @file{init.el}: | |
| 5735 | |
| 5736 @lisp | |
| 5737 (setq options-save-faces t) | |
| 5738 @end lisp | |
| 5739 | |
| 5740 @unnumberedsec 4.1: Syntax Highlighting (Font Lock) | |
| 5741 | |
| 5742 @node Q4.1.1, Q4.1.2, Q4.0.9, Display | |
| 5743 @unnumberedsubsec Q4.1.1: How can I do source code highlighting using font-lock? | |
| 5744 | |
| 5745 For most modes, font-lock is already set up and just needs to be turned | |
| 5746 on. This can be done by adding the line: | |
| 5747 | |
| 5748 @lisp | |
| 5749 (require 'font-lock) | |
| 5750 @end lisp | |
| 5751 | |
| 5752 to your @file{init.el}. (You can turn it on for the | |
| 5753 current buffer and session only by @kbd{M-x font-lock-mode}.) See the | |
| 5754 file @file{etc/sample.init.el} (@file{etc/sample.emacs} in XEmacs | |
| 5755 versions prior to 21.4) for more information. | |
| 5756 | |
| 5757 @c the old way: | |
| 5758 @c (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock) | |
| 5759 @c (add-hook 'dired-mode-hook 'turn-on-font-lock) | |
| 5760 | |
| 5761 See also @code{Syntax Highlighting} from the @code{Options} menu. | |
| 5762 Remember to save options. | |
| 5763 | |
| 5764 @node Q4.1.2, Q4.2.1, Q4.1.1, Display | |
| 5765 @unnumberedsubsec Q4.1.2: How do I get @samp{More} Syntax Highlighting on by default? | |
| 5766 | |
| 5767 Use the following code in your @file{init.el}: | |
| 5768 | |
| 5769 @lisp | |
| 5770 (setq-default font-lock-maximum-decoration t) | |
| 5771 @end lisp | |
| 5772 | |
| 5773 See also @code{Syntax Highlighting} from the @code{Options} menu. | |
| 5774 Remember to save options. | |
| 5775 | |
| 5776 @unnumberedsec 4.2: The Modeline | |
| 5777 | |
| 5778 @node Q4.2.1, Q4.2.2, Q4.1.2, Display | |
| 5779 @unnumberedsubsec Q4.2.1: How can I make the modeline go away? | |
| 5780 | |
| 5781 @lisp | |
| 5782 (set-specifier has-modeline-p nil) | |
| 5783 @end lisp | |
| 5784 | |
| 5785 @node Q4.2.2, Q4.2.3, Q4.2.1, Display | |
| 5786 @unnumberedsubsec Q4.2.2: How do you have XEmacs display the line number in the modeline? | |
| 5787 | |
| 5788 Add the following line to your @file{init.el} file to | |
| 5789 display the line number: | |
| 5790 | |
| 5791 @lisp | |
| 5792 (line-number-mode 1) | |
| 5793 @end lisp | |
| 5794 | |
| 5795 Use the following to display the column number: | |
| 5796 | |
| 5797 @lisp | |
| 5798 (column-number-mode 1) | |
| 5799 @end lisp | |
| 5800 | |
| 5801 Or select from the @code{Options} menu | |
| 5802 @iftex | |
| 5803 @* | |
| 5804 @end iftex | |
| 5805 @code{Advanced (Customize)->Emacs->Editing->Basics->Line Number Mode} | |
| 5806 and/or | |
| 5807 @iftex | |
| 5808 @* | |
| 5809 @end iftex | |
| 5810 @code{Advanced (Customize)->Emacs->Editing->Basics->Column Number Mode} | |
| 5811 | |
| 5812 Or type @kbd{M-x customize @key{RET} editing-basics @key{RET}}. | |
| 5813 | |
| 5814 @node Q4.2.3, Q4.2.4, Q4.2.2, Display | |
| 5815 @unnumberedsubsec Q4.2.3: How do I get XEmacs to put the time of day on the modeline? | |
| 5816 | |
| 5817 Add the following line to your @file{init.el} file to | |
| 5818 display the time: | |
| 5819 | |
| 5820 @lisp | |
| 5821 (display-time) | |
| 5822 @end lisp | |
| 5823 | |
| 5824 See @code{Customize} from the @code{Options} menu for customization. | |
| 5825 | |
| 5826 @node Q4.2.4, Q4.3.1, Q4.2.3, Display | |
| 5827 @unnumberedsubsec Q4.2.4: How can I change the modeline color based on the mode used? | |
| 5828 | |
| 5829 You can use something like the following: | |
| 5830 | |
| 5831 @lisp | |
| 5832 (add-hook 'lisp-mode-hook | |
| 5833 (lambda () | |
| 5834 (set-face-background 'modeline "red" (current-buffer)))) | |
| 5835 @end lisp | |
| 5836 | |
| 5837 Then, when editing a Lisp file (i.e. when in Lisp mode), the modeline | |
| 5838 colors change from the default set in your @file{init.el}. | |
| 5839 The change will only be made in the buffer you just entered (which | |
| 5840 contains the Lisp file you are editing) and will not affect the modeline | |
| 5841 colors anywhere else. | |
| 5842 | |
| 5843 Notes: | |
| 5844 | |
| 5845 @itemize @bullet | |
| 5846 | |
| 5847 @item The hook is the mode name plus @code{-hook}. eg. c-mode-hook, | |
| 5848 c++-mode-hook, emacs-lisp-mode-hook (used for your | |
| 5849 @file{init.el} or a @file{xx.el} file), | |
| 5850 lisp-interaction-mode-hook (the @samp{*scratch*} buffer), | |
| 5851 text-mode-hook, etc. | |
| 5852 | |
| 5853 @item | |
| 5854 Be sure to use @code{add-hook}, not @code{(setq c-mode-hook xxxx)}, | |
| 5855 otherwise you will erase anything that anybody has already put on the | |
| 5856 hook. | |
| 5857 | |
| 5858 @item | |
| 5859 You can also do @code{(set-face-font 'modeline @var{font})}, | |
| 5860 eg. @code{(set-face-font 'modeline "*bold-r-normal*140-100-100*" | |
| 5861 (current-buffer))} if you wish the modeline font to vary based on the | |
| 5862 current mode. | |
| 5863 @end itemize | |
| 5864 | |
| 5865 There are additional modeline faces, @code{modeline-buffer-id}, | |
| 5866 @code{modeline-mousable}, and @code{modeline-mousable-minor-mode}, which | |
| 5867 you may want to customize. | |
| 5868 | |
| 5869 @unnumberedsec 4.3: The Cursor | |
| 5870 | |
| 5871 @node Q4.3.1, Q4.3.2, Q4.2.4, Display | |
| 5872 @unnumberedsubsec Q4.3.1: Is there a way to make the bar cursor thicker? | |
| 5873 | |
| 5874 I'd like to have the bar cursor a little thicker, as I tend to "lose" it | |
| 5875 often. | |
| 5876 | |
| 5877 For a 1 pixel bar cursor, use: | |
| 5878 | |
| 5879 @lisp | |
| 5880 (setq bar-cursor t) | |
| 5881 @end lisp | |
| 5882 | |
| 5883 For a 2 pixel bar cursor, use: | |
| 5884 | |
| 5885 @lisp | |
| 5886 (setq bar-cursor 'anything-else) | |
| 5887 @end lisp | |
| 5888 | |
| 5889 You can also change these with Customize. | |
| 5890 Select from the @code{Options} menu | |
| 5891 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type | |
| 5892 @kbd{M-x customize @key{RET} display @key{RET}}. | |
| 5893 | |
| 5894 You can use a color to make it stand out better: | |
| 5895 | |
| 5896 @example | |
| 5897 Emacs*cursorColor: Red | |
| 5898 @end example | |
| 5899 | |
| 5900 @node Q4.3.2, Q4.3.3, Q4.3.1, Display | |
| 5901 @unnumberedsubsec Q4.3.2: Is there a way to get back the block cursor? | |
| 5902 | |
| 5903 @lisp | |
| 5904 (setq bar-cursor nil) | |
| 5905 @end lisp | |
| 5906 | |
| 5907 You can also change this with Customize. | |
| 5908 Select from the @code{Options} menu | |
| 5909 @code{Advanced (Customize)->Emacs->Environment->Display->Bar Cursor...} or type | |
| 5910 @kbd{M-x customize @key{RET} display @key{RET}}. | |
| 5911 | |
| 5912 @node Q4.3.3, Q4.4.1, Q4.3.2, Display | |
| 5913 @unnumberedsubsec Q4.3.3: Can I make the cursor blink? | |
| 5914 | |
| 5915 Yes, like this: | |
| 5916 | |
| 5917 @lisp | |
| 5918 (blink-cursor-mode) | |
| 5919 @end lisp | |
| 5920 | |
| 5921 This function toggles between a steady cursor and a blinking cursor. | |
| 5922 You may also set this mode from the menu bar by selecting | |
| 5923 @samp{Options->Display->Blinking Cursor}. Remember to save options. | |
| 5924 | |
| 5925 @unnumberedsec 4.4: The Menubar | |
| 5926 | |
| 5927 @node Q4.4.1, Q4.4.2, Q4.3.3, Display | |
| 5928 @unnumberedsubsec Q4.4.1: How do I get rid of the menubar? | |
| 5929 | |
| 5930 @lisp | |
| 5931 (set-specifier menubar-visible-p nil) | |
| 5932 @end lisp | |
| 5933 | |
| 5934 @node Q4.4.2, Q4.4.3, Q4.4.1, Display | |
| 5935 @unnumberedsubsec Q4.4.2: How can I customize the menubar? | |
| 5936 | |
| 5937 For an extensive menubar, add this line to your @file{init.el}: | |
| 5938 | |
| 5939 @lisp | |
| 5940 (load "big-menubar") | |
| 5941 @end lisp | |
| 5942 | |
| 5943 If you'd like to write your own, this file provides as good a set of | |
| 5944 examples as any to start from. The file is located in edit-utils | |
| 5945 package. | |
| 5946 | |
| 5947 @node Q4.4.3, Q4.4.4, Q4.4.2, Display | |
| 5948 @unnumberedsubsec Q4.4.3: How do I enable use of the keyboard (@kbd{Alt}) to access menu items? | |
| 5949 | |
| 5950 #### Write me. | |
| 5951 | |
| 5952 @node Q4.4.4, Q4.4.5, Q4.4.3, Display | |
| 5953 @unnumberedsubsec Q4.4.4: How do I control how many buffers are listed in the menu @code{Buffers List}? | |
| 5954 | |
| 5955 Add the following to your @file{init.el} (suit to fit): | |
| 5956 | |
| 5957 @lisp | |
| 5958 (setq buffers-menu-max-size 20) | |
| 5959 @end lisp | |
| 5960 | |
| 5961 For no limit, use an argument of @samp{nil}. | |
| 5962 | |
| 5963 You can also change this with Customize. Select from the | |
| 5964 @code{Options} menu | |
| 5965 @code{Advanced (Customize)->Emacs->Environment->Menu->Buffers Menu->Max Size...} | |
| 5966 or type @kbd{M-x customize @key{RET} buffers-menu @key{RET}}. | |
| 5967 | |
| 5968 @node Q4.4.5, Q4.5.1, Q4.4.4, Display | |
| 5969 @unnumberedsubsec Q4.4.5: Resources like @code{Emacs*menubar*font} are not working? | |
| 5970 | |
| 5971 I am trying to use a resource like @code{Emacs*menubar*font} to set the | |
| 5972 font of the menubar but it's not working. | |
| 5973 | |
| 5974 In Motif, the use of @samp{font} resources is obsoleted in order to | |
| 5975 support internationalization. If you are using the real Motif menubar, | |
| 5976 this resource is not recognized at all; you have to say: | |
| 5977 | |
| 5978 @example | |
| 5979 Emacs*menubar*fontList: FONT | |
| 5980 @end example | |
| 5981 | |
| 5982 If you are using the Lucid menubar, for backward compatibility with | |
| 5983 existing user configurations, the @samp{font} resource is recognized. | |
| 5984 Since this is not supported by Motif itself, the code is a kludge and | |
| 5985 the @samp{font} resource will be recognized only if the @samp{fontList} | |
| 5986 resource resource is unset. This means that the resource | |
| 5987 | |
| 5988 @example | |
| 5989 *fontList: FONT | |
| 5990 @end example | |
| 5991 | |
| 5992 will override | |
| 5993 | |
| 5994 @example | |
| 5995 Emacs*menubar*font: FONT | |
| 5996 @end example | |
| 5997 | |
| 5998 even though the latter is more specific. | |
| 5999 | |
| 6000 In non-Motif configurations using @samp{--with-mule} and | |
| 6001 @samp{--with-xfs} it @emph{is} necessary to use the @code{fontSet} | |
| 6002 resource @emph{instead of} the @code{font} resource. The backward | |
| 6003 compatibility kludge was never implemented for non-Motif builds. | |
| 6004 Example: | |
| 6005 | |
| 6006 @example | |
| 6007 *fontSet: FONT | |
| 6008 @end example | |
| 6009 | |
| 6010 @unnumberedsec 4.5: The Toolbar | |
| 6011 | |
| 6012 @node Q4.5.1, Q4.5.2, Q4.4.5, Display | |
| 6013 @unnumberedsubsec Q4.5.1: How do I get rid of the toolbar? | |
| 6014 | |
| 6015 #### Write me. | |
| 6016 | |
| 6017 @node Q4.5.2, Q4.5.3, Q4.5.1, Display | |
| 6018 @unnumberedsubsec Q4.5.2: How can I customize the toolbar? | |
| 6019 | |
| 6020 #### Write me. | |
| 6021 | |
| 6022 @node Q4.5.3, Q4.5.4, Q4.5.2, Display | |
| 6023 @unnumberedsubsec Q4.5.3: How can I bind a key to a function to toggle the toolbar? | |
| 6024 | |
| 6025 Try something like: | |
| 6026 | |
| 6027 @lisp | |
| 6028 (defun my-toggle-toolbar () | |
| 6029 (interactive) | |
| 6030 (set-specifier default-toolbar-visible-p | |
| 6031 (not (specifier-instance default-toolbar-visible-p)))) | |
| 6032 (global-set-key "\C-xT" 'my-toggle-toolbar) | |
| 6033 @end lisp | |
| 6034 | |
| 6035 @ignore | |
| 6036 @c Probably not relevant any more | |
| 6037 There are redisplay bugs in 19.14 that may make the preceding result in | |
| 6038 a messed-up display, especially for frames with multiple windows. You | |
| 6039 may need to resize the frame before XEmacs completely realizes the | |
| 6040 toolbar is really gone. | |
| 6041 @end ignore | |
| 6042 | |
| 6043 Thanks to @email{martin@@xemacs.org, Martin Buchholz} for the correct | |
| 6044 code. | |
| 6045 | |
| 6046 @node Q4.5.4, Q4.6.1, Q4.5.3, Display | |
| 6047 @unnumberedsubsec Q4.5.4: @samp{Can't instantiate image error...} in toolbar | |
| 6048 | |
| 6049 @email{expt@@alanine.ram.org, Dr. Ram Samudrala} writes: | |
| 6050 | |
| 6051 I just installed the XEmacs (20.4-2) RPMS that I downloaded from | |
| 6052 @uref{http://www.xemacs.org/}. Everything works fine, except that when | |
| 6053 I place my mouse over the toolbar, it beeps and gives me this message: | |
| 6054 | |
| 6055 @example | |
| 6056 Can't instantiate image (probably cached): | |
| 6057 [xbm :mask-file "/usr/include/X11/bitmaps/leftptrmsk :mask-data | |
| 6058 (16 16 <strange control characters> ... | |
| 6059 @end example | |
| 6060 | |
| 6061 @email{kyle_jones@@wonderworks.com, Kyle Jones} writes: | |
| 6062 @quotation | |
| 6063 This is problem specific to some Chips and Technologies video | |
| 6064 chips, when running XFree86. Putting | |
| 6065 | |
| 6066 @code{Option "sw_cursor"} | |
| 6067 | |
| 6068 in @file{XF86Config} gets rid of the problem. | |
| 6069 @end quotation | |
| 6070 | |
| 6071 @unnumberedsec 4.6: Scrollbars and Scrolling | |
| 6072 | |
| 6073 @node Q4.6.1, Q4.6.2, Q4.5.4, Display | |
| 6074 @unnumberedsubsec Q4.6.1: How can I disable the scrollbar? | |
| 6075 | |
| 6076 To disable them for all frames, add the following line to | |
| 6077 your @file{.Xresources}: | |
| 6078 | |
| 6079 @example | |
| 6080 Emacs.scrollBarWidth: 0 | |
| 6081 @end example | |
| 6082 | |
| 6083 Or select @samp{Options->Display->Scrollbars}. | |
| 6084 Remember to save options. | |
| 6085 | |
| 6086 To turn the scrollbar off on a per-frame basis, use the following | |
| 6087 function: | |
| 6088 | |
| 6089 @lisp | |
| 6090 (set-specifier scrollbar-width 0 (selected-frame)) | |
| 6091 @end lisp | |
| 6092 | |
| 6093 You can actually turn the scrollbars on at any level you want by | |
| 6094 substituting for (selected-frame) in the above command. For example, to | |
| 6095 turn the scrollbars off only in a single buffer: | |
| 6096 | |
| 6097 @lisp | |
| 6098 (set-specifier scrollbar-width 0 (current-buffer)) | |
| 6099 @end lisp | |
| 6100 | |
| 6101 @node Q4.6.2, Q4.6.3, Q4.6.1, Display | |
| 6102 @unnumberedsubsec Q4.6.2: How can I change the scrollbar width? | |
| 6103 | |
| 6104 #### Write me. | |
| 6105 | |
| 6106 @node Q4.6.3, Q4.6.4, Q4.6.2, Display | |
| 6107 @unnumberedsubsec Q4.6.3: How can I use resources to change scrollbar colors? | |
| 6108 | |
| 6109 Here's a recap of how to use resources to change your scrollbar colors: | |
| 6110 | |
| 6111 @example | |
| 6112 ! Motif scrollbars | |
| 6113 | |
| 6114 Emacs*XmScrollBar.Background: skyblue | |
| 6115 Emacs*XmScrollBar.troughColor: lightgray | |
| 6116 | |
| 6117 ! Athena scrollbars | |
| 6118 | |
| 6119 Emacs*Scrollbar.Foreground: skyblue | |
| 6120 Emacs*Scrollbar.Background: lightgray | |
| 6121 @end example | |
| 6122 | |
| 6123 Note the capitalization of @code{Scrollbar} for the Athena widget. | |
| 6124 | |
| 6125 @node Q4.6.4, Q4.6.5, Q4.6.3, Display | |
| 6126 @unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this? | |
| 6127 | |
| 6128 When I move the scrollbar in an XEmacs window, it moves the point as | |
| 6129 well, which should not be the default behavior. Is this a bug or a | |
| 6130 feature? Can I disable it? | |
| 6131 | |
| 6132 The current behavior is a feature, not a bug. Point remains at the same | |
| 6133 buffer position as long as that position does not scroll off the screen. | |
| 6134 In that event, point will end up in either the upper-left or lower-left | |
| 6135 hand corner. | |
| 6136 | |
| 6137 This cannot be changed. | |
| 6138 | |
| 6139 @node Q4.6.5, Q4.6.6, Q4.6.4, Display | |
| 6140 @unnumberedsubsec Q4.6.5: Scrolling one line at a time. | |
| 6141 | |
| 6142 Can the cursor keys scroll the screen a line at a time, rather than the | |
| 6143 default half page jump? I tend it to find it disorienting. | |
| 6144 | |
| 6145 Use the following: | |
| 6146 | |
| 6147 @lisp | |
| 6148 (setq scroll-step 1) | |
| 6149 @end lisp | |
| 6150 | |
| 6151 You can also change this with Customize. Select from the | |
| 6152 @code{Options} menu | |
| 6153 @code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...} | |
| 6154 or type @kbd{M-x customize @key{RET} windows @key{RET}}. | |
| 6155 | |
| 6156 @node Q4.6.6, Q4.6.7, Q4.6.5, Display | |
| 6157 @unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes? | |
| 6158 | |
| 6159 Do @code{(setq truncate-lines t)} in the mode-hooks for any modes | |
| 6160 in which you want lines truncated. | |
| 6161 | |
| 6162 More precisely: If @code{truncate-lines} is nil, horizontal scrollbars | |
| 6163 will never appear. Otherwise, they will appear only if the value of | |
| 6164 @code{scrollbar-height} for that buffer/window/etc. is non-zero. If you | |
| 6165 do | |
| 6166 | |
| 6167 @lisp | |
| 6168 (set-specifier scrollbar-height 0) | |
| 6169 @end lisp | |
| 6170 | |
| 6171 then horizontal scrollbars will not appear in truncated buffers unless | |
| 6172 the package specifically asked for them. | |
| 6173 | |
| 6174 @node Q4.6.7, Q4.7.1, Q4.6.6, Display | |
| 6175 @unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off? | |
| 6176 | |
| 6177 @code{auto-show-mode} controls whether or not a horizontal scrollbar | |
| 6178 magically appears when a line is too long to be displayed. This is | |
| 6179 enabled by default. To turn it off, put the following in your | |
| 6180 @file{init.el}: | |
| 6181 | |
| 6182 @lisp | |
| 6183 (setq auto-show-mode nil) | |
| 6184 (setq-default auto-show-mode nil) | |
| 6185 @end lisp | |
| 6186 | |
| 6187 @unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets | |
| 6188 | |
| 6189 @node Q4.7.1, Q4.7.2, Q4.6.7, Display | |
| 6190 @unnumberedsubsec Q4.7.1: How can I disable the gutter tabs? | |
| 6191 | |
| 6192 #### Write me. | |
| 6193 | |
| 6194 @node Q4.7.2, Q4.7.3, Q4.7.1, Display | |
| 6195 @unnumberedsubsec Q4.7.2: How can I disable the progress bar? | |
| 6196 | |
| 6197 #### Write me. | |
| 6198 | |
| 6199 @node Q4.7.3, Q4.7.4, Q4.7.2, Display | |
| 6200 @unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets. | |
| 6201 | |
| 6202 #### Write me. | |
| 6203 | |
| 6204 @node Q4.7.4, , Q4.7.3, Display | |
| 6205 @unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs? | |
| 6206 | |
| 6207 #### Write me. | |
| 6208 | |
| 6209 @node External Subsystems, Internet, Display, Top | |
| 6210 @unnumbered 5 Interfacing with the Operating System and External Devices | |
| 6211 | |
| 6212 This is part 5 of the XEmacs Frequently Asked Questions list. This | |
| 2417 | 6213 section is devoted to the various ways that XEmacs interfaces with the |
| 6214 operating system, with other processes and with external devices such | |
| 6215 as speakers and the printer. | |
| 428 | 6216 |
| 6217 @menu | |
| 2459 | 6218 5.0: X Window System and Resources |
| 6219 * Q5.0.1:: Where is a list of X resources? | |
| 6220 * Q5.0.2:: How can I detect a color display? | |
| 6221 * Q5.0.3:: How can I get the icon to just say @samp{XEmacs}? | |
| 6222 * Q5.0.4:: How can I have the window title area display the full path? | |
| 6223 * Q5.0.5:: @samp{xemacs -name junk} doesn't work? | |
| 6224 * 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
|
6225 * Q5.0.7:: How can I use antialiased fonts under X11? |
| 2459 | 6226 |
| 6227 5.1: Microsoft Windows | |
| 6228 * Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? | |
| 6229 * Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 6230 | |
| 6231 5.2: Printing | |
| 6232 * Q5.2.1:: What do I need to change to make printing work? | |
| 6233 * Q5.2.2:: How can I print WYSIWYG a font-locked buffer? | |
| 6234 * Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 6235 * Q5.2.4:: Can you print under MS Windows? | |
| 6236 | |
| 6237 5.3: Sound | |
| 6238 * Q5.3.1:: How do I turn off the sound? | |
| 6239 * Q5.3.2:: How do I get funky sounds instead of a boring beep? | |
| 6240 * Q5.3.3:: What are NAS and ESD (EsounD)? | |
| 6241 * Q5.3.4:: Sunsite sounds don't play. | |
| 6242 | |
| 6243 5.4: Running an Interior Shell, Invoking Subprocesses | |
| 6244 * Q5.4.1:: What is an interior shell? | |
| 6245 * Q5.4.2:: How do I start up a second shell buffer? | |
| 6246 * Q5.4.3:: Telnet from shell filters too much | |
| 6247 * Q5.4.4:: Strange things are happening in Shell Mode. | |
| 6248 * Q5.4.5:: XEmacs complains "No such file or directory, diff" | |
| 2995 | 6249 * Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed" |
| 2459 | 6250 |
| 6251 5.5: Multiple Device Support | |
| 6252 * Q5.5.1:: How do I open a frame on another screen of my multi-headed display? | |
| 6253 * Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 6254 * Q5.5.3:: How do I disable gnuserv from opening a new frame? | |
| 6255 * Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 6256 * Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 428 | 6257 @end menu |
| 6258 | |
| 2459 | 6259 @unnumberedsec 5.0: X Window System and Resources |
| 6260 | |
| 6261 @node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems | |
| 6262 @unnumberedsubsec Q5.0.1: Where is a list of X resources? | |
| 2417 | 6263 |
| 6264 Search through the @file{NEWS} file for @samp{X Resources}. A fairly | |
| 6265 comprehensive list is given after it. | |
| 6266 | |
| 6267 In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is | |
| 6268 supplied, listing the defaults. The file @file{etc/sample.Xresources} | |
| 6269 gives a different set of defaults that you might consider for | |
| 6270 installation in your @file{~/.Xresources} file. It is nearly the same | |
| 6271 as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about | |
| 6272 installing the contents of this file into your @file{.Xresources} (or | |
| 6273 legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well. | |
| 6274 | |
| 2459 | 6275 @node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems |
| 6276 @unnumberedsubsec Q5.0.2: How can I detect a color display? | |
| 2417 | 6277 |
| 6278 You can test the return value of the function @code{(device-class)}, as | |
| 6279 in: | |
| 6280 | |
| 6281 @lisp | |
| 6282 (when (eq (device-class) 'color) | |
| 6283 (set-face-foreground 'font-lock-comment-face "Grey") | |
| 6284 (set-face-foreground 'font-lock-string-face "Red") | |
| 6285 .... | |
| 6286 ) | |
| 6287 @end lisp | |
| 6288 | |
| 2459 | 6289 @node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems |
| 6290 @unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}? | |
| 2417 | 6291 |
| 6292 I'd like the icon to just say @samp{XEmacs}, and not include the name of | |
| 6293 the current file in it. | |
| 6294 | |
| 6295 Add the following line to your @file{init.el}: | |
| 6296 | |
| 6297 @lisp | |
| 6298 (setq frame-icon-title-format "XEmacs") | |
| 6299 @end lisp | |
| 6300 | |
| 2459 | 6301 @node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems |
| 6302 @unnumberedsubsec Q5.0.4: How can I have the window title area display the full path? | |
| 2417 | 6303 |
| 6304 I'd like to have the window title area display the full directory/name | |
| 6305 of the current buffer file and not just the name. | |
| 6306 | |
| 6307 Add the following line to your @file{init.el}: | |
| 6308 | |
| 6309 @lisp | |
| 6310 (setq frame-title-format "%S: %f") | |
| 6311 @end lisp | |
| 6312 | |
| 6313 A more sophisticated title might be: | |
| 6314 | |
| 6315 @lisp | |
| 6316 (setq frame-title-format | |
| 6317 '("%S: " (buffer-file-name "%f" | |
| 6318 (dired-directory dired-directory "%b")))) | |
| 6319 @end lisp | |
| 6320 | |
| 6321 That is, use the file name, or the dired-directory, or the buffer name. | |
| 6322 | |
| 2459 | 6323 @node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems |
| 6324 @unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work? | |
| 2417 | 6325 |
| 6326 When I run @samp{xterm -name junk}, I get an xterm whose class name | |
| 6327 according to xprop, is @samp{junk}. This is the way it's supposed to | |
| 6328 work, I think. When I run @samp{xemacs -name junk} the class name is | |
| 6329 not set to @samp{junk}. It's still @samp{emacs}. What does | |
| 6330 @samp{xemacs -name} really do? The reason I ask is that my window | |
| 6331 manager (fvwm) will make a window sticky and I use XEmacs to read my | |
| 6332 mail. I want that XEmacs window to be sticky, without having to use the | |
| 6333 window manager's function to set the window sticky. What gives? | |
| 6334 | |
| 6335 @samp{xemacs -name} sets the application name for the program (that is, | |
| 6336 the thing which normally comes from @samp{argv[0]}). Using @samp{-name} | |
| 6337 is the same as making a copy of the executable with that new name. The | |
| 6338 @code{WM_CLASS} property on each frame is set to the frame-name, and the | |
| 6339 application-class. So, if you did @samp{xemacs -name FOO} and then | |
| 6340 created a frame named @var{BAR}, you'd get an X window with WM_CLASS = | |
| 6341 @code{( "BAR", "Emacs")}. However, the resource hierarchy for this | |
| 6342 widget would be: | |
| 6343 | |
| 6344 @example | |
| 6345 Name: FOO .shell .container .BAR | |
| 6346 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame | |
| 6347 @end example | |
| 6348 | |
| 6349 instead of the default | |
| 6350 | |
| 6351 @example | |
| 6352 Name: xemacs.shell .container .emacs | |
| 6353 Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame | |
| 6354 @end example | |
| 6355 | |
| 6356 | |
| 6357 It is arguable that the first element of WM_CLASS should be set to the | |
| 6358 application-name instead of the frame-name, but I think that's less | |
| 6359 flexible, since it does not give you the ability to have multiple frames | |
| 6360 with different WM_CLASS properties. Another possibility would be for | |
| 6361 the default frame name to come from the application name instead of | |
| 6362 simply being @samp{emacs}. However, at this point, making that change | |
| 6363 would be troublesome: it would mean that many users would have to make | |
| 6364 yet another change to their resource files (since the default frame name | |
| 6365 would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever | |
| 6366 the executable happened to be named), so we'd rather avoid it. | |
| 6367 | |
| 6368 To make a frame with a particular name use: | |
| 6369 | |
| 6370 @lisp | |
| 6371 (make-frame '((name . "the-name"))) | |
| 6372 @end lisp | |
| 6373 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6374 @node Q5.0.6, Q5.0.7, Q5.0.5, External Subsystems |
| 2459 | 6375 @unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work. |
| 2417 | 6376 |
| 6377 When I start up XEmacs using @samp{-iconic} it doesn't work right. | |
| 6378 Using @samp{-unmapped} on the command line, and setting the | |
| 6379 @code{initiallyUnmapped} X Resource don't seem to help much either... | |
| 6380 | |
| 6381 @email{ben@@xemacs.org, Ben Wing} writes: | |
| 6382 | |
| 6383 @quotation | |
| 6384 Ugh, this stuff is such an incredible mess that I've about given up | |
| 6385 getting it to work. The principal problem is numerous window-manager | |
| 6386 bugs... | |
| 6387 @end quotation | |
| 6388 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6389 @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
|
6390 @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
|
6391 |
|
4509
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6392 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
|
6393 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
|
6394 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
|
6395 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
|
6396 following configure options, plus any others you normally use: |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6397 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6398 @samp{--enable-mule --with-xft=emacs,menubars} |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6399 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6400 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
|
6401 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
|
6402 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
|
6403 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
|
6404 @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
|
6405 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
|
6406 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
|
6407 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
|
6408 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
|
6409 prequisites. |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6410 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6411 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
|
6412 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
|
6413 |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6414 @example |
|
4509
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6415 XEmacs.default.attributeFont: monospace-12 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6416 XEmacs.bold.attributeFont: monospace-12:style=Bold |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6417 XEmacs.italic.attributeFont: monospace-12:style=Oblique |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6418 XEmacs.bold-italic.attributeFont: monospace-12:style=Bold Oblique |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6419 XEmacs.modeline.attributeFont: sans-serif-11 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6420 XEmacs.menubar.xftFont: sans-serif-11 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6421 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
|
6422 @end example |
|
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6423 |
|
4509
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6424 @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
|
6425 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
|
6426 that, but this @emph{is} beta software!) |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6427 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6428 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
|
6429 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
|
6430 @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
|
6431 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
|
6432 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
|
6433 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
|
6434 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
|
6435 |
|
dd12adb12b8f
Fix broken Xft FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4505
diff
changeset
|
6436 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
|
6437 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
|
6438 Lisp. |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6439 |
| 2459 | 6440 @unnumberedsec 5.1: Microsoft Windows |
| 6441 | |
|
4505
a5f1da0eb001
Document XFT support in the FAQ, better describe XEmacs pronunciation.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4311
diff
changeset
|
6442 @node Q5.1.1, Q5.1.2, Q5.0.7, External Subsystems |
| 2459 | 6443 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? |
| 2417 | 6444 |
| 6445 In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*} | |
| 6446 symbols to @samp{w32-*}. Does XEmacs do the same? | |
| 6447 | |
| 6448 We consider such a move counter-productive, thus we do not use the | |
| 6449 @samp{w32} prefix. (His rather questionable justification was that he | |
| 6450 did not consider Windows to be a "winning" platform.) However, the name | |
| 6451 @samp{Win32} is not particularly descriptive outside the Windows world, | |
| 6452 and using just @samp{windows-} would be too generic. So we chose a | |
| 6453 compromise, the prefix @samp{mswindows-} for Windows-related variables | |
| 6454 and functions. | |
| 6455 | |
| 6456 Thus all the XEmacs variables and functions directly related to either | |
| 6457 the Windows GUI or OS are prefixed @samp{mswindows-} (except for a | |
| 6458 couple of debugging variables, prefixed @samp{debug-mswindows-}). From | |
| 6459 an architectural perspective, however, we believe that this is mostly a | |
| 6460 non-issue because there should be a very small number of | |
| 6461 window-systems-specific variables anyway. Whenever possible, we try to | |
| 6462 provide generic interfaces that apply to all window systems. | |
| 6463 | |
| 6464 @c not true: | |
| 6465 @c The user variables | |
| 6466 @c that share functionality with existing NT Emacs variables are be named | |
| 6467 @c with our convention, but we provide the GNU Emacs names as | |
| 6468 @c compatibility aliases. | |
| 6469 | |
| 2459 | 6470 @node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems |
| 6471 @unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs? | |
| 2417 | 6472 |
| 6473 @unnumberedsubsubsec Associating a new file type with XEmacs. | |
| 6474 | |
| 6475 In Explorer select @samp{View->Options->File Types}, press @samp{[New | |
| 6476 Type...]} and fill in the dialog box, e.g.: | |
| 6477 | |
| 6478 @example | |
| 6479 Description of type: Emacs Lisp source | |
| 6480 Associated extension: el | |
| 6481 Content Type (MIME): text/plain | |
| 6482 @end example | |
| 6483 | |
| 6484 then press @samp{[New...]} and fill in the @samp{Action} dialog box as | |
| 6485 follows: | |
| 6486 | |
| 6487 @example | |
| 6488 Action: | |
| 6489 Open | |
| 6490 | |
| 6491 Application used to perform action: | |
| 6492 D:\Full\path\for\xemacs.exe "%1" | |
| 6493 | |
| 6494 [x] Use DDE | |
| 6495 | |
| 6496 DDE Message: | |
| 6497 open("%1") | |
| 6498 | |
| 6499 Application: | |
| 6500 <leave blank> | |
| 6501 | |
| 6502 DDE Application Not Running: | |
| 6503 <leave blank> | |
| 6504 | |
| 6505 Topic: | |
| 6506 <leave blank> | |
| 6507 @end example | |
| 6508 | |
| 6509 @unnumberedsubsubsec Associating an existing file type with XEmacs. | |
| 6510 | |
| 6511 In Explorer select @samp{View->Options->File Types}. Click on the file | |
| 6512 type in the list and press @samp{[Edit...]}. If the file type already | |
| 6513 has an @samp{Open} action, double click on it and fill in the | |
| 6514 @samp{Action} dialog box as described above; otherwise create a new | |
| 6515 action. | |
| 6516 | |
| 6517 If the file type has more than one action listed, you probably want to | |
| 6518 make the @samp{Open} action that you just edited the default by clicking on | |
| 6519 it and pressing @samp{Set Default}. | |
| 6520 | |
| 6521 Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types} | |
| 6522 using @samp{Control Panel->Folder Options->File Types}. | |
| 6523 | |
| 2459 | 6524 @unnumberedsec 5.2: Printing |
| 6525 | |
| 6526 @node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems | |
| 6527 @unnumberedsubsec Q5.2.1: What do I need to change to make printing work? | |
| 2417 | 6528 |
| 6529 For regular printing there are two variables that can be customized. | |
| 6530 | |
| 6531 @table @code | |
| 6532 @item lpr-command | |
| 6533 This should be set to a command that takes standard input and sends | |
| 6534 it to a printer. Something like: | |
| 6535 | |
| 6536 @lisp | |
| 6537 (setq lpr-command "lp") | |
| 6538 @end lisp | |
| 6539 | |
| 6540 @item lpr-switches | |
| 6541 This should be set to a list that contains whatever the print command | |
| 6542 requires to do its job. Something like: | |
| 6543 | |
| 6544 @lisp | |
| 6545 (setq lpr-switches '("-depson")) | |
| 6546 @end lisp | |
| 6547 @end table | |
| 6548 | |
| 6549 For postscript printing there are three analogous variables to | |
| 6550 customize. | |
| 6551 | |
| 6552 @table @code | |
| 6553 @item ps-lpr-command | |
| 6554 This should be set to a command that takes postscript on standard input | |
| 6555 and directs it to a postscript printer. | |
| 6556 | |
| 6557 @item ps-lpr-switches | |
| 6558 This should be set to a list of switches required for | |
| 6559 @code{ps-lpr-command} to do its job. | |
| 6560 | |
| 6561 @item ps-print-color-p | |
| 6562 This boolean variable should be set @code{t} if printing will be done in | |
| 6563 color, otherwise it should be set to @code{nil}. | |
| 6564 @end table | |
| 6565 | |
| 6566 NOTE: It is an undocumented limitation in XEmacs that postscript | |
| 6567 printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a | |
| 6568 window system environment. It cannot be used outside of X11. | |
| 6569 | |
| 2459 | 6570 @node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems |
| 6571 @unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer? | |
| 2417 | 6572 |
| 6573 Font-lock looks nice. How can I print (WYSIWYG) the highlighted | |
| 6574 document? | |
| 6575 | |
| 6576 The package @code{ps-print}, which is now included with XEmacs, provides | |
| 6577 the ability to do this. The source code contains complete instructions | |
| 6578 on its use, in | |
|
5551
40a52efbf3a3
Reflect change of location of packages to share/
Mike Sperber <sperber@deinprogramm.de>
parents:
5390
diff
changeset
|
6579 @file{$prefix/share/xemacs/xemacs-packages/lisp/ps-print/ps-print.el}, |
| 2417 | 6580 being the default location of an installed ps-print package. |
| 6581 | |
| 2459 | 6582 @node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems |
| 6583 @unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer. | |
| 2417 | 6584 |
| 6585 My printer is a Postscript printer and @code{lpr} only works for | |
| 6586 Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x | |
| 6587 lpr-buffer} to work? | |
| 6588 | |
| 6589 Put something like this in your @file{init.el}: | |
| 428 | 6590 |
| 6591 @lisp | |
| 2417 | 6592 (setq lpr-command "a2ps") |
| 6593 (setq lpr-switches '("-p" "-1")) | |
| 6594 @end lisp | |
| 6595 | |
| 6596 If you don't use a2ps to convert ASCII to postscript (why not, it's | |
| 6597 free?), replace with the command you do use. Note also that some | |
| 6598 versions of a2ps require a @samp{-Pprinter} to ensure spooling. | |
| 6599 | |
| 2459 | 6600 @node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems |
| 6601 @unnumberedsubsec Q5.2.4: Can you print under MS Windows? | |
| 2417 | 6602 |
| 6603 As of 21.4, printing works on Windows, using simply | |
| 6604 @samp{File->Print BUFFER...}, and can be configured with | |
| 6605 @samp{File->Page Setup...}. | |
| 6606 | |
| 6607 Prior to 21.4, there is no built-in support, but there are some clever | |
| 6608 hacks out there. If you know how, please let us know and we'll put it | |
| 6609 here. | |
| 6610 | |
| 2459 | 6611 @unnumberedsec 5.3: Sound |
| 6612 | |
| 6613 @node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems | |
| 6614 @unnumberedsubsec Q5.3.1: How do I turn off the sound? | |
| 2417 | 6615 |
| 6616 Add the following line to your @file{init.el}: | |
| 6617 | |
| 6618 @lisp | |
| 6619 (setq bell-volume 0) | |
| 6620 (setq sound-alist nil) | |
| 6621 @end lisp | |
| 6622 | |
| 6623 That will make your XEmacs totally silent---even the default ding sound | |
| 6624 (TTY beep on TTY-s) will be gone. | |
| 6625 | |
| 6626 You can also change these with Customize. Select from the | |
| 6627 @code{Options} menu @code{Advanced | |
| 6628 (Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x | |
| 6629 customize @key{RET} sound @key{RET}}. | |
| 6630 | |
| 6631 | |
| 2459 | 6632 @node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems |
| 6633 @unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep? | |
| 2417 | 6634 |
| 6635 Make sure your XEmacs was compiled with sound support, and then put this | |
| 6636 in your @file{init.el}: | |
| 6637 | |
| 6638 @lisp | |
| 6639 (load-default-sounds) | |
| 6640 @end lisp | |
| 6641 | |
| 2459 | 6642 @node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems |
| 6643 @unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)? | |
| 6644 | |
| 6645 @dfn{Network Audio System} (NAS) is a client-server sound library for X. | |
| 6646 | |
| 6647 @uref{http://radscan.com/nas.html}. | |
| 6648 | |
| 3018 | 6649 To build XEmacs with it, use the @file{configure} flag |
| 6650 @samp{--with-sound=nas} (@samp{--enable-sound=nas} in 21.5 or later). | |
| 2459 | 6651 |
| 6652 @dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system. | |
| 6653 | |
| 6654 @uref{http://www.tux.org/~ricdude/EsounD.html}. | |
| 6655 | |
| 3018 | 6656 To build XEmacs with it, use the @file{configure} flag |
| 6657 @samp{--with-sound=esd} (@samp{--enable-sound=esd} in 21.5 or later). | |
| 6658 | |
| 6659 You can specify support for both with a flag like | |
| 6660 @samp{--with-sound=nas,esd} (@samp{--enable-sound=nas,esd} in 21.5 or | |
| 6661 later). | |
| 2459 | 6662 |
| 6663 @node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems | |
| 6664 @unnumberedsubsec Q5.3.4: Sunsite sounds don't play. | |
| 2417 | 6665 |
| 6666 I'm having some trouble with sounds I've downloaded from sunsite. They | |
| 6667 play when I run them through @code{showaudio} or cat them directly to | |
| 6668 @file{/dev/audio}, but XEmacs refuses to play them. | |
| 6669 | |
| 6670 @email{gutschk@@uni-muenster.de, Markus Gutschke} writes: | |
| 6671 | |
| 6672 @quotation | |
| 6673 [Many of] These files have an (erroneous) 24byte header that tells about | |
| 6674 the format that they have been recorded in. If you cat them to | |
| 6675 @file{/dev/audio}, the header will be ignored and the default behavior | |
| 6676 for /dev/audio will be used. This happens to be 8kHz uLaw. It is | |
| 6677 probably possible to fix the header by piping through @code{sox} and | |
| 6678 passing explicit parameters for specifying the sampling format; you then | |
| 6679 need to perform a 'null' conversion from SunAudio to SunAudio. | |
| 6680 @end quotation | |
| 6681 | |
| 2459 | 6682 @unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses |
| 6683 | |
| 6684 @node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems | |
| 6685 @unnumberedsubsec Q5.4.1: What is an interior shell? | |
| 2417 | 6686 |
| 6687 #### Write me. | |
| 6688 | |
| 2459 | 6689 @node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems |
| 6690 @unnumberedsubsec Q5.4.2: How do I start up a second shell buffer? | |
| 2417 | 6691 |
| 6692 In the @code{*shell*} buffer: | |
| 6693 | |
| 6694 @lisp | |
| 6695 M-x rename-buffer @key{RET} *shell-1* @key{RET} | |
| 6696 M-x shell RET | |
| 6697 @end lisp | |
| 6698 | |
| 6699 This will then start a second shell. The key is that no buffer named | |
| 6700 @samp{*shell*} can exist. It might be preferable to use @kbd{M-x | |
| 6701 rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x | |
| 6702 rename-buffer}. | |
| 6703 | |
| 6704 Alternately, you can set the variable @code{shell-multiple-shells}. | |
| 6705 If the value of this variable is non-nil, each time shell mode is invoked, | |
| 6706 a new shell is made | |
| 6707 | |
| 2459 | 6708 @node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems |
| 6709 @unnumberedsubsec Q5.4.3: Telnet from shell filters too much | |
| 2417 | 6710 |
| 6711 I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke | |
| 6712 and use a telnet session within it. Everything works fine except that | |
| 6713 now all @samp{^M}'s are filtered out by Emacs. Fixes? | |
| 6714 | |
| 6715 Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather | |
| 6716 than doing rsh or telnet within the local shell buffer. You can also | |
| 6717 use @kbd{M-x ssh} to open secure remote session if you have @code{ssh} | |
| 6718 installed. | |
| 6719 | |
| 2459 | 6720 @node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems |
| 6721 @unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode. | |
| 2417 | 6722 |
| 6723 Sometimes (i.e. it's not repeatable, and I can't work out why it | |
| 6724 happens) when I'm typing into shell mode, I hit return and only a | |
| 6725 portion of the command is given to the shell, and a blank prompt is | |
| 6726 returned. If I hit return again, the rest of the previous command is | |
| 6727 given to the shell. | |
| 6728 | |
| 6729 @email{martin@@xemacs.org, Martin Buchholz} writes: | |
| 6730 | |
| 6731 @quotation | |
| 6732 There is a known problem with interaction between @code{csh} and the | |
| 6733 @code{filec} option and XEmacs. You should add the following to your | |
| 6734 @file{.cshrc}: | |
| 6735 | |
| 6736 @example | |
| 6737 if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec | |
| 6738 @end example | |
| 6739 @end quotation | |
| 6740 | |
| 2995 | 6741 @node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems |
| 2459 | 6742 @unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff" |
| 2417 | 6743 |
| 6744 or "ispell" or other commands that seem related to whatever you just | |
| 6745 tried to do (M-x ediff or M-$, for example). | |
| 6746 | |
| 6747 There are a large number of common (in the sense that "everyone has | |
| 6748 these, they really do") Unix utilities that are not provided with | |
| 6749 XEmacs. The GNU Project's implementations are available for Windows in | |
| 6750 the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also | |
| 6751 provides a complete Unix emulation environment (and thus makes ports of | |
| 6752 Unix utilities nearly trivial). Another implementation is that from | |
| 6753 MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others, | |
| 6754 please let us know! | |
| 6755 | |
| 2995 | 6756 @node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems |
| 6757 @unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed" | |
| 6758 | |
| 6759 If you are getting an error like | |
| 6760 | |
| 6761 @example | |
| 6762 17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed, | |
| 6763 0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487 | |
| 6764 bash: fork: resource temporarily unavailable | |
| 6765 @end example | |
| 6766 | |
| 6767 when trying to run bash using @kbd{M-x shell}, then you need to rebase | |
| 6768 your Cygwin DLL's. This is a known problem with Cygwin. To fix: | |
| 6769 | |
| 6770 @enumerate | |
| 6771 @item | |
| 6772 Download the @file{rebase} utility from Cygwin setup (it's under | |
| 6773 @samp{System}). | |
| 6774 @item | |
| 6775 Kill @strong{all} of your Cygwin processes, including all of your | |
| 6776 shells and all background processes. Use @code{ps -a} to list all the | |
| 6777 processes you need to kill. | |
| 6778 @item | |
| 6779 From a DOS prompt, run @file{ash} (@strong{not} @file{bash}, | |
| 6780 @file{tcsh} or @file{zsh}). Do not try to be clever and @code{exec | |
| 6781 /bin/ash} from your last shell; it won't work. | |
| 6782 @item | |
| 6783 Type @code{/bin/rebaseall -v}. | |
| 6784 @end enumerate | |
| 6785 | |
| 6786 The problem should now be fixed -- at least, until you install another | |
| 6787 Cygwin package with DLL's, in which case you may have to repeat the | |
| 6788 procedure. | |
| 6789 | |
| 2459 | 6790 @unnumberedsec 5.5: Multiple Device Support |
| 6791 | |
| 2995 | 6792 @node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems |
| 2459 | 6793 @unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display? |
| 2417 | 6794 |
| 6795 Use the command @kbd{M-x make-frame-on-display}. This command is also | |
| 6796 on the File menu in the menubar. | |
| 6797 | |
| 6798 The command @code{make-frame-on-tty} also exists, which will establish a | |
| 6799 connection to any tty-like device. Opening the TTY devices should be | |
| 6800 left to @code{gnuclient}, though. | |
| 6801 | |
| 2459 | 6802 @node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems |
| 6803 @unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How? | |
| 6804 | |
| 6805 Yes. Use @code{gnuclient -nw}. | |
| 6806 | |
| 6807 Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}. | |
| 6808 | |
| 6809 @node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems | |
| 6810 @unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame? | |
| 2417 | 6811 |
| 6812 If you set the @code{gnuserv-frame} variable to the frame that should be | |
| 6813 used to display buffers that are pulled up, a new frame will not be | |
| 6814 created. For example, you could put | |
| 6815 | |
| 6816 @lisp | |
| 6817 (setq gnuserv-frame (selected-frame)) | |
| 428 | 6818 @end lisp |
| 6819 | |
| 2417 | 6820 early on in your @file{init.el}, to ensure that the first frame created |
| 6821 is the one used for your gnuserv buffers. | |
| 6822 | |
| 6823 There is an option to set the gnuserv target to the current frame. See | |
| 6824 @code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target} | |
| 6825 | |
| 6826 You can also change this with Customize. Select from the | |
| 6827 @code{Options} menu @code{Advanced | |
| 6828 (Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type | |
| 6829 @kbd{M-x customize @key{RET} gnuserv @key{RET}}. | |
| 6830 | |
| 6831 | |
| 2459 | 6832 @node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems |
| 6833 @unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client? | |
| 2417 | 6834 |
| 6835 Put the following in your @file{init.el} file to start the server: | |
| 6836 | |
| 6837 @lisp | |
| 6838 (gnuserv-start) | |
| 6839 @end lisp | |
| 6840 | |
| 6841 Start your first XEmacs as usual. After that, you can do: | |
| 6842 | |
| 6843 @example | |
| 6844 gnuclient randomfilename | |
| 6845 @end example | |
| 6846 | |
| 6847 from the command line to get your existing XEmacs process to open a new | |
| 6848 frame and visit randomfilename in that window. When you're done editing | |
| 6849 randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the | |
| 6850 frame. | |
| 6851 | |
| 6852 See also man page of gnuclient. | |
| 6853 | |
| 2459 | 6854 @node Q5.5.5, , Q5.5.4, External Subsystems |
| 6855 @unnumberedsubsec Q5.5.5: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient? | |
| 2417 | 6856 |
| 6857 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes: | |
| 6858 @quotation | |
| 6859 Here is one of the solutions, we have this in a script called | |
| 6860 @file{etc/editclient.sh}. | |
| 6861 @example | |
| 6862 #!/bin/sh | |
| 6863 if gnuclient -batch -eval t >/dev/null 2>&1 | |
| 6864 then | |
| 6865 exec gnuclient $@{1+"$@@"@} | |
| 6866 else | |
| 6867 xemacs -unmapped -f gnuserv-start & | |
| 6868 until gnuclient -batch -eval t >/dev/null 2>&1 | |
| 6869 do | |
| 6870 sleep 1 | |
| 6871 done | |
| 6872 exec gnuclient $@{1+"$@@"@} | |
| 6873 fi | |
| 6874 @end example | |
| 6875 | |
| 6876 Note that there is a known problem when running XEmacs and 'gnuclient | |
| 6877 -nw' on the same TTY. | |
| 6878 @end quotation | |
| 6879 | |
| 2459 | 6880 @node Internet, Advanced, External Subsystems, Top |
| 6881 @unnumbered 6 Connecting to the Internet | |
| 6882 | |
| 6883 This is part 6 of the XEmacs Frequently Asked Questions list. This | |
| 6884 section is devoted connecting to the Internet. | |
| 6885 | |
| 6886 @menu | |
| 6887 6.0: General Mail and News | |
| 6888 * Q6.0.1:: What are the various packages for reading mail? | |
| 6889 * Q6.0.2:: How can I send mail? | |
| 6890 * Q6.0.3:: How do I get my outgoing mail archived? | |
| 6891 * Q6.0.4:: How can I read and/or compose MIME messages? | |
| 6892 * Q6.0.5:: How do I customize the From line? | |
| 6893 * Q6.0.6:: How do I get my MUA to filter mail for me? | |
| 6894 * Q6.0.7:: Remote mail reading with an MUA. | |
| 6895 * Q6.0.8:: An MUA gets an error incorporating new mail. | |
| 6896 * Q6.0.9:: Why isn't @file{movemail} working? | |
| 6897 * Q6.0.10:: How do I make my MUA display graphical smilies? | |
| 6898 * Q6.0.11:: How can I get those oh-so-neat X-Face lines? | |
| 6899 | |
| 6900 6.1: Reading Mail with VM | |
| 6901 * Q6.1.1:: How do I set up VM to retrieve mail from a remote site using POP? | |
| 6902 * Q6.1.2:: How can I get VM to automatically check for new mail? | |
| 6903 * 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"? | |
| 6904 * Q6.1.4:: Is there a mailing list or FAQ for VM? | |
| 6905 * Q6.1.5:: How do I make VM stay in a single frame? | |
| 6906 * Q6.1.6:: Customization of VM not covered in the manual, or here. | |
| 6907 | |
| 6908 6.2: Reading Netnews and Mail with Gnus | |
| 6909 * Q6.2.1:: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 6910 * Q6.2.2:: How do I make Gnus stay within a single frame? | |
| 6911 | |
| 6912 6.3: FTP Access | |
| 6913 * Q6.3.1:: Can I edit files on other hosts? | |
| 6914 * Q6.3.2:: What is EFS? | |
| 6915 | |
| 6916 6.4: Web Browsing with W3 | |
| 6917 * Q6.4.1:: What is W3? | |
| 6918 * Q6.4.2:: How do I run W3 from behind a firewall? | |
| 6919 * Q6.4.3:: Is it true that W3 supports style sheets and tables? | |
| 6920 @end menu | |
| 6921 | |
| 6922 @unnumberedsec 6.0: General Mail and News | |
| 6923 | |
| 6924 @node Q6.0.1, Q6.0.2, Internet, Internet | |
| 6925 @unnumberedsubsec Q6.0.1: What are the various packages for reading mail? | |
| 6926 | |
| 6927 #### Write me. | |
| 6928 | |
| 6929 @node Q6.0.2, Q6.0.3, Q6.0.1, Internet | |
| 6930 @unnumberedsubsec Q6.0.2: How can I send mail? | |
| 6931 | |
| 6932 Under Unix and Mac OS X, the @samp{sendmail} package is normally used | |
| 6933 for this. | |
| 6934 #### Write me. | |
| 6935 | |
| 6936 Under Windows, you need to use @samp{smtpmail}, which communicates | |
| 6937 directly with the mail server, as there is no @file{sendmail} program | |
| 6938 running. To get it working, use code like the following in your | |
| 6939 @file{init.el} file: | |
| 6940 | |
| 6941 @lisp | |
| 6942 ;; Get mail working under Windows. | |
| 6943 (setq message-send-mail-function 'smtpmail-send-it) ; for message/Gnus | |
| 6944 (setq send-mail-function 'smtpmail-send-it) ; for C-x m, etc. | |
| 6945 ;; the following ensures that mail problems can be debugged: it logs a trace | |
| 6946 ;; of the SMTP conversation to *trace of SMTP session to <somewhere>*. | |
| 6947 (setq smtpmail-debug-info t) | |
| 6948 ;; Substitute your info here. | |
| 6949 ;(setq user-mail-address "ben@@xemacs.org") | |
| 6950 ;(setq user-full-name "Ben Wing") | |
| 6951 ;(setq smtpmail-default-smtp-server "smtp.myserver.myisp.com") | |
| 6952 ;; The following two aren't completely necessary but may help. | |
| 6953 ;(setq smtpmail-local-domain "666.com") | |
| 6954 ;(setq smtpmail-sendto-domain "666.com") | |
| 6955 ;; If your SMTP server requires a username/password to authenticate, as | |
| 6956 ;; many do nowadays, set them like this: | |
| 6957 ;(setq smtpmail-auth-credentials ; or use ~/.authinfo | |
| 6958 ; '(("smtp.myserver.myisp.com" 25 "USER@@SOMEWHERE" "PASSWORD"))) | |
| 6959 | |
| 6960 ;; Other possibilities for getting smtpmail to work: | |
| 6961 ;; | |
| 6962 ;; If for some reason you need to authenticate using the STARTTLS protocol | |
| 6963 ;; (don't look into this unless you know what it is), use | |
| 6964 ;; (setq smtpmail-starttls-credentials | |
| 6965 ;; '(("YOUR SMTP HOST" 25 "~/.my_smtp_tls.key" "~/.my_smtp_tls.cert"))) | |
| 6966 ;; Requires external program | |
| 6967 ;; ftp://ftp.opaopa.org/pub/elisp/starttls-*.tar.gz. | |
| 6968 ;; See http://www.ietf.org/rfc/rfc2246.txt, | |
| 6969 ;; http://www.ietf.org/rfc/rfc2487.txt | |
| 6970 @end lisp | |
| 6971 | |
| 6972 The lines you need to care about are those that set | |
| 6973 @code{user-mail-address}, @code{user-full-name}, | |
| 6974 @code{smtpmail-default-smtp-server}, and | |
| 6975 @code{smtpmail-auth-credentials}. You need to set these with, | |
| 6976 respectively, your email address, your full name, the SMTP server you | |
| 6977 use for outgoing mail, and the username and password you need to log | |
| 6978 in to your SMTP server. (If for some reason your SMTP server doesn't | |
| 6979 require logging in to send mail, don't uncomment this last line.) | |
| 6980 | |
| 6981 The other settings may be useful in specific cases, but you should know what | |
| 6982 you're doing before enabling them. | |
| 6983 | |
| 6984 @node Q6.0.3, Q6.0.4, Q6.0.2, Internet | |
| 6985 @unnumberedsubsec Q6.0.3: How do I get my outgoing mail archived? | |
| 6986 | |
| 6987 @lisp | |
| 6988 (setq mail-archive-file-name "~/outbox") | |
| 6989 @end lisp | |
| 6990 | |
| 6991 @node Q6.0.4, Q6.0.5, Q6.0.3, Internet | |
| 6992 @unnumberedsubsec Q6.0.4: How can I read and/or compose MIME messages? | |
| 6993 | |
| 6994 VM, MH-E and GNUS support MIME natively. Other MUAs may or may not | |
| 6995 have MIME support; refer to their documentation and other resources, | |
| 6996 such as web pages and mailing lists. Packages like SEMI/WEMI may be | |
| 6997 useful in connection with MUAs like mew and Wanderlust. | |
| 6998 | |
| 6999 @node Q6.0.5, Q6.0.6, Q6.0.4, Internet | |
| 7000 @unnumberedsubsec Q6.0.5: How do I customize the From line? | |
| 7001 | |
| 7002 How do I change the @samp{From:} line? I have set gnus-user-from-line | |
| 7003 to | |
| 7004 @example | |
| 7005 Gail Gurman <gail.gurman@@sybase.com> | |
| 7006 @end example | |
| 7007 @noindent , but XEmacs Gnus doesn't use | |
| 7008 it. [This should apply to all MUA's. --ed] Instead it uses | |
| 7009 @example | |
| 7010 Gail Mara Gurman @email{gailg@@deall} | |
| 7011 @end example | |
| 7012 @noindent and then complains | |
| 7013 that it's incorrect. Also, as you perhaps can see, my Message-ID is | |
| 7014 screwy. How can I change that? | |
| 7015 | |
| 7016 @email{larsi@@ifi.uio.no, Lars Magne Ingebrigtsen} writes: | |
| 7017 | |
| 7018 @quotation | |
| 7019 Set @code{user-mail-address} to @samp{gail.gurman@@sybase.com} or | |
| 7020 @code{mail-host-address} to @samp{sybase.com}. | |
| 7021 @end quotation | |
| 7022 | |
| 7023 @node Q6.0.6, Q6.0.7, Q6.0.5, Internet | |
| 7024 @unnumberedsubsec Q6.0.6: How do I get my MUA to filter mail for me? | |
| 7025 | |
| 7026 One possibility is to use procmail to split your mail before it gets to | |
| 7027 the MUA. I prefer this personally, since there are many strange and | |
| 7028 wonderful things one can do with procmail. Procmail may be found at | |
| 7029 @uref{http://www.procmail.org/}. | |
| 7030 | |
| 7031 Also see the Mail Filtering FAQ at: | |
| 7032 @iftex | |
| 7033 @* | |
| 7034 @end iftex | |
| 7035 @uref{http://www.faqs.org/faqs/mail/filtering-faq/}. | |
| 7036 | |
| 7037 @node Q6.0.7, Q6.0.8, Q6.0.6, Internet | |
| 7038 @unnumberedsubsec Q6.0.7: Remote mail reading with an MUA. | |
| 7039 | |
| 7040 My mailbox lives at the office on a big honkin server. My regular INBOX | |
| 7041 lives on my honkin desktop machine. I now can PPP to the office from | |
| 7042 home which is far from honking... I'd like to be able to read mail at | |
| 7043 home without storing it here and I'd like to use xemacs and the MUA at | |
| 7044 home... Is there a recommended setup? | |
| 7045 | |
| 7046 @email{nuspl@@nvwls.cc.purdue.edu, Joseph J. Nuspl Jr.} writes: | |
| 7047 | |
| 7048 @quotation | |
| 7049 There are several ways to do this. | |
| 7050 | |
| 7051 @enumerate | |
| 7052 @item | |
| 7053 Set your display to your home machine and run dxpc or one of the other X | |
| 7054 compressors. | |
| 7055 | |
| 7056 @item | |
| 7057 NFS mount your desktop machine on your home machine and modify your pop | |
| 7058 command on your home machine to rsh to your desktop machine and actually | |
| 7059 do the pop get's. | |
| 7060 | |
| 7061 @item | |
| 7062 Run a POP server on your desktop machine as well and do a sort of two | |
| 7063 tiered POP get. | |
| 7064 @end enumerate | |
| 7065 @end quotation | |
| 7066 | |
| 7067 @email{wmperry@@monolith.spry.com, William Perry} adds: | |
| 7068 | |
| 7069 @quotation | |
| 7070 Or you could run a pop script periodically on your desktop machine, and | |
| 7071 just use ange-ftp or NFS to get to your mailbox. I used to do this all | |
| 7072 the time back at IU. | |
| 7073 @end quotation | |
| 7074 | |
| 7075 @node Q6.0.8, Q6.0.9, Q6.0.7, Internet | |
| 7076 @unnumberedsubsec Q6.0.8: An MUA gets an error incorporating new mail. | |
| 7077 | |
| 7078 rmail and VM, and probably other MUA's as well, get new mail from | |
| 7079 your mailbox (called @file{/var/mail/$USER} or @file{/var/spool/mail/$USER} | |
| 7080 or something similar) using a program called @code{movemail}. | |
| 7081 This program interlocks with @code{/bin/mail} using the protocol | |
| 7082 defined by @code{/bin/mail}. | |
| 7083 | |
| 7084 There are various different protocols in general use, which you need to | |
| 3018 | 7085 specify using the @samp{--mail-locking} option |
| 7086 (@samp{--with-mail-locking} in 21.5 or later) to @file{configure}: | |
| 2459 | 7087 |
| 7088 @table @samp | |
| 7089 @item lockf | |
| 7090 POSIX file locking with @code{lockf()} | |
| 7091 @item flock | |
| 7092 BSD file locking with @code{flock()} | |
| 7093 @item dot | |
| 7094 To manipulate mail file @file{foo}, first create file @file{foo.lock} | |
| 7095 @item locking | |
| 7096 Use @code{locking()}, Microsoft's renamed @code{flock()} | |
| 7097 @item mmdf | |
| 7098 Use @code{lk_open()} and @code{lk_close()} as defined by the Multi-channel | |
| 7099 Memo Distribution Facility | |
| 7100 @item pop | |
| 7101 Retrieve mail using POP (the Post Office Protocol). This is the | |
| 7102 default for Cygwin/MinGW. | |
| 7103 @end table | |
| 7104 | |
| 7105 @strong{IF YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR | |
| 7106 SYSTEM, YOU CAN LOSE MAIL!} | |
| 7107 | |
| 7108 Usually the value is correctly determined automatically: | |
| 7109 @file{configure} tries to detect the method in use, and defaults exist | |
| 7110 on systems for which this doesn't work. | |
| 7111 | |
| 7112 However, if you run into problems incorporating new mail, it may be | |
| 7113 because an incorrect method is being used. | |
| 7114 | |
| 7115 If your system uses the lock file protocol, and permissions are set | |
| 7116 so that ordinary users cannot write lock files in the mail spool | |
| 7117 directory, you may need to make @file{movemail} setgid to a | |
| 7118 suitable group such as @samp{mail}. You can use these commands (as | |
| 7119 root): | |
| 7120 | |
| 7121 @example | |
| 7122 chgrp mail movemail | |
| 7123 chmod 2755 movemail | |
| 7124 @end example | |
| 7125 | |
| 7126 If you are using the @samp{pop} locking method, @file{movemail} must | |
| 7127 be setuid root. | |
| 7128 | |
| 7129 Installation normally copies movemail from the build directory to an | |
| 7130 installation directory which is usually under @file{/usr/local/lib}. | |
| 7131 The installed copy of @file{movemail} is usually in the directory | |
| 7132 @file{/usr/local/lib/xemacs-VERSION/TARGET} (for example, | |
| 7133 @file{/usr/local/lib/xemacs-21.4.15/i686-pc-cygwin}). You must change | |
| 7134 the group and mode of the installed copy; changing the group and mode | |
| 7135 of the build directory copy is ineffective. | |
| 7136 | |
| 7137 @node Q6.0.9, Q6.0.10, Q6.0.8, Internet | |
| 7138 @unnumberedsubsec Q6.0.9: Why isn't @file{movemail} working? | |
| 7139 | |
| 7140 @xref{Q6.0.8}. | |
| 7141 | |
| 7142 Note also that older versions of Mozilla came with a @file{movemail} | |
| 7143 program that is @strong{not} compatible with XEmacs. Do not use it. | |
| 7144 Always use the @file{movemail} installed with your XEmacs. Failure to | |
| 7145 do so can result in lost mail. | |
| 7146 | |
| 7147 @node Q6.0.10, Q6.0.11, Q6.0.9, Internet | |
| 7148 @unnumberedsubsec Q6.0.10: How do I make my MUA display graphical smilies? | |
| 7149 For mh-e use the following: | |
| 7150 | |
| 7151 @lisp | |
| 7152 (add-hook 'mh-show-mode-hook '(lambda () | |
| 7153 (smiley-region (point-min) | |
| 7154 (point-max)))) | |
| 7155 @end lisp | |
| 7156 | |
| 7157 @email{bill@@carpenter.ORG, WJCarpenter} writes: | |
| 7158 For VM use the following: | |
| 7159 @lisp | |
| 7160 (autoload 'smiley-region "smiley" nil t) | |
| 7161 (add-hook 'vm-select-message-hook | |
| 7162 '(lambda () | |
| 7163 (smiley-region (point-min) | |
| 7164 (point-max)))) | |
| 7165 @end lisp | |
| 7166 | |
| 7167 For tm use the following: | |
| 7168 @lisp | |
| 7169 (autoload 'smiley-buffer "smiley" nil t) | |
| 7170 (add-hook 'mime-viewer/plain-text-preview-hook 'smiley-buffer) | |
| 7171 @end lisp | |
| 7172 | |
| 7173 @node Q6.0.11, Q6.1.1, Q6.0.10, Internet | |
| 7174 @unnumberedsubsec Q6.0.11: How can I get those oh-so-neat X-Face lines? | |
| 7175 | |
| 7176 Firstly there is an ftp site which describes X-faces and has the | |
| 7177 associated tools mentioned below, at | |
| 7178 @uref{http://ftp.cs.indiana.edu/pub/faces/}. | |
| 7179 | |
| 7180 Then the steps are | |
| 7181 | |
| 7182 @enumerate | |
| 7183 @item | |
| 7184 Create 48x48x1 bitmap with your favorite tool | |
| 7185 | |
| 7186 @item | |
| 7187 Convert to "icon" format using one of xbm2ikon, pbmtoicon, etc., | |
| 7188 and then compile the face. | |
| 7189 | |
| 7190 @item | |
| 7191 @example | |
| 7192 cat file.xbm | xbm2ikon |compface > file.face | |
| 7193 @end example | |
| 7194 | |
| 7195 @item | |
| 7196 Then be sure to quote things that are necessary for emacs strings: | |
| 7197 | |
| 7198 @example | |
| 7199 cat ./file.face | sed 's/\\/\\\\/g' | |
| 7200 @iftex | |
| 7201 \ @* | |
| 7202 @end iftex | |
| 7203 | sed 's/\"/\\\"/g' > ./file.face.quoted | |
| 7204 @end example | |
| 7205 | |
| 7206 @item | |
| 7207 Then set up emacs to include the file as a mail header - there were a | |
| 7208 couple of suggestions here---either something like: | |
| 7209 | |
| 7210 @lisp | |
| 7211 (setq mail-default-headers | |
| 7212 "X-Face: @email{Ugly looking text string here}") | |
| 7213 @end lisp | |
| 7214 | |
| 7215 Or, alternatively, as: | |
| 7216 | |
| 7217 @lisp | |
| 7218 (defun mail-insert-x-face () | |
| 7219 (save-excursion | |
| 7220 (goto-char (point-min)) | |
| 7221 (search-forward mail-header-separator) | |
| 7222 (beginning-of-line) | |
| 7223 (insert "X-Face:") | |
| 7224 (insert-file-contents "~/.face"))) | |
| 7225 | |
| 7226 (add-hook 'mail-setup-hook 'mail-insert-x-face) | |
| 7227 @end lisp | |
| 7228 @end enumerate | |
| 7229 | |
| 7230 However, 2 things might be wrong: | |
| 7231 | |
| 7232 Some versions of pbmtoicon produces some header lines that is not | |
| 7233 expected by the version of compface that I grabbed. So I found I had to | |
| 7234 include a @code{tail +3} in the pipeline like this: | |
| 7235 | |
| 7236 @example | |
| 7237 cat file.xbm | xbm2ikon | tail +3 |compface > file.face | |
| 7238 @end example | |
| 7239 | |
| 7240 Some people have also found that if one uses the @code{(insert-file)} | |
| 7241 method, one should NOT quote the face string using the sed script . | |
| 7242 | |
| 7243 It might also be helpful to use @email{stig@@hackvan.com, Stig's} script | |
| 7244 xbm2face (included in the compface distribution at XEmacs.org) to do the | |
| 7245 conversion. | |
| 7246 | |
| 7247 Contributors for this item: | |
| 7248 | |
| 7249 Paul Emsley, | |
| 7250 Ricardo Marek, | |
| 7251 Amir J. Katz, | |
| 7252 Glen McCort, | |
| 7253 Heinz Uphoff, | |
| 7254 Peter Arius, | |
| 7255 Paul Harrison, and | |
| 7256 Vegard Vesterheim | |
| 7257 | |
| 7258 @unnumberedsec 6.1: Reading Mail with VM | |
| 7259 | |
| 7260 @node Q6.1.1, Q6.1.2, Q6.0.11, Internet | |
| 7261 @unnumberedsubsec Q6.1.1: How do I set up VM to retrieve mail from a remote site using POP? | |
| 7262 | |
| 7263 Use @code{vm-spool-files}, like this for example: | |
| 7264 | |
| 7265 @lisp | |
| 7266 (setq vm-spool-files '("/var/spool/mail/wing" | |
| 7267 "netcom23.netcom.com:110:pass:wing:MYPASS")) | |
| 7268 @end lisp | |
| 7269 | |
| 7270 Of course substitute your actual password for MYPASS. | |
| 7271 | |
| 7272 @node Q6.1.2, Q6.1.3, Q6.1.1, Internet | |
| 7273 @unnumberedsubsec Q6.1.2: How can I get VM to automatically check for new mail? | |
| 7274 | |
| 7275 @email{turner@@lanl.gov, John Turner} writes: | |
| 7276 | |
| 7277 @quotation | |
| 7278 Use the following: | |
| 7279 | |
| 7280 @lisp | |
| 7281 (setq vm-auto-get-new-mail 60) | |
| 7282 @end lisp | |
| 7283 @end quotation | |
| 7284 | |
| 7285 @node Q6.1.3, Q6.1.4, Q6.1.2, Internet | |
| 7286 @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"? | |
| 7287 | |
| 7288 Set @code{vm-reply-ignored-addresses} to a list, like | |
| 7289 | |
| 7290 @lisp | |
| 7291 (setq vm-reply-ignored-addresses | |
| 7292 '("wing@@nuspl@@nvwls.cc.purdue.edu,netcom[0-9]*.netcom.com" | |
| 7293 "wing@@netcom.com" "wing@@xemacs.org")) | |
| 7294 @end lisp | |
| 7295 | |
| 7296 Note that each string is a regular expression. | |
| 7297 | |
| 7298 @node Q6.1.4, Q6.1.5, Q6.1.3, Internet | |
| 7299 @unnumberedsubsec Q6.1.4: Is there a mailing list or FAQ for VM? | |
| 7300 | |
| 7301 A FAQ for VM exists at @uref{http://www.wonderworks.com/vm/FAQ.html}. | |
| 7302 | |
| 7303 VM has its own newsgroups gnu.emacs.vm.info and gnu.emacs.vm.bug. | |
| 7304 | |
| 7305 @node Q6.1.5, Q6.1.6, Q6.1.4, Internet | |
| 7306 @unnumberedsubsec Q6.1.5: How do I make VM stay in a single frame? | |
| 7307 | |
| 7308 John.@email{Cooper@@Eng.Sun.COM, John S Cooper} writes: | |
| 7309 | |
| 7310 @quotation | |
| 7311 @lisp | |
| 7312 ; Don't use multiple frames | |
| 7313 (setq vm-frame-per-composition nil) | |
| 7314 (setq vm-frame-per-folder nil) | |
| 7315 (setq vm-frame-per-edit nil) | |
| 7316 (setq vm-frame-per-summary nil) | |
| 7317 @end lisp | |
| 7318 @end quotation | |
| 7319 | |
| 7320 @node Q6.1.6, Q6.2.1, Q6.1.5, Internet | |
| 7321 @unnumberedsubsec Q6.1.6: Customization of VM not covered in the manual, or here. | |
| 7322 | |
| 4311 | 7323 @email{boffi@@hp735.stru.polimi.it, Giacomo Boffi} writes: |
| 2459 | 7324 |
| 7325 @quotation | |
| 7326 The meta-answer is to look into the file @file{vm-vars.el}, in the vm | |
| 7327 directory of the lisp library. | |
| 7328 | |
| 7329 @file{vm-vars.el} contains, initializes and carefully describes, with | |
| 7330 examples of usage, the plethora of user options that @emph{fully} | |
| 7331 control VM's behavior. | |
| 7332 | |
| 7333 Enter vm-vars, @code{forward-search} for toolbar, find the variables | |
| 7334 that control the toolbar placement, appearance, existence, copy to your | |
| 7335 @file{init.el} or @file{.vm} and modify according to the | |
| 7336 detailed instructions. | |
| 7337 | |
| 7338 The above also applies to all the various features of VM: search for | |
| 7339 some keywords, maybe the first you conjure isn't appropriate, find the | |
| 7340 appropriate variables, copy and experiment. | |
| 7341 @end quotation | |
| 7342 | |
| 7343 @unnumberedsec 6.2: Reading Netnews and Mail with Gnus | |
| 7344 | |
| 7345 @node Q6.2.1, Q6.2.2, Q6.1.6, Internet | |
| 7346 @unnumberedsubsec Q6.2.1: GNUS, (ding) Gnus, Gnus 5, September Gnus, Red Gnus, Quassia Gnus, argh! | |
| 7347 | |
| 7348 The Gnus numbering issues are not meant for mere mortals to know them. | |
| 7349 If you feel you @emph{must} enter the muddy waters of Gnus, visit the | |
| 7350 excellent FAQ, maintained by Justin Sheehy, at: | |
| 7351 | |
| 7352 @example | |
| 7353 @uref{http://my.gnus.org/FAQ/} | |
| 7354 @end example | |
| 7355 | |
| 7356 See also Gnus home page | |
| 7357 @example | |
| 7358 @uref{http://www.gnus.org/} | |
| 7359 @end example | |
| 7360 | |
| 7361 @node Q6.2.2, Q6.3.1, Q6.2.1, Internet | |
| 7362 @unnumberedsubsec Q6.2.2: How do I make Gnus stay within a single frame? | |
| 7363 | |
| 7364 The toolbar code to start Gnus opens the new frame---and it's a feature | |
| 7365 rather than a bug. If you don't like it, but would still like to click | |
| 7366 on the seemly icon, use the following code: | |
| 7367 | |
| 7368 @lisp | |
| 7369 (defun toolbar-news () | |
| 7370 (gnus)) | |
| 7371 @end lisp | |
| 7372 | |
| 7373 It will redefine the callback function of the icon to just call | |
| 7374 @code{gnus}, without all the fancy frame stuff. | |
| 7375 | |
| 7376 @unnumberedsec 6.3: FTP Access | |
| 7377 | |
| 7378 @node Q6.3.1, Q6.3.2, Q6.2.2, Internet | |
| 7379 @unnumberedsubsec Q6.3.1: Can I edit files on other hosts? | |
| 7380 | |
| 7381 Yes. Of course XEmacs can use any network file system (such as NFS or | |
| 7382 Windows file sharing) you have available, and includes some | |
| 7383 optimizations and safety features appropriate to those environments. | |
| 7384 | |
| 7385 It is also possible to transparently edit files via FTP, ssh, or rsh. That | |
| 7386 is, XEmacs makes a local copy using the transport in the background, and | |
| 7387 automatically refreshes the remote original from that copy when you save | |
| 7388 it. XEmacs also is capable of doing file system manipulations like | |
| 7389 creating and removing directories and files. The FTP interface is | |
| 7390 provided by the standard @samp{efs} package @ref{Top, EFS, , efs}. The | |
| 7391 ssh/rsh interface is provided by the optional @samp{tramp} package | |
| 7392 @ref{Top, TRAMP, , tramp}. | |
| 7393 | |
| 7394 @node Q6.3.2, Q6.4.1, Q6.3.1, Internet | |
| 7395 @unnumberedsubsec Q6.3.2: What is EFS? | |
| 7396 | |
| 7397 #### Write me. | |
| 7398 | |
| 7399 @unnumberedsec 6.4: Web Browsing with W3 | |
| 7400 | |
| 7401 @node Q6.4.1, Q6.4.2, Q6.3.2, Internet | |
| 7402 @unnumberedsubsec Q6.4.1: What is W3? | |
| 7403 | |
| 7404 W3 is an advanced graphical browser written in Emacs lisp that runs on | |
| 7405 XEmacs. It has full support for cascaded style sheets, and more... | |
| 7406 | |
| 7407 It has a home web page at | |
| 7408 @uref{http://www.cs.indiana.edu/elisp/w3/docs.html}. | |
| 7409 | |
| 7410 @node Q6.4.2, Q6.4.3, Q6.4.1, Internet | |
| 7411 @unnumberedsubsec Q6.4.2: How do I run W3 from behind a firewall? | |
| 7412 | |
| 7413 There is a long, well-written, detailed section in the W3 manual that | |
| 7414 describes how to do this. Look in the section entitled "Firewalls". | |
| 7415 | |
| 7416 @node Q6.4.3, , Q6.4.2, Internet | |
| 7417 @unnumberedsubsec Q6.4.3: Is it true that W3 supports style sheets and tables? | |
| 7418 | |
| 7419 Yes, and much more. W3, as distributed with the latest XEmacs is a | |
| 7420 full-featured web browser. | |
| 7421 | |
| 7422 @node Advanced, Other Packages, Internet, Top | |
| 7423 @unnumbered 7 Advanced Customization Using XEmacs Lisp | |
| 7424 | |
| 7425 This is part 7 of the XEmacs Frequently Asked Questions list. This | |
| 7426 section is devoted to advanced customization using XEmacs Lisp. | |
| 7427 | |
| 7428 @menu | |
| 2537 | 7429 7.0: Emacs Lisp and @file{init.el} |
| 7430 * Q7.0.1:: What version of Emacs am I running? | |
| 7431 * Q7.0.2:: How can I evaluate Emacs-Lisp expressions? | |
| 7432 * Q7.0.3:: @code{(setq tab-width 6)} behaves oddly. | |
| 7433 * Q7.0.4:: How can I add directories to the @code{load-path}? | |
| 7434 * Q7.0.5:: How to check if a lisp function is defined? | |
| 7435 * Q7.0.6:: Can I force the output of @code{(face-list)} to a buffer? | |
| 7436 | |
| 7437 7.1: Emacs Lisp Programming Techniques | |
| 7438 * Q7.1.1:: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 7439 * Q7.1.2:: Can I generate "fake" keyboard events? | |
| 7440 * Q7.1.3:: Could you explain @code{read-kbd-macro} in more detail? | |
| 7441 * Q7.1.4:: What is the performance hit of @code{let}? | |
| 7442 * Q7.1.5:: What is the recommended use of @code{setq}? | |
| 7443 * Q7.1.6:: What is the typical misuse of @code{setq}? | |
| 7444 * Q7.1.7:: I like the @code{do} form of cl, does it slow things down? | |
| 7445 * Q7.1.8:: I like recursion, does it slow things down? | |
| 7446 * Q7.1.9:: How do I put a glyph as annotation in a buffer? | |
| 7447 * Q7.1.10:: @code{map-extents} won't traverse all of my extents! | |
| 7448 * Q7.1.11:: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 7449 | |
| 7450 7.2: Mathematics | |
| 7451 * Q7.2.1:: What are bignums, ratios, and bigfloats in Lisp? | |
| 7452 * Q7.2.2:: XEmacs segfaults when I use very big numbers! | |
| 7453 * Q7.2.3:: Bignums are really slow! | |
| 7454 * Q7.2.4:: Equal bignums don't compare as equal! What gives? | |
| 2459 | 7455 @end menu |
| 7456 | |
| 2537 | 7457 @unnumberedsec 7.0: Emacs Lisp and @file{init.el} |
| 2459 | 7458 |
| 7459 @node Q7.0.1, Q7.0.2, Advanced, Advanced | |
| 2537 | 7460 @unnumberedsubsec Q7.0.1: What version of Emacs am I running? |
| 2459 | 7461 |
| 7462 How can @file{init.el} determine which of the family of | |
| 7463 Emacsen I am using? | |
| 7464 | |
| 7465 To determine if you are currently running GNU Emacs 18, GNU Emacs 19, | |
| 7466 XEmacs 19, XEmacs 20, or Epoch, and use appropriate code, check out the | |
| 7467 example given in @file{etc/sample.init.el} (@file{etc/sample.emacs} in | |
| 7468 XEmacs versions prior to 21.4). There are other nifty things in there | |
| 7469 as well! | |
| 7470 | |
| 7471 For all new code, all you really need to do is: | |
| 7472 | |
| 7473 @lisp | |
| 7474 (defvar running-xemacs (string-match "XEmacs\\|Lucid" emacs-version)) | |
| 7475 @end lisp | |
| 7476 | |
| 2537 | 7477 @node Q7.0.2, Q7.0.3, Q7.0.1, Advanced |
| 7478 @unnumberedsubsec Q7.0.2: How can I evaluate Emacs-Lisp expressions? | |
| 2459 | 7479 |
| 7480 I know I can evaluate Elisp expressions from @code{*scratch*} buffer | |
| 7481 with @kbd{C-j} after the expression. How do I do it from another | |
| 7482 buffer? | |
| 7483 | |
| 7484 Press @kbd{M-:} (the default binding of @code{eval-expression}), and | |
| 7485 enter the expression to the minibuffer. | |
| 7486 | |
| 2537 | 7487 @node Q7.0.3, Q7.0.4, Q7.0.2, Advanced |
| 7488 @unnumberedsubsec Q7.0.3: @code{(setq tab-width 6)} behaves oddly. | |
| 2459 | 7489 |
| 7490 If you put @code{(setq tab-width 6)} in your | |
| 7491 @file{init.el} file it does not work! Is there a reason | |
| 7492 for this? If you do it at the EVAL prompt it works fine!! How strange. | |
| 7493 | |
| 7494 Use @code{setq-default} instead, since @code{tab-width} is | |
| 7495 all-buffer-local. | |
| 7496 | |
| 2537 | 7497 @node Q7.0.4, Q7.0.5, Q7.0.3, Advanced |
| 7498 @unnumberedsubsec Q7.0.4: How can I add directories to the @code{load-path}? | |
| 2459 | 7499 |
| 7500 Here are two ways to do that, one that puts your directories at the | |
| 7501 front of the load-path, the other at the end: | |
| 7502 | |
| 7503 @lisp | |
| 7504 ;;; Add things at the beginning of the load-path, do not add | |
| 7505 ;;; duplicate directories: | |
| 7506 (pushnew "bar" load-path :test 'equal) | |
| 7507 | |
| 7508 (pushnew "foo" load-path :test 'equal) | |
| 7509 | |
| 7510 ;;; Add things at the end, unconditionally | |
| 7511 (setq load-path (nconc load-path '("foo" "bar"))) | |
| 7512 @end lisp | |
| 7513 | |
| 4311 | 7514 @email{keithh@@nortel.ca, Keith (k.p.) Hanlan} writes: |
| 2459 | 7515 |
| 7516 @quotation | |
| 7517 To add directories using Unix shell metacharacters use | |
| 7518 @file{expand-file-name} like this: | |
| 7519 | |
| 7520 @lisp | |
| 7521 (push (expand-file-name "~keithh/.emacsdir") load-path) | |
| 7522 @end lisp | |
| 7523 @end quotation | |
| 7524 | |
| 2537 | 7525 @node Q7.0.5, Q7.0.6, Q7.0.4, Advanced |
| 7526 @unnumberedsubsec Q7.0.5: How to check if a lisp function is defined? | |
| 2459 | 7527 |
| 7528 Use the following elisp: | |
| 7529 | |
| 7530 @lisp | |
| 7531 (fboundp 'foo) | |
| 7532 @end lisp | |
| 7533 | |
| 7534 It's almost always a mistake to test @code{emacs-version} or any similar | |
| 7535 variables. | |
| 7536 | |
| 7537 Instead, use feature-tests, such as @code{featurep}, @code{boundp}, | |
| 7538 @code{fboundp}, or even simple behavioral tests, eg.: | |
| 7539 | |
| 7540 @lisp | |
| 7541 (defvar foo-old-losing-code-p | |
| 7542 (condition-case nil (progn (losing-code t) nil) | |
| 7543 (wrong-number-of-arguments t))) | |
| 7544 @end lisp | |
| 7545 | |
| 7546 There is an incredible amount of broken code out there which could work | |
| 7547 much better more often in more places if it did the above instead of | |
| 7548 trying to divine its environment from the value of one variable. | |
| 7549 | |
| 2537 | 7550 @node Q7.0.6, Q7.1.1, Q7.0.5, Advanced |
| 7551 @unnumberedsubsec Q7.0.6: Can I force the output of @code{(face-list)} to a buffer? | |
| 2459 | 7552 |
| 7553 It would be good having it in a buffer, as the output of | |
| 7554 @code{(face-list)} is too wide to fit to a minibuffer. | |
| 7555 | |
| 7556 Evaluate the expression in the @samp{*scratch*} buffer with point after | |
| 7557 the rightmost paren and typing @kbd{C-j}. | |
| 7558 | |
| 7559 If the minibuffer smallness is the only problem you encounter, you can | |
| 7560 simply press @kbd{C-h l} to get the former minibuffer contents in a | |
| 7561 buffer. | |
| 7562 | |
| 2537 | 7563 @unnumberedsec 7.1: Emacs Lisp Programming Techniques |
| 7564 | |
| 7565 @node Q7.1.1, Q7.1.2, Q7.0.6, Advanced | |
| 7566 @unnumberedsubsec Q7.1.1: What is the difference in key sequences between XEmacs and GNU Emacs? | |
| 2459 | 7567 |
| 7568 @email{clerik@@naggum.no, Erik Naggum} writes; | |
| 7569 | |
| 7570 @quotation | |
| 7571 Emacs has a legacy of keyboards that produced characters with modifier | |
| 7572 bits, and therefore map a variety of input systems into this scheme even | |
| 7573 today. XEmacs is instead optimized for X events. This causes an | |
| 7574 incompatibility in the way key sequences are specified, but both Emacs | |
| 7575 and XEmacs will accept a key sequence as a vector of lists of modifiers | |
| 7576 that ends with a key, e.g., to bind @kbd{M-C-a}, you would say | |
| 7577 @code{[(meta control a)]} in both Emacsen. XEmacs has an abbreviated | |
| 7578 form for a single key, just (meta control a). Emacs has an abbreviated | |
| 7579 form for the Control and the Meta modifiers to string-characters (the | |
| 7580 ASCII characters), as in @samp{\M-\C-a}. XEmacs users need to be aware | |
| 7581 that the abbreviated form works only for one-character key sequences, | |
| 7582 while Emacs users need to be aware that the string-character is rather | |
| 7583 limited. Specifically, the string-character can accommodate only 256 | |
| 7584 different values, 128 of which have the Meta modifier and 128 of which | |
| 7585 have not. In each of these blocks, only 32 characters have the Control | |
| 7586 modifier. Whereas @code{[(meta control A)]} differs from @code{[(meta | |
| 7587 control a)]} because the case differs, @samp{\M-\C-a} and @samp{\M-\C-A} | |
| 7588 do not. Programmers are advised to use the full common form, both | |
| 7589 because it is more readable and less error-prone, and because it is | |
| 7590 supported by both Emacsen. | |
| 7591 @end quotation | |
| 7592 | |
| 7593 Another (even safer) way to be sure of the key-sequences is to use the | |
| 7594 @code{read-kbd-macro} function, which takes a string like @samp{C-c | |
| 7595 <up>}, and converts it to the internal key representation of the Emacs | |
| 7596 you use. The function is available both on XEmacs and GNU Emacs. | |
| 7597 | |
| 2537 | 7598 @node Q7.1.2, Q7.1.3, Q7.1.1, Advanced |
| 7599 @unnumberedsubsec Q7.1.2: Can I generate "fake" keyboard events? | |
| 2459 | 7600 |
| 7601 I wonder if there is an interactive function that can generate | |
| 7602 @dfn{fake} keyboard events. This way, I could simply map them inside | |
| 7603 XEmacs. | |
| 7604 | |
| 7605 This seems to work: | |
| 7606 | |
| 7607 @lisp | |
| 7608 (defun cg--generate-char-event (ch) | |
| 7609 "Generate an event, as if ch has been typed" | |
| 7610 (dispatch-event (character-to-event ch))) | |
| 7611 | |
| 7612 ;; Backspace and Delete stuff | |
| 7613 (global-set-key [backspace] | |
| 7614 (lambda () (interactive) (cg--generate-char-event 127))) | |
| 7615 (global-set-key [unknown_keysym_0x4] | |
| 7616 (lambda () (interactive) (cg--generate-char-event 4))) | |
| 7617 @end lisp | |
| 7618 | |
| 2537 | 7619 @node Q7.1.3, Q7.1.4, Q7.1.2, Advanced |
| 7620 @unnumberedsubsec Q7.1.3: Could you explain @code{read-kbd-macro} in more detail? | |
| 2459 | 7621 |
| 7622 The @code{read-kbd-macro} function returns the internal Emacs | |
| 7623 representation of a human-readable string (which is its argument). | |
| 7624 Thus: | |
| 7625 | |
| 7626 @lisp | |
| 7627 (read-kbd-macro "C-c C-a") | |
| 7628 @result{} [(control ?c) (control ?a)] | |
| 7629 | |
| 7630 (read-kbd-macro "C-c C-. <up>") | |
| 7631 @result{} [(control ?c) (control ?.) up] | |
| 7632 @end lisp | |
| 7633 | |
| 7634 In GNU Emacs the same forms will be evaluated to what GNU Emacs | |
| 7635 understands internally---the sequences @code{"\C-x\C-c"} and @code{[3 | |
| 7636 67108910 up]}, respectively. | |
| 7637 | |
| 7638 The exact @dfn{human-readable} syntax is defined in the docstring of | |
| 7639 @code{edmacro-mode}. I'll repeat it here, for completeness. | |
| 7640 | |
| 7641 @quotation | |
| 7642 Format of keyboard macros during editing: | |
| 7643 | |
| 7644 Text is divided into @dfn{words} separated by whitespace. Except for | |
| 7645 the words described below, the characters of each word go directly as | |
| 7646 characters of the macro. The whitespace that separates words is | |
| 7647 ignored. Whitespace in the macro must be written explicitly, as in | |
| 7648 @kbd{foo @key{SPC} bar @key{RET}}. | |
| 7649 | |
| 7650 @itemize @bullet | |
| 7651 @item | |
| 7652 The special words @kbd{RET}, @kbd{SPC}, @kbd{TAB}, @kbd{DEL}, @kbd{LFD}, | |
| 7653 @kbd{ESC}, and @kbd{NUL} represent special control characters. The | |
| 7654 words must be written in uppercase. | |
| 7655 | |
| 7656 @item | |
| 7657 A word in angle brackets, e.g., @code{<return>}, @code{<down>}, or | |
| 7658 @code{<f1>}, represents a function key. (Note that in the standard | |
| 7659 configuration, the function key @code{<return>} and the control key | |
| 7660 @key{RET} are synonymous.) You can use angle brackets on the words | |
| 7661 @key{RET}, @key{SPC}, etc., but they are not required there. | |
| 7662 | |
| 7663 @item | |
| 7664 Keys can be written by their @sc{ascii} code, using a backslash followed | |
| 7665 by up to six octal digits. This is the only way to represent keys with | |
| 7666 codes above \377. | |
| 7667 | |
| 7668 @item | |
| 7669 One or more prefixes @kbd{M-} (meta), @kbd{C-} (control), @kbd{S-} | |
| 7670 (shift), @kbd{A-} (alt), @kbd{H-} (hyper), and @kbd{s-} (super) may | |
| 7671 precede a character or key notation. For function keys, the prefixes | |
| 7672 may go inside or outside of the brackets: @code{C-<down>} @equiv{} | |
| 7673 @code{<C-down>}. The prefixes may be written in any order: @kbd{M-C-x} | |
| 7674 @equiv{} @kbd{C-M-x}. | |
| 7675 | |
| 7676 Prefixes are not allowed on multi-key words, e.g., @kbd{C-abc}, except | |
| 7677 that the Meta prefix is allowed on a sequence of digits and optional | |
| 7678 minus sign: @kbd{M--123} @equiv{} @kbd{M-- M-1 M-2 M-3}. | |
| 7679 | |
| 7680 @item | |
| 7681 The @code{^} notation for control characters also works: @kbd{^M} | |
| 7682 @equiv{} @kbd{C-m}. | |
| 7683 | |
| 7684 @item | |
| 7685 Double angle brackets enclose command names: @code{<<next-line>>} is | |
| 7686 shorthand for @kbd{M-x next-line @key{RET}}. | |
| 7687 | |
| 7688 @item | |
| 7689 Finally, @code{REM} or @code{;;} causes the rest of the line to be | |
| 7690 ignored as a comment. | |
| 7691 @end itemize | |
| 7692 | |
| 7693 Any word may be prefixed by a multiplier in the form of a decimal number | |
| 7694 and @code{*}: @code{3*<right>} @equiv{} @code{<right> <right> <right>}, | |
| 7695 and @code{10*foo} @equiv{} | |
| 7696 @iftex | |
| 7697 @* | |
| 7698 @end iftex | |
| 7699 @code{foofoofoofoofoofoofoofoofoofoo}. | |
| 7700 | |
| 7701 Multiple text keys can normally be strung together to form a word, but | |
| 7702 you may need to add whitespace if the word would look like one of the | |
| 7703 above notations: @code{; ; ;} is a keyboard macro with three semicolons, | |
| 7704 but @code{;;;} is a comment. Likewise, @code{\ 1 2 3} is four keys but | |
| 7705 @code{\123} is a single key written in octal, and @code{< right >} is | |
| 7706 seven keys but @code{<right>} is a single function key. When in doubt, | |
| 7707 use whitespace. | |
| 7708 @end quotation | |
| 7709 | |
| 2537 | 7710 @node Q7.1.4, Q7.1.5, Q7.1.3, Advanced |
| 7711 @unnumberedsubsec Q7.1.4: What is the performance hit of @code{let}? | |
| 2459 | 7712 |
| 7713 In most cases, not noticeable. Besides, there's no avoiding | |
| 7714 @code{let}---you have to bind your local variables, after all. Some | |
| 7715 pose a question whether to nest @code{let}s, or use one @code{let} per | |
| 7716 function. I think because of clarity and maintenance (and possible | |
| 7717 future implementation), @code{let}-s should be used (nested) in a way to | |
| 7718 provide the clearest code. | |
| 7719 | |
| 2537 | 7720 @node Q7.1.5, Q7.1.6, Q7.1.4, Advanced |
| 7721 @unnumberedsubsec Q7.1.5: What is the recommended use of @code{setq}? | |
| 2459 | 7722 |
| 7723 @itemize @bullet | |
| 7724 @item Global variables | |
| 7725 | |
| 7726 You will typically @code{defvar} your global variable to a default | |
| 7727 value, and use @code{setq} to set it later. | |
| 7728 | |
| 7729 It is never a good practice to @code{setq} user variables (like | |
| 7730 @code{case-fold-search}, etc.), as it ignores the user's choice | |
| 7731 unconditionally. Note that @code{defvar} doesn't change the value of a | |
| 7732 variable if it was bound previously. If you wish to change a | |
| 7733 user-variable temporarily, use @code{let}: | |
| 7734 | |
| 7735 @lisp | |
| 7736 (let ((case-fold-search nil)) | |
| 7737 ... ; code with searches that must be case-sensitive | |
| 7738 ...) | |
| 7739 @end lisp | |
| 7740 | |
| 7741 You will notice the user-variables by their docstrings beginning with an | |
| 7742 asterisk (a convention). | |
| 7743 | |
| 7744 @item Local variables | |
| 7745 | |
| 7746 Bind them with @code{let}, which will unbind them (or restore their | |
| 7747 previous value, if they were bound) after exiting from the @code{let} | |
| 7748 form. Change the value of local variables with @code{setq} or whatever | |
| 7749 you like (e.g. @code{incf}, @code{setf} and such). The @code{let} form | |
| 7750 can even return one of its local variables. | |
| 7751 | |
| 7752 Typical usage: | |
| 7753 | |
| 7754 @lisp | |
| 7755 ;; iterate through the elements of the list returned by | |
| 7756 ;; `hairy-function-that-returns-list' | |
| 7757 (let ((l (hairy-function-that-returns-list))) | |
| 7758 (while l | |
| 7759 ... do something with (car l) ... | |
| 7760 (setq l (cdr l)))) | |
| 7761 @end lisp | |
| 7762 | |
| 7763 Another typical usage includes building a value simply to work with it. | |
| 7764 | |
| 7765 @lisp | |
| 7766 ;; Build the mode keymap out of the key-translation-alist | |
| 7767 (let ((inbox (file-truename (expand-file-name box))) | |
| 7768 (i 0)) | |
| 7769 ... code dealing with inbox ... | |
| 7770 inbox) | |
| 7771 @end lisp | |
| 7772 | |
| 7773 This piece of code uses the local variable @code{inbox}, which becomes | |
| 7774 unbound (or regains old value) after exiting the form. The form also | |
| 7775 returns the value of @code{inbox}, which can be reused, for instance: | |
| 7776 | |
| 7777 @lisp | |
| 7778 (setq foo-processed-inbox | |
| 7779 (let .....)) | |
| 7780 @end lisp | |
| 7781 @end itemize | |
| 7782 | |
| 2537 | 7783 @node Q7.1.6, Q7.1.7, Q7.1.5, Advanced |
| 7784 @unnumberedsubsec Q7.1.6: What is the typical misuse of @code{setq}? | |
| 2459 | 7785 |
| 7786 A typical misuse is probably @code{setq}ing a variable that was meant to | |
| 7787 be local. Such a variable will remain bound forever, never to be | |
| 7788 garbage-collected. For example, the code doing: | |
| 7789 | |
| 7790 @lisp | |
| 7791 (defun my-function (whatever) | |
| 7792 (setq a nil) | |
| 7793 ... build a large list ... | |
| 7794 ... and exit ...) | |
| 7795 @end lisp | |
| 7796 | |
| 7797 does a bad thing, as @code{a} will keep consuming memory, never to be | |
| 7798 unbound. The correct thing is to do it like this: | |
| 7799 | |
| 7800 @lisp | |
| 7801 (defun my-function (whatever) | |
| 7802 (let (a) ; default initialization is to nil | |
| 7803 ... build a large list ... | |
| 7804 ... and exit, unbinding `a' in the process ...) | |
| 7805 @end lisp | |
| 7806 | |
| 7807 Not only is this prettier syntactically, but it makes it possible for | |
| 7808 Emacs to garbage-collect the objects which @code{a} used to reference. | |
| 7809 | |
| 7810 Note that even global variables should not be @code{setq}ed without | |
| 7811 @code{defvar}ing them first, because the byte-compiler issues warnings. | |
| 7812 The reason for the warning is the following: | |
| 7813 | |
| 7814 @lisp | |
| 7815 (defun flurgoze nil) ; ok, global internal variable | |
| 7816 ... | |
| 7817 | |
| 7818 (setq flurghoze t) ; ops! a typo, but semantically correct. | |
| 7819 ; however, the byte-compiler warns. | |
| 7820 | |
| 7821 While compiling toplevel forms: | |
| 7822 ** assignment to free variable flurghoze | |
| 7823 @end lisp | |
| 7824 | |
| 2537 | 7825 @node Q7.1.7, Q7.1.8, Q7.1.6, Advanced |
| 7826 @unnumberedsubsec Q7.1.7: I like the @code{do} form of cl, does it slow things down? | |
| 2459 | 7827 |
| 7828 It shouldn't. Here is what Dave Gillespie has to say about cl.el | |
| 7829 performance: | |
| 7830 | |
| 7831 @quotation | |
| 7832 Many of the advanced features of this package, such as @code{defun*}, | |
| 7833 @code{loop}, and @code{setf}, are implemented as Lisp macros. In | |
| 7834 byte-compiled code, these complex notations will be expanded into | |
| 7835 equivalent Lisp code which is simple and efficient. For example, the | |
| 7836 forms | |
| 7837 | |
| 7838 @lisp | |
| 7839 (incf i n) | |
| 7840 (push x (car p)) | |
| 7841 @end lisp | |
| 7842 | |
| 7843 are expanded at compile-time to the Lisp forms | |
| 7844 | |
| 7845 @lisp | |
| 7846 (setq i (+ i n)) | |
| 7847 (setcar p (cons x (car p))) | |
| 7848 @end lisp | |
| 7849 | |
| 7850 which are the most efficient ways of doing these respective operations | |
| 7851 in Lisp. Thus, there is no performance penalty for using the more | |
| 7852 readable @code{incf} and @code{push} forms in your compiled code. | |
| 7853 | |
| 7854 @emph{Interpreted} code, on the other hand, must expand these macros | |
| 7855 every time they are executed. For this reason it is strongly | |
|
4905
755ae5b97edb
Change "special form" to "special operator" in our sources.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4759
diff
changeset
|
7856 recommended that code making heavy use of macros be compiled. A loop |
|
755ae5b97edb
Change "special form" to "special operator" in our sources.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4759
diff
changeset
|
7857 using @code{incf} a hundred times will execute considerably faster if |
|
755ae5b97edb
Change "special form" to "special operator" in our sources.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4759
diff
changeset
|
7858 compiled, and will also garbage-collect less because the macro expansion |
|
755ae5b97edb
Change "special form" to "special operator" in our sources.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4759
diff
changeset
|
7859 will not have to be generated, used, and thrown away a hundred times. |
| 2459 | 7860 |
| 7861 You can find out how a macro expands by using the @code{cl-prettyexpand} | |
| 7862 function. | |
| 7863 @end quotation | |
| 7864 | |
| 2537 | 7865 @node Q7.1.8, Q7.1.9, Q7.1.7, Advanced |
| 7866 @unnumberedsubsec Q7.1.8: I like recursion, does it slow things down? | |
| 2459 | 7867 |
| 7868 Yes. The Emacs byte-compiler cannot do much to optimize recursion. But | |
| 7869 think well whether this is a real concern in Emacs. Much of the Emacs | |
| 7870 slowness comes from internal mechanisms such as redisplay, or from the | |
| 7871 fact that it is an interpreter. | |
| 7872 | |
| 7873 Please try not to make your code much uglier to gain a very small speed | |
| 7874 gain. It's not usually worth it. | |
| 7875 | |
| 2537 | 7876 @node Q7.1.9, Q7.1.10, Q7.1.8, Advanced |
| 7877 @unnumberedsubsec Q7.1.9: How do I put a glyph as annotation in a buffer? | |
| 2459 | 7878 |
| 7879 Here is a solution that will insert the glyph annotation at the | |
| 7880 beginning of buffer: | |
| 7881 | |
| 7882 @lisp | |
| 7883 (make-annotation (make-glyph '([FORMAT :file FILE] | |
| 7884 [string :data "fallback-text"])) | |
| 7885 (point-min) | |
| 7886 'text | |
| 7887 (current-buffer)) | |
| 7888 @end lisp | |
| 7889 | |
| 7890 Replace @samp{FORMAT} with an unquoted symbol representing the format of | |
| 7891 the image (e.g. @code{xpm}, @code{xbm}, @code{gif}, @code{jpeg}, etc.) | |
| 7892 Instead of @samp{FILE}, use the image file name | |
| 7893 (e.g. | |
| 7894 @iftex | |
| 7895 @* | |
| 7896 @end iftex | |
| 7897 @file{/usr/local/lib/xemacs-21.4/etc/recycle.xpm}). | |
| 7898 | |
| 7899 You can turn this to a function (that optionally prompts you for a file | |
| 7900 name), and inserts the glyph at @code{(point)} instead of | |
| 7901 @code{(point-min)}. | |
| 7902 | |
| 2537 | 7903 @node Q7.1.10, Q7.1.11, Q7.1.9, Advanced |
| 7904 @unnumberedsubsec Q7.1.10: @code{map-extents} won't traverse all of my extents! | |
| 2459 | 7905 |
| 7906 I tried to use @code{map-extents} to do an operation on all the extents | |
| 7907 in a region. However, it seems to quit after processing a random number | |
| 7908 of extents. Is it buggy? | |
| 7909 | |
| 7910 No. The documentation of @code{map-extents} states that it will iterate | |
| 7911 across the extents as long as @var{function} returns @code{nil}. | |
| 7912 Unexperienced programmers often forget to return @code{nil} explicitly, | |
| 7913 which results in buggy code. For instance, the following code is | |
| 7914 supposed to delete all the extents in a buffer, and issue as many | |
| 7915 @samp{fubar!} messages. | |
| 7916 | |
| 7917 @lisp | |
| 7918 (map-extents (lambda (ext ignore) | |
| 7919 (delete-extent ext) | |
| 7920 (message "fubar!"))) | |
| 7921 @end lisp | |
| 7922 | |
| 7923 Instead, it will delete only the first extent, and stop right there -- | |
| 7924 because @code{message} will return a non-nil value. The correct code | |
| 7925 is: | |
| 7926 | |
| 7927 @lisp | |
| 7928 (map-extents (lambda (ext ignore) | |
| 7929 (delete-extent ext) | |
| 7930 (message "fubar!") | |
| 7931 nil)) | |
| 7932 @end lisp | |
| 7933 | |
| 2537 | 7934 @node Q7.1.11, Q7.2.1, Q7.1.10, Advanced |
| 7935 @unnumberedsubsec Q7.1.11: My elisp program is horribly slow. Is there an easy way to find out where it spends time? | |
| 2459 | 7936 @c New |
| 7937 | |
| 7938 @email{hniksic@@xemacs.org, Hrvoje Niksic} writes: | |
| 7939 @quotation | |
| 7940 Under XEmacs 20.4 and later you can use @kbd{M-x profile-key-sequence}, | |
| 7941 press a key (say @key{RET} in the Gnus Group buffer), and get the | |
| 7942 results using @kbd{M-x profile-results}. It should give you an idea of | |
| 7943 where the time is being spent. | |
| 7944 @end quotation | |
| 7945 | |
| 2537 | 7946 @unnumberedsec 7.2: Mathematics |
| 7947 | |
| 7948 @node Q7.2.1, Q7.2.2, Q7.1.11, Advanced | |
| 7949 @unnumberedsubsec Q7.2.1: What are bignums, ratios, and bigfloats in Lisp? | |
| 2459 | 7950 |
| 7951 Thanks to @email{james@@xemacs.org, Jerry James}, XEmacs 21.5.18 and | |
| 7952 later can use the capabilities of multiple-precision libraries that may | |
|
5739
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7953 be available for your platform. The GNU Multiple Precision (GMP), |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7954 Multiple Precision Integers and Rationals (MPIR), and BSD Multiple |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7955 Precision (MP) libraries are supported. GMP and MPIR give you |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7956 @dfn{bignums} (arbitrary precision integers), @dfn{ratios} (arbitrary |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7957 precision fractions), and @dfn{bigfloats} (arbitrary precision floating |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7958 point numbers). GMP and MPIR are better-supported by XEmacs. BSD MP |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7959 support does not include ratios or bigfloats. |
| 2459 | 7960 |
| 7961 In most cases, bignum support should be transparent to users and Lisp | |
| 7962 programmers. A bignum-enabled XEmacs will automatically convert from | |
|
5739
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7963 fixnums to bignums and back in pure integer arithmetic, and for GMP and |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7964 MPIR, from floats to bigfloats. (Bigfloats must be explicitly coerced |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
7965 to other types, even if they are exactly representable by less precise |
| 2459 | 7966 types.) The Lisp reader and printer have been enhanced to handle |
| 7967 bignums, as have the mathematical functions. Rationals (fixnums, | |
| 7968 bignums, and ratios) are printed using the @samp{%d}, @samp{%o}, | |
| 7969 @samp{%x}, and @samp{%u} format conversions. The read syntax for ratios | |
| 7970 is @samp{3/5}. | |
| 7971 | |
| 7972 User-visible changes in behavior include (in probable order of annoyance) | |
| 7973 | |
| 7974 @itemize | |
| 7975 @item | |
| 7976 Arithmetic can cause a segfault, depending on your MP library | |
| 2537 | 7977 @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. |
| 2459 | 7978 |
| 7979 @item | |
| 7980 Terminology is not Common-Lisp-conforming. For example, ``integer'' for | |
| 7981 Emacs Lisp means what Common Lisp calls ``fixnum''. This issue is being | |
| 7982 investigated, but the use of ``integer'' for fixnum is pervasive and may | |
| 7983 cause backward-compatibility and GNU-Emacs-compatibility problems. | |
| 7984 | |
| 7985 @item | |
| 7986 Many operations that used to cause a range error now succeed, with | |
| 7987 intermediate results and return values coerced to bignums as needed. | |
| 7988 | |
| 7989 @item | |
| 7990 An atom with ratio read syntax now returns a number, not a symbol. | |
| 7991 | |
| 7992 @item | |
| 7993 The @samp{%u} format conversion will now give an error if its argument | |
| 7994 is negative. (Without MP, it prints a number which Lisp can't read.) | |
| 7995 @end itemize | |
| 7996 | |
| 7997 @emph{Surgeon General's Warning}: The automatic conversions cannot be | |
| 7998 disabled at runtime. New functions have been added which produce | |
| 7999 ratios, so there should be few surprises with type conflicts, but they | |
| 8000 can't be ruled out. ``Arbitrary'' precision means precisely what it | |
| 8001 says. If you work with extremely large numbers, your machine may | |
| 8002 arbitrarily decide to hand you an unpleasant surprise rather than a | |
| 2537 | 8003 bignum @ref{Q7.2.2, XEmacs segfaults when I use very big numbers!}. |
| 2459 | 8004 |
|
5739
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
8005 To configure with GMP, add @samp{--enable-bignum=gmp} to your invocation |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
8006 of @file{configure}. For MPIR, use @samp{--enable-bignum=mpir}. For |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
8007 BSD MP, use @samp{--enable-bignum=mp}. |
| 2459 | 8008 |
| 8009 | |
| 2537 | 8010 @node Q7.2.2, Q7.2.3, Q7.2.1, Advanced |
| 8011 @unnumberedsubsec Q7.2.2: XEmacs segfaults when I use very big numbers! | |
| 2459 | 8012 |
| 8013 GMP by default allocates temporaries on the stack. If you run out of | |
| 8014 stack space, you're dead; there is no way that we know of to reliably | |
| 8015 detect this condition, because @samp{alloca} is typically implemented to | |
| 8016 be @emph{fast} rather than robust. If you just need a little more | |
| 8017 oomph, use a bigger stack (@emph{e.g.}, the @file{ulimit -s} command in | |
| 8018 bash(1)). If you want robustness at the cost of speed, configure GMP | |
| 8019 with @samp{--disable-alloca} and rebuild the GMP library. | |
| 8020 | |
| 8021 We do not know whether BSD MP uses @samp{alloca} or not. Please send | |
| 8022 any information you have as a bug report (@kbd{M-x report-xemacs-bug | |
| 8023 @key{RET}}), which will give us platform information. (We do know that | |
| 8024 BSD MP implementations vary across vendors, but how much, we do not know | |
| 8025 yet.) | |
| 8026 | |
| 8027 | |
| 2537 | 8028 @node Q7.2.3, Q7.2.4, Q7.2.2, Advanced |
| 8029 @unnumberedsubsec Q7.2.3: Bignums are really slow! | |
| 2459 | 8030 |
|
5739
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
8031 Many Unix and Linux distributions compile all packages for a generic |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
8032 version of the supported CPU, and this is costly. An optimized version |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
8033 can improve responiveness dramatically; see |
|
a2912073be85
Support bignums with MPIR. Add documentation on the bignum, ratio,
Jerry James <james@xemacs.org>
parents:
5551
diff
changeset
|
8034 @uref{http://gmplib.org/gmpbench.html}.) |
| 2459 | 8035 |
| 8036 | |
| 2537 | 8037 @node Q7.2.4, , Q7.2.3, Advanced |
| 8038 @unnumberedsubsec Q7.2.4: Equal bignums don't compare as equal! What gives? | |
| 2459 | 8039 |
| 8040 Ah, Grasshopper, I see you are using @code{(eq x y)}. The Bodhisattva | |
| 8041 CLTL2 warned of the illusion that equal numbers would be @samp{eq}! | |
| 8042 Meditate on the deeper truths of @samp{eql}, in which numbers of the same | |
| 8043 type which have equal values compare equal, and @samp{=}, which does any | |
| 8044 necessary type coercions before comparing for equality. | |
| 8045 | |
| 8046 Yeah, yeah, it has always worked for integer types, because fixnums and | |
| 8047 characters have an immediate representation. Sorry about that; | |
| 8048 arbitrary precision obviously requires consing new objects because the | |
| 8049 objects are ``large'' and of variable size, and the definition of | |
| 8050 @samp{eq} does not permit different objects to compare as equal. | |
| 8051 | |
| 8052 @node Other Packages, Current Events, Advanced, Top | |
| 8053 @unnumbered 8 Other External Packages | |
| 8054 | |
| 8055 This is part 8 of the XEmacs Frequently Asked Questions list. This | |
| 8056 section is devoted to miscellaneous external packages not covered | |
| 8057 elsewhere in XEmacs. | |
| 8058 | |
| 8059 @menu | |
| 2537 | 8060 8.0: TeX |
| 2459 | 8061 * Q8.0.1:: Is there something better than LaTeX mode? |
| 8062 * Q8.0.2:: What is AUCTeX? Where do you get it? | |
| 8063 * Q8.0.3:: Problems installing AUCTeX. | |
| 8064 * Q8.0.4:: How do I turn off current chapter from AUCTeX modeline? | |
| 8065 | |
| 8066 8.1: Other Unbundled Packages | |
| 8067 * Q8.1.1:: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 8068 * Q8.1.2:: Are there any Emacs Lisp Spreadsheets? | |
| 8069 * Q8.1.3:: Is there a MatLab mode? | |
| 8070 | |
| 8071 8.2: Environments Built Around XEmacs | |
| 8072 * Q8.2.1:: What are SPARCworks, EOS, and WorkShop? | |
| 8073 * Q8.2.2:: How do I start the Sun Workshop support in XEmacs 21? | |
| 8074 * Q8.2.3:: What is/was Energize? | |
| 8075 * Q8.2.4:: What is Infodock? | |
| 8076 @end menu | |
| 8077 | |
| 8078 @unnumberedsec 8.0: TeX | |
| 8079 | |
| 8080 @node Q8.0.1, Q8.0.2, Other Packages, Other Packages | |
| 8081 @unnumberedsubsec Q8.0.1: Is there something better than LaTeX mode? | |
| 2417 | 8082 |
| 8083 @email{dak@@fsnif.neuroinformatik.ruhr-uni-bochum.de, David Kastrup} writes: | |
| 8084 | |
| 8085 @quotation | |
| 8086 The standard TeX modes leave much to be desired, and are somewhat | |
| 2459 | 8087 leniently maintained. Serious TeX users use AUCTeX (@pxref{Q8.0.2, |
| 2417 | 8088 What is AUCTeX? Where do you get it?}). |
| 8089 @end quotation | |
| 8090 | |
| 2459 | 8091 @node Q8.0.2, Q8.0.3, Q8.0.1, Other Packages |
| 8092 @unnumberedsubsec Q8.0.2: What is AUCTeX? Where do you get it? | |
| 2417 | 8093 |
| 8094 AUCTeX is a complex and sophisticated editing package dedicated to TeX | |
| 8095 and related text formatting languages, including LaTeX and Texinfo. | |
| 8096 It provides support for running TeX on a file or part of a file, | |
| 8097 include files, and of course shortcuts for entering common TeX macros, | |
| 8098 LaTeX environments, etc, and for fontlock. | |
| 8099 | |
| 8100 AUCTeX is a standard package provided by XEmacs. You can get it as | |
| 8101 usual through the @kbd{M-x list-packages} interface. It is also | |
| 8102 included in the (non-Mule) SUMO package. The AUCTeX XEmacs package is | |
| 8103 maintained by Uwe Brauer <GET MAIL ADDRESS>. | |
| 8104 | |
| 8105 AUCTeX is extremely complicated, and its developers primarily | |
| 8106 use GNU Emacs. Not all features of the bleeding edge version | |
| 8107 of AUCTeX are immediately ported to XEmacs; if you need | |
| 8108 these, you may be better off getting the most recent versions | |
| 8109 from the GNU AUCTeX project on @uref{http://savannah.gnu.org}. | |
| 8110 | |
| 2459 | 8111 @node Q8.0.3, Q8.0.4, Q8.0.2, Other Packages |
| 8112 @unnumberedsubsec Q8.0.3: Problems installing AUCTeX. | |
| 2417 | 8113 |
| 8114 @email{vroonhof@@math.ethz.ch, Jan Vroonhof} writes: | |
| 8115 | |
| 8116 @quotation | |
| 8117 AUCTeX works fine on both stock Emacs and XEmacs has been doing so for | |
| 8118 a very very long time. This is mostly due to the work of | |
| 8119 @email{abraham@@dina.kvl.dk, Per Abrahamsen} (clap clap) in particular his @file{easymenu} | |
| 8120 package. Which leads to what is probably the problem... | |
| 8121 @end quotation | |
| 8122 | |
| 8123 Most problems with AUCTeX are one of two things: | |
| 8124 | |
| 8125 @itemize @bullet | |
| 8126 @item | |
| 8127 The TeX-lisp-directory in @file{tex-site.el} and the makefile don't | |
| 8128 match. | |
| 8129 | |
| 8130 Fix: make sure you configure AUCTeX properly @strong{before} installing. | |
| 8131 | |
| 8132 @item | |
| 8133 You have an old version of easymenu.el in your path. | |
| 8134 | |
| 8135 Fix: use @code{locate-library} and remove old versions to make sure it | |
| 8136 @strong{only} finds the one that came with XEmacs. | |
| 8137 @end itemize | |
| 8138 | |
| 2459 | 8139 @node Q8.0.4, Q8.1.1, Q8.0.3, Other Packages |
| 8140 @unnumberedsubsec Q8.0.4: How do I turn off current chapter from AUCTeX modeline? | |
| 2417 | 8141 |
| 8142 With AUCTeX, fast typing is hard because the current chapter, section | |
| 8143 etc. are given in the modeline. How can I turn this off? | |
| 8144 | |
| 8145 It's not AUCTeX, it comes from @code{func-menu} in @file{func-menu.el}. | |
| 8146 | |
| 8147 @c Add this code to your @file{init.el} to turn it off: | |
| 8148 @c | |
| 8149 @c @lisp | |
| 8150 @c (setq fume-display-in-modeline-p nil) | |
| 8151 @c @end lisp | |
| 8152 @c | |
| 8153 @c Or just add a hook to @code{TeX-mode-hook} to turn it off only for TeX | |
| 8154 @c mode: | |
| 8155 @c | |
| 8156 @c @lisp | |
| 8157 @c (add-hook 'TeX-mode-hook | |
| 8158 @c '(lambda () (setq fume-display-in-modeline-p nil))) | |
| 8159 @c @end lisp | |
| 8160 @c | |
| 8161 @email{dhughes@@origin-at.co.uk, David Hughes} writes: | |
| 8162 | |
| 8163 @quotation | |
| 8164 Try this; you'll still get the function name displayed in the modeline, | |
| 8165 but it won't attempt to keep track when you modify the file. To refresh | |
| 8166 when it gets out of synch, you simply need click on the @samp{Rescan | |
| 8167 Buffer} option in the function-menu. | |
| 8168 | |
| 8169 @lisp | |
| 8170 (setq-default fume-auto-rescan-buffer-p nil) | |
| 8171 @end lisp | |
| 8172 @end quotation | |
| 8173 | |
| 2459 | 8174 @unnumberedsec 8.1: Other Unbundled Packages |
| 8175 | |
| 8176 @node Q8.1.1, Q8.1.2, Q8.0.4, Other Packages | |
| 8177 @unnumberedsubsec Q8.1.1: Is there a reason for an Emacs package not to be included in XEmacs? | |
| 2417 | 8178 |
| 8179 The reason for an Emacs package not to be included in XEmacs is | |
| 8180 usually one or more of the following: | |
| 8181 | |
| 8182 @enumerate | |
| 8183 @item | |
| 8184 The package has not been ported to XEmacs. This will typically happen | |
| 8185 when it uses GNU-Emacs-specific features, which make it fail under | |
| 8186 XEmacs. | |
| 8187 | |
| 8188 Porting a package to XEmacs can range from a trivial amount of change to | |
| 8189 a partial or full rewrite. Fortunately, the authors of modern packages | |
| 8190 usually choose to support both Emacsen themselves. | |
| 8191 | |
| 8192 @item | |
| 8193 The package has been decided not to be appropriate for XEmacs. It may | |
| 8194 have an equivalent or better replacement within XEmacs, in which case | |
| 8195 the developers may choose not to burden themselves with supporting an | |
| 8196 additional package. | |
| 8197 | |
| 8198 Each package bundled with XEmacs means more work for the maintainers, | |
| 8199 whether they want it or not. If you are ready to take over the | |
| 8200 maintenance responsibilities for the package you port, be sure to say | |
| 8201 so---we will more likely include it. | |
| 8202 | |
| 8203 @item | |
| 8204 The package simply hasn't been noted by the XEmacs development. If | |
| 8205 that's the case, the messages like yours are very useful for attracting | |
| 8206 our attention. | |
| 8207 | |
| 8208 @item | |
| 8209 The package was noted by the developers, but they simply haven't yet | |
| 8210 gotten around to including/porting it. Wait for the next release or, | |
| 8211 even better, offer your help. It will be gladly accepted and | |
| 8212 appreciated. | |
| 8213 @end enumerate | |
| 8214 | |
| 2459 | 8215 @node Q8.1.2, Q8.1.3, Q8.1.1, Other Packages |
| 8216 @unnumberedsubsec Q8.1.2: Are there any Emacs Lisp Spreadsheets? | |
| 2417 | 8217 |
| 8218 Yes. Check out @dfn{dismal} (which stands for Dis' Mode Ain't Lotus) at | |
| 428 | 8219 @iftex |
| 8220 @* | |
| 8221 @end iftex | |
| 2459 | 8222 @uref{http://acs.ist.psu.edu/dismal/dismal.html}. |
| 8223 | |
| 8224 @node Q8.1.3, Q8.2.1, Q8.1.2, Other Packages | |
| 8225 @unnumberedsubsec Q8.1.3: Is there a MatLab mode? | |
| 2417 | 8226 |
| 8227 Yes, a matlab mode and other items are available at the | |
| 2459 | 8228 @uref{http://www.mathworks.com/matlabcentral/files/104/matlab.el}. |
| 8229 | |
| 8230 @unnumberedsec 8.2: Environments Built Around XEmacs | |
| 8231 | |
| 8232 @node Q8.2.1, Q8.2.2, Q8.1.3, Other Packages | |
| 8233 @unnumberedsubsec Q8.2.1: What are SPARCworks, EOS, and WorkShop? | |
| 2417 | 8234 |
| 8235 SPARCworks was a development environment from Sun (circa 1993-1996) | |
| 8236 and consisted of compilers (C, C++, FORTRAN 77, Fortran 90, Ada, and | |
| 8237 Pascal), a debugger, and other tools such as TeamWare (for | |
| 8238 configuration management), MakeTool, etc. | |
| 428 | 8239 |
| 8240 EOS is the integration of XEmacs with the SPARCworks debugger. It | |
| 8241 allows one to use an XEmacs frame to view code (complete with | |
| 8242 fontification, etc.), set breakpoints, print variables, etc., while | |
| 2417 | 8243 using the SPARCworks debugger. |
| 8244 | |
| 8245 EOS stands for "Era on SPARCworks"; Era stood for "Emacs Rewritten | |
| 8246 Again" and was the name used by Sun for its modified version of Lucid | |
| 8247 Emacs (later XEmacs) in the early-mid 90's. This is documented in | |
| 8248 more detail in the history section of the XEmacs About page. | |
| 8249 | |
| 8250 EOS was replaced around 1996 with a newer graphical development | |
| 8251 environment called Sun WorkShop. The current status of this is | |
| 8252 unknown. | |
| 8253 | |
| 2459 | 8254 @node Q8.2.2, Q8.2.3, Q8.2.1, Other Packages |
| 8255 @unnumberedsubsec Q8.2.2: How do I start the Sun Workshop support in XEmacs 21? | |
| 428 | 8256 |
| 8257 Add the switch ---with-workshop to the configure command when building | |
| 8258 XEmacs and put the following in one of your startup files | |
| 8259 (e.g. site-start.el or .emacs): | |
| 8260 | |
| 8261 @lisp | |
| 8262 (when (featurep 'tooltalk) | |
| 8263 (load "tooltalk-macros") | |
| 8264 (load "tooltalk-util") | |
| 8265 (load "tooltalk-init")) | |
| 8266 (when (featurep 'sparcworks) | |
| 8267 (load "sunpro-init") | |
| 8268 (load "ring") | |
| 8269 (load "comint") | |
| 8270 (load "annotations") | |
| 8271 (sunpro-startup)) | |
| 8272 @end lisp | |
| 8273 | |
| 8274 If you are not using the latest Workshop (5.0) you have to apply the | |
| 8275 following patch: | |
| 8276 | |
| 8277 @format | |
| 8278 --- /opt/SUNWspro/lib/eserve.el.ORIG Fri May 14 15:23:26 1999 | |
| 8279 +++ /opt/SUNWspro/lib/eserve.el Fri May 14 15:24:54 1999 | |
| 8280 @@@@ -42,7 +42,7 @@@@ | |
| 8281 (defvar running-xemacs nil "t if we're running XEmacs") | |
| 8282 (defvar running-emacs nil "t if we're running GNU Emacs 19") | |
| 438 | 8283 |
| 428 | 8284 -(if (string-match "^\\(19\\|20\\)\..*\\(XEmacs\\|Lucid\\)" emacs-version) |
| 8285 +(if (string-match "\\(XEmacs\\|Lucid\\)" emacs-version) | |
| 8286 (setq running-xemacs t) | |
| 8287 (setq running-emacs t)) | |
| 438 | 8288 @end format |
| 428 | 8289 |
| 2459 | 8290 @node Q8.2.3, Q8.2.4, Q8.2.2, Other Packages |
| 8291 @unnumberedsubsec Q8.2.3: What is/was Energize? | |
| 2417 | 8292 |
| 8293 The "Energize Programming System" was a C and C++ development environment | |
| 8294 sold by Lucid, Inc. It was the reason why Lucid Emacs, now XEmacs, was | |
| 8295 created in the first place. Unfortunately, Lucid went out of business in | |
| 8296 1994. The rights to sell it in Japan were purchased by INS | |
| 8297 Engineering (which briefly employed Stig Hackvan aka Jonathan | |
| 8298 Stigelman to work on Japanese support for XEmacs, in late 1994 and | |
| 8299 early 1995) and Tartan bought the rights to sell it in the rest of the | |
| 8300 world. However, INS is not selling Energize at this point and may or | |
| 8301 may not have ever done so; Tartan certainly never did. | |
| 8302 | |
| 2459 | 8303 @node Q8.2.4, , Q8.2.3, Other Packages |
| 8304 @unnumberedsubsec Q8.2.4: What is Infodock? | |
| 428 | 8305 |
| 660 | 8306 @uref{http://sourceforge.net/projects/infodock/, InfoDock} is an |
| 8307 integrated productivity toolset, mainly aimed at technical people, | |
| 8308 hosted at SourceForge. | |
| 428 | 8309 |
| 8310 InfoDock is built atop the XEmacs variant of GNU Emacs and so has all of | |
| 8311 the power of Emacs, but with an easier to use and more comprehensive | |
| 8312 menu-based user interface. The bottom portion of this text describes | |
| 8313 how it differs from XEmacs and GNU Emacs from the Free Software | |
| 8314 Foundation. | |
| 8315 | |
| 8316 InfoDock is aimed at people who want a free, turn-key productivity | |
| 8317 environment. Although InfoDock is customizable, it is not intended for | |
| 8318 people who like basic versions of Emacs which need to be customized | |
| 8319 extensively for local use; standard Emacs distributions are better for | |
| 8320 such uses. InfoDock is for those people who want a complete, | |
| 8321 pre-customized environment in one package, which they need not touch | |
| 8322 more than once or twice a year to update to new revisions. | |
| 8323 | |
| 8324 InfoDock is pre-built for SPARC SunOS/Solaris systems, PA-RISC HP-UX, | |
| 8325 and Intel Linux systems. It is intended for use on a color display, | |
| 8326 although most features will work on monochrome monitors. Simply unpack | |
| 8327 InfoDock according to the instructions in the ID-INSTALL file and you | |
| 8328 are ready to run. | |
| 8329 | |
| 8330 The InfoDock Manual is concise, yet sufficient as a user guide for users | |
| 8331 who have never used an Emacs-type editor before. For users who are | |
| 8332 already familiar with Emacs, it supplements the information in the GNU | |
| 8333 Emacs Manual. | |
| 8334 | |
| 8335 InfoDock menus are much more extensive and more mature than standard | |
| 8336 Emacs menus. Each menu offers a @samp{Manual} item which displays | |
| 8337 documentation associated with the menu's functions. | |
| 8338 | |
| 8339 @noindent | |
| 8340 Four types of menubars are provided: | |
| 8341 @enumerate | |
| 8342 @item | |
| 8343 An extensive menubar providing access to global InfoDock commands. | |
| 8344 @item | |
| 8345 Mode-specific menubars tailored to the current major mode. | |
| 8346 @item | |
| 8347 A simple menubar for basic editing to help novices get started with InfoDock. | |
| 8348 @item | |
| 8349 The standard XEmacs menubar. | |
| 8350 @end enumerate | |
| 8351 | |
| 8352 Most modes also include mode-specific popup menus. Additionally, region and | |
| 8353 rectangle popup menus are included. | |
| 8354 | |
| 8355 @samp{Hyperbole}, the everyday information manager, is a core part of | |
| 8356 InfoDock. This provides context-sensitive mouse keys, a rolodex-type | |
| 8357 contact manager, programmable hypertext buttons, and an autonumbered | |
| 8358 outliner with embedded hyperlink anchors. | |
| 8359 | |
| 8360 The @samp{OO-Browser}, a multi-language object-oriented code browser, is a | |
| 8361 standard part of InfoDock. | |
| 8362 | |
| 8363 InfoDock saves a more extensive set of user options than other Emacs | |
| 8364 versions. | |
| 8365 | |
| 8366 InfoDock inserts a useful file header in many file types, showing the | |
| 8367 author, summary, and last modification time of each file. A summary | |
| 8368 program can then be used to summarize all of the files in a directory, | |
| 8369 for easy MANIFEST file creation. | |
| 8370 | |
| 8371 Your working set of buffers is automatically saved and restored (if you | |
| 8372 answer yes to a prompt) between InfoDock sessions. | |
| 8373 | |
| 8374 Refined color choices for code highlighting are provided for both dark and | |
| 8375 light background display frames. | |
| 8376 | |
| 8377 The @kbd{C-z} key prefix performs frame-based commands which parallel the | |
| 8378 @kbd{C-x} key prefix for window-based commands. | |
| 8379 | |
| 8380 The Smart Menu system is included for producing command menus on dumb | |
| 8381 terminals. | |
| 8382 | |
| 8383 Lisp libraries are better categorized according to function. | |
| 8384 | |
| 8385 Extensions and improvements to many areas of Emacs are included, such as: | |
| 8386 paragraph filling, mail reading with Rmail, shell handling, outlining, code | |
| 8387 highlighting and browsing, and man page browsing. | |
| 8388 | |
| 8389 InfoDock questions, answers and discussion should go to the mail list | |
| 8390 @iftex | |
| 8391 @* | |
| 8392 @end iftex | |
| 8393 @email{infodock@@infodock.com}. Use | |
| 8394 @email{infodock-request@@infodock.com} to be added or removed from the | |
| 8395 list. Always include your InfoDock version number when sending help | |
| 8396 requests. | |
| 8397 | |
| 2459 | 8398 @node Current Events, Legacy Versions, Other Packages, Top |
| 8399 @unnumbered 9 What the Future Holds | |
| 8400 | |
| 8401 This is part 9 of the XEmacs Frequently Asked Questions list. This | |
| 611 | 8402 section will change frequently, and (in theory) should contain any |
| 8403 interesting items that have transpired recently. (But in practice it's | |
| 8404 not getting updated like this.) | |
| 8405 | |
| 8406 This section also contains descriptions of the new features in all the | |
| 8407 recent releases of XEmacs. For the most part, the information below is | |
| 8408 a synopsis of the more complete information that can be found in the | |
| 8409 file @file{NEWS} in the @file{etc} directory of the XEmacs distribution. | |
| 8410 You can view this file in XEmacs using @kbd{C-h n} or the @samp{Help} | |
| 8411 menu. | |
| 8412 | |
| 8413 Information on older versions of XEmacs can be find in @file{ONEWS} in | |
| 8414 the same directory, or @file{OONEWS} for really old versions. | |
| 8415 | |
| 428 | 8416 @menu |
| 2537 | 8417 9.0: Changes |
| 2459 | 8418 * Q9.0.1:: What new features will be in XEmacs soon? |
| 8419 * Q9.0.2:: What's new in XEmacs 21.4? | |
| 8420 * Q9.0.3:: What's new in XEmacs 21.1? | |
| 8421 * Q9.0.4:: What's new in XEmacs 20.4? | |
| 8422 * Q9.0.5:: What's new in XEmacs 20.3? | |
| 8423 * Q9.0.6:: What's new in XEmacs 20.2? | |
| 428 | 8424 @end menu |
| 8425 | |
| 2459 | 8426 @unnumberedsec 9.0: Changes |
| 8427 | |
| 8428 @node Q9.0.1, Q9.0.2, Current Events, Current Events | |
| 8429 @unnumberedsubsec Q9.0.1: What new features will be in XEmacs soon? | |
| 611 | 8430 |
| 2417 | 8431 #### Write me. |
| 428 | 8432 |
| 2459 | 8433 @node Q9.0.2, Q9.0.3, Q9.0.1, Current Events |
| 8434 @unnumberedsubsec Q9.0.2: What's new in XEmacs 21.4? | |
| 611 | 8435 |
| 8436 21.4 was the "stable" version of the 21.2 series, which was considered | |
| 8437 "experimental" throughout its life; thus there were no "official" | |
| 8438 releases at all. In essence, XEmacs is now following the "alternating" | |
| 8439 scheme of Linux, where at any point there are at least two different | |
| 8440 development branches, one "stable" and one "experimental". Periodic | |
| 8441 releases happen in both branches, but those in the experimental branch | |
| 8442 are not tested as well, and there's no guarantee they will work at all. | |
| 4311 | 8443 The experimental branch is open to any and all code that's acceptable |
| 611 | 8444 to the developers; the stable branch, however, is in general limited |
| 8445 only to bug fixes, and all contributions are carefully reviewed to make | |
| 8446 sure they will increase and not decrease stability. | |
| 8447 | |
| 8448 21.3 never existed at all; it was decided to follow the Linux scheme | |
| 8449 exactly, where odd-numbered series are experimental and even-numbered | |
| 8450 ones stable. | |
| 8451 | |
| 8452 The following lists summarizes the essential changes made in this | |
| 8453 version. For a fuller list, see the @file{NEWS} in the @file{etc} | |
| 8454 directory of the XEmacs distribution, or use @kbd{C-h n} or the | |
| 8455 @samp{Help} menu to view this file inside of XEmacs. | |
| 8456 | |
| 676 | 8457 @unnumberedsubsubsec User-visible changes in XEmacs 21.4 |
| 611 | 8458 |
| 8459 @itemize @bullet | |
| 8460 | |
| 8461 @item | |
| 8462 The delete key now deletes forward by default. | |
| 8463 @item | |
| 8464 Shifted motion keys now select text by default. | |
| 8465 @item | |
| 8466 You can now build XEmacs with support for GTK+ widget set. | |
| 8467 @item | |
| 8468 ~/.xemacs/init.el is now the preferred location for the init | |
| 8469 file. (XEmacs now supports a `~/.xemacs/init.el' startup file. Custom | |
| 8470 file will move to ~/.xemacs/custom.el.) | |
| 8471 @item | |
| 8472 Much-improved sample init.el, showing how to use many useful features. | |
| 8473 @item | |
| 8474 XEmacs support for menu accelerators has been much improved. | |
| 8475 @item | |
| 8476 Default menubar improvements. (Default menubar has many new commands and | |
| 8477 better organization. The font-menu is now available under MS Windows.) | |
| 8478 @item | |
| 2417 | 8479 Dialog box improvements, including a real file dialog box. (XEmacs now |
| 8480 has a proper file dialog box under MS Windows (and GTK)! The old | |
| 8481 clunky file dialog box is improved. Keyboard traversal now works | |
| 8482 correctly in MS Windows dialog boxes. There is a Search dialog box | |
| 8483 available from @samp{Edit->Find...}) | |
| 611 | 8484 @item |
| 8485 New buffer tabs. | |
| 8486 @item | |
| 8487 There is a new MS Windows installer, netinstall, ported from Cygwin. | |
| 8488 @item | |
| 8489 The subprocess quote-handling mechanism under Windows is much improved. | |
| 8490 @item | |
| 8491 Printing support now available under MS Windows. | |
| 8492 @item | |
| 8493 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).) | |
| 8494 @item | |
| 8495 Mail spool locking now works correctly. | |
| 8496 @item | |
| 8497 International support changes. (The default coding-priority-list is now | |
| 8498 safer. International keysyms are now supported under X. MS Windows | |
| 8499 1251 code page now supported. Czech, Thai, Cyrillic-KOI8, Vietnamese, | |
| 8500 Ethiopic now supported. Proper support for words in Latin 3 and Latin | |
| 8501 4.) | |
| 8502 @item | |
| 8503 Help buffers contain hyperlinks, and other changes. | |
| 8504 @item | |
| 8505 The modeline's text is now scrollable. | |
| 8506 @item | |
| 8507 The mouse wheel under MS Windows now functions correctly. | |
| 8508 @item | |
| 8509 Interactive searching and matching case improvements. (Incremental search will now highlight all visible matches. Interactive searches always respect uppercase characters.) | |
| 8510 @item | |
| 8511 Rectangle functions rewritten to avoid inserting extra spaces. | |
| 8512 @item | |
| 8513 New command `kill-entire-line' that always kills the entire line. | |
| 8514 @item | |
| 8515 Default values correctly stored in minibuffer histories. | |
| 8516 @item | |
| 8517 You can now create "indirect buffers", like in GNU Emacs. | |
| 8518 @item | |
| 8519 Pixel-based scrolling has been implemented. | |
| 8520 @item | |
| 8521 Operation progress can be displayed using graphical widgets. | |
| 8522 @item | |
| 8523 User names following a tilde can now be completed at file name prompts. | |
| 8524 @item | |
| 8525 XEmacs can now play sound using Enlightenment Sound Daemon (ESD). | |
| 8526 @item | |
| 8527 X-Face support is now available under MS Windows. | |
| 8528 @item | |
| 8529 The PostgreSQL Relational Database Management System is now supported. | |
| 8530 @item | |
| 8531 Indentation no longer indents comments that begin at column zero. | |
| 8532 @item | |
| 8533 Face and variable settings can have comments in Customize. | |
| 8534 @item | |
| 8535 New locations for early package hierarchies. | |
| 8536 @item | |
| 8537 The `auto-save' library has been greatly improved. | |
| 8538 @item | |
| 8539 New variable `mswindows-alt-by-itself-activates-menu'. | |
| 8540 @item | |
| 8541 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.) | |
| 8542 @item | |
| 8543 Etags changes. See @file{NEWS} for full details. | |
| 8544 @end itemize | |
| 8545 | |
| 676 | 8546 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.4 |
| 611 | 8547 |
| 8548 Not yet written. | |
| 8549 | |
| 661 | 8550 @c APA: Texi2html produces invalid HTML from an empty list of bullets! |
| 8551 @c Please uncomment following list when it does contain bullets. | |
| 8552 @c @itemize @bullet | |
| 8553 @c @end itemize | |
| 611 | 8554 |
| 2459 | 8555 @node Q9.0.3, Q9.0.4, Q9.0.2, Current Events |
| 8556 @unnumberedsubsec Q9.0.3: What's new in XEmacs 21.1? | |
| 611 | 8557 |
| 8558 21.1 was the "stable" version of "experimental" 21.0 series. | |
| 2459 | 8559 @xref{Q9.0.2, What's new in XEmacs 21.4?}. |
| 611 | 8560 |
| 8561 The following lists summarizes the essential changes made in this | |
| 8562 version. For a fuller list, see the @file{NEWS} in the @file{etc} | |
| 8563 directory of the XEmacs distribution, or use @kbd{C-h n} or the | |
| 8564 @samp{Help} menu to view this file inside of XEmacs. | |
| 8565 | |
| 676 | 8566 @unnumberedsubsubsec User-visible changes in XEmacs 21.1 |
| 611 | 8567 |
| 8568 @itemize @bullet | |
| 8569 | |
| 8570 @item | |
| 2459 | 8571 XEmacs is now supported under Microsoft Windows 95/98 and Windows |
| 2417 | 8572 NT/2000/XP operating systems. To discuss Windows-specific issues, |
| 8573 subscribe to the mailing list at | |
| 8574 @email{xemacs-winnt-request@@xemacs.org}. | |
| 611 | 8575 |
| 8576 @item | |
| 8577 XEmacs has been unbundled into constituent installable packages. | |
| 8578 | |
| 8579 @item | |
| 8580 @strong{Other notable changes}: The @samp{Options} menu has been ported to | |
| 8581 Custom; XEmacs now is able to choose X visuals and use private | |
| 8582 colormaps; You can drag the vertical divider of "horizontally" | |
| 8583 (side-by-side) split windows. | |
| 8584 | |
| 8585 @item | |
| 8586 @strong{Building changes}: XEmacs can be built with support for 31-bit Lisp | |
| 8587 integers and 32-bit pointers (previously, it was 28-bit integers and | |
| 8588 pointers); XEmacs can be built with LDAP support; @file{dir} files can be | |
| 8589 removed in the Info subsystem, and will be regenerated on-the-fly. | |
| 8590 | |
| 8591 @item | |
| 8592 @strong{New packages}: @file{imenu}, @file{popper}, @file{gdb-highlight} | |
| 8593 | |
| 8594 @item | |
| 8595 @strong{Package changes}: Many changes to @file{cc-mode}, @file{gnus}, | |
| 8596 @file{gnuclient}. See @file{NEWS} for full details. | |
| 8597 | |
| 8598 @item | |
| 8599 @strong{New commands, variables and functions}: | |
| 8600 @code{center-to-window-line} (like @code{recenter} but doesn't force a | |
| 8601 redisplay); variable @code{user-full-name} (customize what your full | |
| 8602 name looks like in mail); @kbd{M-x customize-changed-options} (customize | |
| 8603 options whose default values changes because you upgraded your XEmacs); | |
| 8604 @kbd{M-x add-log-convert} (converts an old-style ChangeLog buffer to | |
| 8605 new-style); @kbd{M-x zap-up-to-char} (like @code{zap-to-char} but | |
| 8606 doesn't delete the char searched for); commands to store, retrieve and | |
| 8607 increment numbers in registers, useful for macros. | |
| 8608 | |
| 8609 @item | |
| 8610 @strong{Changes to commands, variables, and functions}: @kbd{M-x | |
| 8611 query-replace} and friends operate only on the region when it's active; | |
| 8612 @code{echo-keystrokes} can now be a floating-point number; @kbd{M-.} | |
| 8613 searches exact tag matches before inexact ones; function | |
| 8614 @code{user-full-name} with no arguments returns the var | |
| 8615 @code{user-full-name}; a prefix arg to @kbd{M-:} and @kbd{C-h c} inserts | |
| 8616 the result in the current buffer. | |
| 1138 | 8617 |
| 611 | 8618 @item |
| 8619 @strong{Other changes}: Under X, new application class @samp{XEmacs}; | |
| 8620 byte-compilation of user-specs now works. | |
| 8621 | |
| 8622 @item | |
| 8623 @strong{XEmacs/Mule (internationalization) changes}: Mule support now | |
| 8624 works on TTY's; Egg/SJ3 input method now officially supported (Quail and | |
| 8625 Egg/Skk already available through LEIM since 20.3); localized Japanese | |
| 8626 menubars if XEmacs is built with the right support. | |
| 8627 | |
| 8628 @end itemize | |
| 8629 | |
| 676 | 8630 @unnumberedsubsubsec Lisp and internal changes in XEmacs 21.1 |
| 611 | 8631 |
| 8632 @itemize @bullet | |
| 8633 | |
| 8634 @item | |
| 8635 @strong{Specifier changes}: The window locale now has a higher | |
| 8636 precedence than the buffer locale when instantiating; new macro | |
| 8637 @code{let-specifier}; new specifiers | |
| 8638 @code{vertical-scrollbar-visible-p}, horizontal-scrollbar-visible-p', | |
| 8639 @code{scrollbar-on-left-p}, @code{scrollbar-on-top-p}, | |
| 8640 @code{vertical-divider-always-visible-p}, | |
| 8641 @code{vertical-divider-shadow-thickness}, | |
| 8642 @code{vertical-divider-line-width}, @code{vertical-divider-spacing}; | |
| 8643 specifiers and symbols whose value is a specifier allowed as modeline | |
| 8644 specifications. | |
| 8645 | |
| 8646 @item | |
| 8647 @strong{Frame focus changes}: @code{focus-follows-mouse} works like FSF, | |
| 8648 prevents any attempt to permanently change the selected frame; new | |
| 8649 function @code{focus-frame} sets the window system focus a frame; new | |
|
4905
755ae5b97edb
Change "special form" to "special operator" in our sources.
Aidan Kehoe <kehoea@parhasard.net>
parents:
4759
diff
changeset
|
8650 macros @code{save-selected-frame} and @code{with-selected-frame}. |
| 611 | 8651 |
| 8652 @item | |
| 8653 @strong{Window function changes}: @code{select-window} now has optional | |
| 8654 argument @var{NORECORD} to inhibit recording a buffer change; | |
| 8655 @code{vertical-motion} now correctly handles optional @var{WINDOW} | |
| 8656 argument and has new optional argument @var{PIXELS}, to have the | |
| 8657 returned values be in pixels; new function | |
| 8658 @code{vertical-motion-pixels}; new functions | |
| 8659 @code{window-text-area-pixel-@{width,height,edges@}}; new functions | |
| 8660 @code{shrink-window-pixels} and @code{enlarge-window-pixels}; new | |
| 8661 function @code{window-displayed-text-pixel-height}. | |
| 8662 | |
| 8663 @item | |
| 8664 @strong{Other function changes}: Arithmetic comparison functions | |
| 8665 @code{<}, @code{>}, @code{=}, @code{/=} now accept a variable number of | |
| 8666 arguments; hashtables now have a consistent read/print syntax; keyword | |
| 8667 symbols cannot be set to a value other than themselves; @code{concat} no | |
| 8668 longer accepts integer arguments; new function @code{string}, like | |
| 8669 @code{list}, @code{vector}, etc.; new function @code{temp-directory} | |
| 8670 (OS-independent way to get a temp directory); @code{load-average} has | |
| 8671 optional argument @var{USE-FLOATS}; @code{make-event} implemented | |
| 8672 completely; new function @code{function-interactive} (returns a | |
| 8673 function's interactive spec); new functions @code{lmessage}, | |
| 8674 @code{lwarn} (printf-like versions of @code{display-wessage}, | |
| 8675 @code{display-warning}); new keyword @code{:version} to | |
| 8676 @code{defcustom}. | |
| 8677 | |
| 8678 @item | |
| 8679 @strong{Performance}: when the new GNU Malloc aka Doug Lea Malloc is | |
| 8680 available, it will be used (better performance on libc6 Linux systems); | |
| 8681 tracking line-numbers in modeline is now efficient; profiling records a | |
| 8682 call-count of all called functions, retrievable through | |
| 8683 @code{profile-call-count-results}. | |
| 8684 | |
| 8685 @item | |
| 8686 @strong{Startup and path searching}: code to assemble paths at startup | |
| 8687 rewritten for new package system; new function @code{split-path} (splits | |
| 8688 by @code{path-separator}); @code{Info-default-directory-list} obsolete, | |
| 8689 use @code{Info-directory-list} instead; site-lisp is deprecated and no | |
| 8690 longer on the load-path by default. | |
| 8691 | |
| 8692 @end itemize | |
| 8693 | |
| 2459 | 8694 @node Q9.0.4, Q9.0.5, Q9.0.3, Current Events |
| 8695 @unnumberedsubsec Q9.0.4: What's new in XEmacs 20.4? | |
| 611 | 8696 |
| 8697 XEmacs 20.4 is a bugfix release with no user-visible changes. | |
| 8698 @c Filled in from NEWS file of 20.5-b33 | |
| 8699 | |
| 2459 | 8700 @node Q9.0.5, Q9.0.6, Q9.0.4, Current Events |
| 8701 @unnumberedsubsec Q9.0.5: What's new in XEmacs 20.3? | |
| 428 | 8702 |
| 8703 XEmacs 20.3 was released in November 1997. It contains many bugfixes, | |
| 8704 and a number of new features, including Autoconf 2 based configuration, | |
| 8705 additional support for Mule (Multi-language extensions to Emacs), many | |
| 8706 more customizations, multiple frames on TTY-s, support for multiple info | |
| 8707 directories, an enhanced gnuclient, improvements to regexp matching, | |
| 8708 increased MIME support, and many, many synches with GNU Emacs 20. | |
| 8709 | |
| 8710 The XEmacs/Mule support has been only seriously tested in a Japanese | |
| 8711 locale, and no doubt many problems still remain. The support for | |
| 8712 ISO-Latin-1 and Japanese is fairly strong. MULE support comes at a | |
| 440 | 8713 price---about a 30% slowdown from 19.16. We're making progress on |
| 428 | 8714 improving performance and XEmacs 20.3 compiled without Mule (which is |
| 8715 the default) is definitely faster than XEmacs 19.16. | |
| 8716 | |
| 8717 XEmacs 20.3 is the first non-beta v20 release, and will be the | |
| 8718 basis for all further development. | |
| 8719 | |
| 2459 | 8720 @node Q9.0.6, , Q9.0.5, Current Events |
| 8721 @unnumberedsubsec Q9.0.6: What's new in XEmacs 20.2? | |
| 611 | 8722 |
| 8723 The biggest changes in 20.2 include integration of EFS (the next | |
| 8724 generation of ange-ftp) and AUC Tex (the Emacs subsystem that includes a | |
| 8725 major mode for editing Tex and LaTeX, and a lot of other stuff). Many | |
| 8726 bugs from 20.0 have been fixed for this release. 20.2 also contains a | |
| 8727 new system for customizing XEmacs options, invoked via @kbd{M-x | |
| 8728 customize}. | |
| 8729 | |
| 8730 XEmacs 20.2 is the development release (20.0 was beta), and is no longer | |
| 8731 considered unstable. | |
| 8732 | |
| 8733 For older news, see the file @file{ONEWS} in the @file{etc} directory of | |
| 8734 the XEmacs distribution. | |
| 428 | 8735 |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8736 @node Legacy Versions, Bleeding Edge, Current Events, Top |
| 2459 | 8737 @unnumbered 10 New information about old XEmacsen |
| 8738 | |
| 8739 This is part 10 of the XEmacs Frequently Asked Questions list. It will | |
| 1495 | 8740 occasionally be updated to reflect new information about versions which |
| 8741 are no longer being revised by the XEmacs Project. The primary purpose | |
| 8742 is advice on compatibility of older XEmacsen with new packages and | |
| 8743 updated versions of packages, but bug fixes (which will not be applied | |
| 8744 to released XEmacsen, but users can apply themselves) are also accepted. | |
| 8745 | |
| 8746 @menu | |
| 2537 | 8747 10.0: XEmacs 21.1 |
| 2459 | 8748 * Q10.0.1:: Gnus 5.10 won't display smileys in XEmacs 21.1. |
| 2559 | 8749 * Q10.0.2:: XEmacs won't start on Windows in XEmacs 21.1. |
| 1495 | 8750 @end menu |
| 8751 | |
| 2459 | 8752 @unnumberedsec 10.0: XEmacs 21.1 |
| 8753 | |
| 2559 | 8754 @node Q10.0.1, Q10.0.2, Legacy Versions, Legacy Versions |
| 2459 | 8755 @unnumberedsubsec Q10.0.1: Gnus 5.10 won't display smileys in XEmacs 21.1. |
| 1495 | 8756 |
| 8757 @email{eeide@@cs.utah.edu, Eric Eide} wrote: | |
| 8758 | |
| 8759 @quotation | |
| 8760 Previously I wrote: | |
| 8761 | |
| 8762 Eric> Summary: with Gnus 5.10.1 in XEmacs 21.1.14, I don't see | |
| 8763 Eric> any smileys :-(. | |
| 8764 | |
| 8765 After a bit of sleuthing, I discovered the essence of the problem. | |
| 8766 For me, the form: | |
| 8767 | |
| 8768 @lisp | |
| 8769 (with-temp-buffer | |
| 8770 (insert-file-contents "foo.xpm") | |
| 8771 (buffer-string)) | |
| 8772 @end lisp | |
| 8773 | |
| 8774 returns the empty string. This is because something somewhere | |
| 8775 replaces the XPM data with a glyph --- I haven't figured out where | |
| 8776 this occurs. | |
| 8777 @end quotation | |
| 8778 | |
| 8779 @email{kyle_jones@@wonderworks.com, Kyle Jones} replies: | |
| 8780 | |
| 8781 @quotation | |
| 8782 Do this: | |
| 8783 | |
| 8784 @lisp | |
| 8785 (setq format-alist nil) | |
| 8786 @end lisp | |
| 8787 | |
| 8788 The image-mode stuff is gone from format-alist in the 21.4 | |
| 8789 branch, praise be. | |
| 8790 @end quotation | |
| 8791 | |
| 2559 | 8792 @node Q10.0.2, , Q10.0.1, Legacy Versions |
| 8793 @unnumberedsubsec Q10.0.2: XEmacs won't start on Windows in XEmacs 21.1. | |
| 8794 | |
| 8795 XEmacs relies on a process called "dumping" to generate a working | |
| 8796 executable. Under MS-Windows this process effectively fixes the memory | |
| 8797 addresses of information in the executable. When XEmacs starts up it tries | |
| 8798 to reserve these memory addresses so that the dumping process can be | |
| 8799 reversed -- putting the information back at the correct addresses. | |
| 8800 Unfortunately some .DLLs (for instance the soundblaster driver) occupy | |
| 8801 memory addresses that can conflict with those needed by the dumped XEmacs | |
| 8802 executable. In this instance XEmacs will fail to start without any | |
| 8803 explanation. Note that this is extremely machine specific. | |
| 8804 | |
| 8805 21.1.10 includes a fix for this that makes more intelligent guesses | |
| 8806 about which memory addresses will be free, and this should cure the | |
| 8807 problem for most people. 21.4 implements "portable dumping", which | |
| 8808 eliminates the problem altogether. We recommend you use the 21.4 | |
| 8809 binaries, but you can use the 21.1 binaries if you are very paranoid | |
| 8810 about stability. @xref{Q1.1.2, Are binaries available?}. | |
| 8811 | |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8812 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8813 @node Bleeding Edge, , Legacy Versions, Top |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8814 @unnumbered 10 Working with XEmacs Source Code Repositories. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8815 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8816 This is part 11 of the XEmacs Frequently Asked Questions list. The |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8817 primary purpose is advice on use of the version control systems used to |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8818 keep the history of XEmacs development. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8819 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8820 @menu |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8821 11.0: The XEmacs repositories |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8822 * Q11.0.1:: Where is the most recent XEmacs development code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8823 * Q11.0.2:: Where is the most recent XEmacs stable code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8824 * Q11.0.3:: Where is the most recent XEmacs package code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8825 * Q11.0.4:: Why isn't @var{package} available? and what to do about it. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8826 * Q11.0.5:: How do I get commit access? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8827 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8828 11.1: Working with CVS |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8829 * Q11.1.1:: How do I keep cool using CVS? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8830 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8831 11.2: Working with Mercurial |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8832 * Q11.2.1:: What is Mercurial? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8833 * Q11.2.2:: Where do I get Mercurial? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8834 * Q11.2.3:: Do I really have to waste space on history? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8835 * Q11.2.4:: @code{hg diff} gives bizarre output. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8836 * Q11.2.5:: How do I recover from a bad commit? (I already pushed.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8837 * Q11.2.6:: How do I recover from a bad commit? (I haven't pushed yet.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8838 * Q11.2.7:: Testing patches with Mercurial Queues. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8839 @end menu |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8840 |
|
5741
d11efddf3617
Fix texinfo constructs that are rejected by texinfo 5.x. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
5739
diff
changeset
|
8841 @unnumberedsec 11.0: The XEmacs repositories |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8842 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8843 @node Q11.0.1, Q11.0.2, Bleeding Edge, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8844 @unnumberedsubsec Where is the most recent XEmacs development code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8845 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8846 The most recent XEmacs @emph{development} code is kept in a Mercurial |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8847 repository, hosted by the Debian project. The read-only URL, for |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8848 anybody who doesn't intend to push upstream directly, is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8849 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8850 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8851 http://hg.debian.org/hg/xemacs/xemacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8852 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8853 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8854 The read-write URL for committers is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8855 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8856 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8857 ssh://sperber-guest@@hg.debian.org//hg/xemacs/xemacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8858 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8859 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8860 Yes, Virginia, that doubled slash is correct. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8861 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8862 @xref{Q11.0.5, How do I get commit access?}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8863 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8864 @xref{Q11.2.1, What is Mercurial?}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8865 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8866 @node Q11.0.2, Q11.0.3, Q11.0.1, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8867 @unnumberedsubsec Where is the most recent XEmacs stable code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8868 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8869 The most recent XEmacs @emph{stable} code is kept in a Mercurial |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8870 repository, hosted by the Debian project. The read-only URL is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8871 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8872 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8873 http://hg.debian.org/hg/xemacs/xemacs-21.4 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8874 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8875 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8876 If you're @emph{not} Vin, you don't need commit access. If you |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8877 @emph{are} Vin, you shouldn't need to refer to this FAQ. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8878 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8879 @xref{Q11.2.1, What is Mercurial?}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8880 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8881 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8882 @node Q11.0.3, Q11.0.4, Q11.0.2, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8883 @unnumberedsubsec Where is the most recent XEmacs package code? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8884 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8885 The most recent XEmacs @emph{packages} code is kept in a CVS |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8886 repository, hosted by the Debian project. The read-only @code{CVSROOT}, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8887 for anybody who doesn't intend to push upstream directly, is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8888 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8889 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8890 CVSROOT=:pserver:anonymous@@cvs.alioth.debian.org:/cvsroot/xemacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8891 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8892 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8893 The read-write @code{CVSROOT} for committers is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8894 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8895 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8896 CVSROOT=:ext:@var{aliothuser}@@cvs.alioth.debian.org:/cvsroot/xemacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8897 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8898 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8899 where @var{aliothuser} is your account on @code{alioth.debian.org}. Then |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8900 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8901 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8902 cvs checkout packages |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8903 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8904 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8905 as usual. For more information, see |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8906 @uref{http://www.xemacs.org/Develop/cvsaccess.html, XEmacs CVS Archive} |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8907 on the website. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8908 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8909 @xref{Q11.1.1, How do I stay cool using CVS?}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8910 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8911 @xref{Q11.0.5, How do I get commit access?}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8912 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8913 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8914 @node Q11.0.4, Q11.0.5, Q11.0.3, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8915 @unnumberedsubsec Why isn't @var{package} available? and what to do about it. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8916 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8917 If a package isn't available from the Packages repository, probably |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8918 nobody has shown enough interest to add it yet. (Occasionally, there is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8919 a better package already in the XEmacs repository, of course.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8920 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8921 The first step is to ask about it, and propose addition, on |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8922 @email{xemacs-beta@@xemacs.org, the XEmacs Contributors list}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8923 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8924 Most regular XEmacs contributors already shoulder primary responsibility |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8925 for several packages, and contribute to maintenance of the rest, so you |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8926 are unlikely to get a massively enthusiastic response unless you |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8927 volunteer to become the maintainer of the version packaged for XEmacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8928 yourself. The duties are not terribly onerous if you're an active user |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8929 of the package @ref{(xemacs-devguide)XEmacs Package Maintainer}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8930 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8931 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8932 @node Q11.0.5, Q11.1.1, Q11.0.4, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8933 @unnumberedsubsec How do I get commit access? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8934 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8935 To get commit access to XEmacs code, write to |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8936 @email{xemacs-review@@xemacs.org, the XEmacs Review Board} and request |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8937 it. Once approved, for the development code, you also need to send |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8938 @email{mike@@xemacs.org, Michael Sperber} your SSH v2 RSA key (Alioth |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8939 policy; v1 and DSA keys aren't acceptable). A CC to |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8940 @email{xemacs-services@@xemacs.org, the XEmacs Services team} is a good |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8941 idea, although not absolutely necessary. You should also get an Alioth |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8942 account so that you can publish branches for review. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8943 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8944 For packages code, you must get an Alioth account. Send your account |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8945 name information to @email{xemacs-services@@xemacs.org, the XEmacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8946 Services team}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8947 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8948 The stable repository is gated; only the gatekeeper (currently Vin |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8949 Shelton) has commit access. Patches for the stable repository should be |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8950 submitted to @email{xemacs-patches@@xemacs.org, XEmacs Patches}, as usual. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8951 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8952 @uref{http://www.xemacs.org/Develop/hgaccess.html, XEmacs Mercurial Archive} |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8953 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8954 @uref{http://www.xemacs.org/Develop/cvsaccess.html, XEmacs CVS Archive} |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8955 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8956 @xref{Q11.1.1, How do I stay cool using CVS?}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8957 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8958 @xref{Q11.2.1, What is Mercurial?}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8959 |
|
5741
d11efddf3617
Fix texinfo constructs that are rejected by texinfo 5.x. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
5739
diff
changeset
|
8960 @unnumberedsec 11.1: Working with CVS |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8961 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8962 @node Q11.1.1, Q11.2.1, Q11.0.5, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8963 @unnumberedsubsec How do I keep cool using CVS? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8964 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8965 You don't. CVS is just basically and in detail @emph{un}-cool. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8966 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8967 What would be really cool is if you would help us out in moving the |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8968 packages repository to Mercurial. Volunteer on |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8969 @email{xemacs-beta@@xemacs.org, the XEmacs Contributors list}. What's |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8970 needed is to figure out how to provide a one step checkout for the whole |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8971 package hierarchy, while restricting commits to one package at a time. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8972 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8973 For help using CVS, Google or ask on @email{xemacs-beta@@xemacs.org}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8974 Please update this FAQ with one or two of the best references you find. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8975 |
|
5741
d11efddf3617
Fix texinfo constructs that are rejected by texinfo 5.x. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
5739
diff
changeset
|
8976 @unnumberedsec 11.1: Working with Mercurial |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8977 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8978 @node Q11.2.1, Q11.2.2, Q11.1.1, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8979 @unnumberedsubsec What is Mercurial? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8980 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8981 Mercurial is a @dfn{distributed version control system}, or DVCS. This |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8982 means that versioning information can be easily exchanged between |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8983 different lines of development, even if located on different hosts. In |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8984 the older @dfn{centralize version control system} model, when you |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8985 @dfn{commit} a change, it is immediately reflected in the public |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8986 repository. In a DVCS, each user has a @dfn{local repository}, and |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8987 the commit operation creates a version in that repository. To |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8988 communicate with the public repository, a separate @dfn{push} operation |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8989 must be executed. The DVCS model is more appropriate for open source |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8990 development. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8991 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8992 @itemize |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8993 @item |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8994 The VCS model mirrors the development organization, where developers |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8995 tend to work independently or in very small groups. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8996 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8997 @item |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8998 Users without commit access can conveniently manage their local changes. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
8999 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9000 @item |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9001 Developers can work, and commit changes, while disconnected from the |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9002 Internet. Then they merge and push their changes later. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9003 @end itemize |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9004 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9005 Use of a DVCS does require some changes in workflow, but the XEmacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9006 developers consider that inconvenience to be far more than balanced by |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9007 the advantages. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9008 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9009 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9010 @node Q11.2.2, Q11.2.3, Q11.2.1, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9011 @unnumberedsubsec Where do I get Mercurial? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9012 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9013 Most OS distributions (including add-on distributions like |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9014 @uref{http://www.cygwin.com/, Cygwin} and |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9015 @uref{http://www.macports.org/, MacPorts}) include Mercurial packages. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9016 Of course, you can get the source distribution, as well as pre-built |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9017 packages for most major platforms, from |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9018 @uref{http://mercurial.selenic.com/wiki/, the Mercurial developers}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9019 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9020 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9021 @node Q11.2.3, Q11.2.4, Q11.2.2, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9022 @unnumberedsubsec Do I really have to waste space on history? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9023 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9024 Yes, you do. It's really not that much, though. In one of my current |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9025 workspaces, I see |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9026 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9027 @table @code |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9028 @item XEmacs source files (and other cruft, such as editor backups) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9029 115464KB |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9030 @item Build products |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9031 49676 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9032 @item Mercurial control files and history |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9033 25644 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9034 @end table |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9035 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9036 That really does include all of the history available in the main XEmacs |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9037 development branch, and the build products are near twice the size of |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9038 all of the Mercurial-specific information. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9039 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9040 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9041 @node Q11.2.4, Q11.2.5, Q11.2.3, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9042 @unnumberedsubsec @code{hg diff} gives bizarre output. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9043 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9044 You may see an unreasonable diff (often large) that doesn't seem to |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9045 reflect your work. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9046 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9047 This is usually due to using @code{hg diff} on a @dfn{merge commit}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9048 That means the commit has multiple parents, and joins together two lines |
|
5384
3889ef128488
Fix misspelled words, and some grammar, across the entire source tree.
Jerry James <james@xemacs.org>
parents:
5028
diff
changeset
|
9049 of development that occurred concurrently. |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9050 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9051 You're diffing against the "wrong" one; try the other one. You get the |
|
5384
3889ef128488
Fix misspelled words, and some grammar, across the entire source tree.
Jerry James <james@xemacs.org>
parents:
5028
diff
changeset
|
9052 relevant revision number or ID from @code{hg log}. In more detail: |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9053 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9054 When there is a merge in Mercurial, it will often be the case that |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9055 one of the parents is the immediate predecessor of the merge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9056 commit. @code{hg log} will report something like |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9057 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9058 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9059 changeset: 4789:56049bea9231 # revision D, below |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9060 parent: 4788:5cca06f930ea # your commit |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9061 parent: 4787:6e6f7b79c1fc # diff against this |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9062 user: you (or somebody else) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9063 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9064 changeset: 4788:5cca06f930ea # revision B, below |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9065 parent: 4760:217abcf015c4 # revision A, below |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9066 user: you |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9067 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9068 changeset: 4787:6e6f7b79c1fc # revision C, below |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9069 parent: 4786:d6cfba1cc388 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9070 user: somebody else |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9071 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9072 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9073 Note that the divergence took place a long time ago (r4760). |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9074 It's natural to diff against (tip - 1), in the example above, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9075 @code{hg diff -r 4788}. But this will give unexpected output! |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9076 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9077 A picture of this history looks something like |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9078 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9079 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9080 B --- D |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9081 / / |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9082 A ... C |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9083 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9084 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9085 where A is the common ancestor, B is the commit you did, C is the |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9086 mainline at the time of the merge, and D is the merge commit. The |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9087 three dots between A and C can represent many commits, and a lot |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9088 of work. Given no conflicts in the merge, @code{hg diff -r C -r D} is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9089 the same as @code{hg diff -r A -r B}, @emph{i.e.}, it shows your work. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9090 Similarly, @code{hg diff -r B -r D} is the same as |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9091 @code{hg diff -r A -r C}. This latter diff is likely to be quite large, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9092 and it doesn't show your work. Unfortunately, that is the typical |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9093 result of diffing against the "previous" commit. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9094 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9095 @node Q11.2.5, Q11.2.6, Q11.2.4, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9096 @unnumberedsubsec How do I recover from a bad commit? (I already pushed.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9097 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9098 Once upon a time, an XEmacs developer wrote: |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9099 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9100 > GAAAAK! What's the best way to restore ChangeLog and its history? |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9101 |
|
5384
3889ef128488
Fix misspelled words, and some grammar, across the entire source tree.
Jerry James <james@xemacs.org>
parents:
5028
diff
changeset
|
9102 He had just inadvertently pushed a commit which deleted |
|
5028
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9103 @file{src/ChangeLog}! The history is still there, not to worry. (In |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9104 this case, another developer had restored src/ChangeLog already.) The |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9105 best way depends on a number of things. First, let's look at the log |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9106 and the state of the DAG (the graph of commits). Here's the log, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9107 formatted somewhat differently from the usual output for compactness. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9108 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9109 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9110 5025 anne Restore src/ChangeLog. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9111 5024 barb merge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9112 parents: 5023 5010 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9113 5023 barb Error-checking. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9114 5020 barb merge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9115 parents: 5019 5006 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9116 5019 barb Fix non-Mule build. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9117 5011 barb Some internals-manual updates. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9118 parents: 5002 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9119 5010 cary Windows fixes for Visual Studio 6. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9120 parents: 5008 5009 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9121 5009 cary Miscellaneous small fixes to Windows VS6 build. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9122 parents: 5006 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9123 5008 dana Add license information. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9124 5007 dana Relicense emodules.texi. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9125 5006 cary Instantiate compile fix for nt.c. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9126 5005 edna Cast correctly. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9127 5003 edna #'union doesn't preserve relative order |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9128 5002 barb Fix some compile bugs. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9129 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9130 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9131 (The gaps at 5003...5005, 5011...5019, and 5020...5023 are filled with |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9132 sequences of commits by the same developers.) Let's visualize this as a |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9133 graph. Time increases to the right, the leading "50" is omitted for |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9134 brevity, and the dotted links indicate that several irrelevant commits |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9135 were omitted, also for brevity. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9136 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9137 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9138 ,------ 09 -----. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9139 / \ |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9140 02 --- 03 ... 05 --- 06 --- 07 --- 08 --- 10 --- 24 --- 25 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9141 \ \ / |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9142 `-- 11 ... 19 -------`-- 20 ... 23 ---------' |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9143 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9144 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9145 The "problem commit" is 5010, which merges 5008 with 5009, and somehow |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9146 managed to "lose" @file{src/ChangeLog}. The unobvious consequence is |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9147 that, although the @emph{other} changes made in 5007 and 5008 were |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9148 successfully merged and are present in 5010, the log entry made by |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9149 Dana for 5008 "just disappeared". (The log entry for 5007 is in a |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9150 different @file{ChangeLog}, so it's safe.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9151 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9152 @subsubheading The safe and simple way for Cary |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9153 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9154 To recover state file-by-file (also for whole directories), use @code{hg |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9155 revert}. This does not change the "current" version, @emph{i.e.}, the |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9156 commit that will be the parent for your next commit. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9157 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9158 If it's not a merge commit, it's simple to restore the ChangeLog. It's |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9159 best to do it before making any other commits in your own workspace, and |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9160 before pulling in new commits from others. If there are a lot of such |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9161 commits in your workspace already, ask for help. But in this case, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9162 there was no such problem. Just |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9163 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9164 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9165 hg revert -r 5009 src/ChangeLog |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9166 # Add Dana's log entry by hand. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9167 hg commit -m "Restore src/ChangeLog." |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9168 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9169 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9170 5009 is the revision id of the most recent commit that had the correct |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9171 version of the file. You get that from the "parent" field in @code{hg |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9172 log}, or from the DAG browser (@code{hg view}, requires @code{hgk} |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9173 extension enabled). |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9174 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9175 Alternatively, Cary could revert from 5008. This would leave her with |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9176 @emph{her} log entry for 5009 missing, and that would have to be added |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9177 by hand. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9178 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9179 Note that in the actual history, Cary didn't realize that Dana's log |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9180 went missing, so Anne had to pick up the slack in 5025. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9181 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9182 @subsubheading Recovery by another developer |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9183 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9184 Another way to recover earlier state is with @code{hg checkout} (or |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9185 @code{hg update}, which is another way to spell the same command). This |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9186 changes the version that hg sees as "current", as well as reverting the |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9187 workspace. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9188 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9189 A common scenario is that another developer, such as Barb in the log |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9190 above, was already working on @file{src/ChangeLog}, saves her copy, then |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9191 tries to merge. She would then get a modify/delete conflict. It's |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9192 tempting to just resolve that in favor of keeping the file, and commit. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9193 This often works, but an alternative way uses the VCS: |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9194 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9195 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9196 hg checkout 5010 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9197 hg revert -r 5009 src/ChangeLog |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9198 # Add Dana's log entry by hand. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9199 hg commit -m "Restore src/ChangeLog." |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9200 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9201 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9202 to get the same effect as described above, then |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9203 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9204 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9205 hg merge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9206 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9207 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9208 (making her changes "float to the top" of the log) or |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9209 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9210 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9211 hg checkout 5023 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9212 hg merge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9213 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9214 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9215 (putting the Cary's branch at the top of the log). This assumes she has |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9216 no other heads in her workspace. If she does have other heads she would |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9217 have to use an explicit argument to @code{hg merge}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9218 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9219 Note that in the actual history, Barb didn't realize that Dana's log |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9220 went missing, so Anne (or somebody) had to pick up the slack in 5025. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9221 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9222 @subsubheading The hard but accurate way |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9223 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9224 Suppose Barb did @code{hg pull -u}, but notices the problem before |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9225 resolving conflicts and committing the merge. Assume Barb was fully committed |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9226 before doing @code{hg pull -u}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9227 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9228 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9229 # Restore the ChangeLog, "covering up" the broken commit. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9230 # Check out Cary's head. This nukes the merged files in the workspace, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9231 # but @emph{the history and versions in Barb's rev. 5023 are preserved |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9232 # in the repository}. The -C is necessary to overwrite files. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9233 hg checkout -C 5010 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9234 hg revert -r 5009 src/ChangeLog |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9235 # Merge Dana's branch (yes, again). |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9236 # The repeated merge outside of src/ChangeLog should resolve to a |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9237 # no-op, but the ChangeLog probably conflicts. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9238 # The -f is needed because revert leaves uncommitted changes. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9239 hg merge -f 5008 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9240 hg commit -m "Re-merge Dana's branch to recover her logs." |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9241 # Merge Barb's work. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9242 # If Barb has only two heads, which seems likely, the argument to |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9243 # merge is optional. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9244 hg merge 5023 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9245 hg commit -m merge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9246 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9247 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9248 Visualizing this with a graph, we have: |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9249 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9250 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9251 ,------ 09 -----. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9252 / \ |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9253 02 --- 03 ... 05 --- 06 --- 07 --- 08 --- 10 *** 24 --- 25 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9254 \ \ \ / / |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9255 \ \ `--------' / |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9256 \ \ / |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9257 `-- 11 ... 19 -------`-- 20 ... 23 ------------' |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9258 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9259 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9260 Note that the versions 5024 and 5025 in this graph denote |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9261 @emph{different} versions from the actual history. The starred link |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9262 means that editing work (aside from resolving conflicts) was done, on |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9263 top of the merge. However, the editing work is actually done by |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9264 Mercurial (the revert command)! |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9265 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9266 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9267 @node Q11.2.6, Q11.2.7, Q11.2.5, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9268 @unnumberedsubsec How do I recover from a bad commit? (I haven't pushed yet.) |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9269 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9270 If you hadn't yet pushed the commit you now regret, and realize it |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9271 before doing further commits, you can use @code{hg strip tip}. Then |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9272 just redo the commit, possibly with additional changes before |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9273 committing. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9274 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9275 @code{hg strip} is dangerous; for practical purposes it destroys |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9276 history, and it also reverts the files in your workspace. It's |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9277 probably possible to recover the history, but I don't know how. And any |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9278 uncommitted changes that might be lost are gone forever. However, it |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9279 is useful in cases like this. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9280 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9281 When in doubt, use the safer method @ref{Q11.2.5}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9282 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9283 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9284 @node Q11.2.7, , Q11.2.6, Bleeding Edge |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9285 @unnumberedsubsec Testing patches with Mercurial Queues. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9286 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9287 When testing a patch proposed on xemacs-beta or xemacs-patches, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9288 conflicts or new heads often appear later, when using @code{hg pull -u}. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9289 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9290 There are both theoretical and practical reasons why this happens, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9291 and it's unlikely to change. The current workflow of XEmacs is also |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9292 unlikely to change soon; testing patches is also probably going to |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9293 remain necessary. One way to avoid this issue is to use Mercurial |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9294 Queues (mq), an extension distributed with Mercurial. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9295 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9296 Enable mq by adding |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9297 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9298 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9299 [extensions] |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9300 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9301 hgext.mq = |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9302 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9303 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9304 to your @file{~/.hgrc}. (Yes, the right hand side is empty.) If you |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9305 already have an @code{[extensions]} section, don't repeat it. Add |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9306 @code{hgext.mq =} to the existing extensions section. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9307 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9308 When you want to test a patch, you need an hg workspace with no |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9309 uncommitted changes. If you already have some uncommitted changes, |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9310 you can preserve them with mq as follows: |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9311 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9312 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9313 $ hg qnew -f -m "Preserve local changes." local-changes |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9314 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9315 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9316 The @code{-m} flag specifies the commit message for the new patch. The |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9317 @code{-f} flag "forces" qnew to put all of the uncommitted local changes |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9318 into an mq patch, and commits it (you will see a commit with summary |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9319 "Preserve local changes." if you do an @code{hg log} now). |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9320 "local-changes" is the name of the patch. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9321 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9322 Now, create an mq patch for the test patch (which we assume was saved |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9323 to @file{/tmp/xemacs.patch}): |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9324 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9325 $ hg qimport -P -n test-xemacs-patch /tmp/xemacs.patch |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9326 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9327 The @code{-n} flag specifies the name of the patch. Give it a name |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9328 sufficiently explicit so you'll know what it is later. Remember, it |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9329 may take several weeks for the patch to be pushed to the public |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9330 mainline. The @code{-P} flag says "apply this patch to the workspace |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9331 now". |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9332 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9333 When you want to update the workspace, you need to remove the mq |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9334 commits, update, and restore your local changes and the test patch. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9335 You do it this way: |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9336 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9337 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9338 $ hg qpop --all |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9339 $ hg pull -u # use your usual method, hg fetch etc. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9340 $ hg qpush --all |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9341 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9342 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9343 @code{hg qpop --all} undoes all the mq commits, but leaves the patches |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9344 in @file{.hg/patches}. @code{hg qpush --all} reapplies the patches and |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9345 restores the mq commits. Of course you hope that the patch will be |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9346 committed upstream. When it is, you do this: |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9347 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9348 @example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9349 $ hg qpop --all |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9350 $ hg pull -u |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9351 $ hg qdelete test-xemacs-patch |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9352 $ hg qpush --all |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9353 @end example |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9354 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9355 and you're back in business with the official version of the patch you |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9356 tested, and all your local changes applied. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9357 |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9358 It's also possible to split your local changes into smaller mq |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9359 patches, but that's out of scope for this answer. |
|
b7232de2a937
Add information about repos and VCSes to FAQ.
Stephen J. Turnbull <stephen@xemacs.org>
parents:
4905
diff
changeset
|
9360 |
| 428 | 9361 @bye |