Combined Document | Split Document
"Emacs is the extensible, customizable, self-documenting real-time display editor. "
For a more detailed description, see the GNU pages at http://www.gnu.org/software/emacs/emacs.html.
This port is known to run on all versions of Windows 95, Windows 98, Windows ME, Windows NT, Windows XP, and Windows 2000.
The Windows port is built using the Windows Win32 API and supports most of the features of the Unix version, there are some omissions at this time, which will be available in the future, these are:
Eli Zaretskii <eliz@gnu.org> maintains the port of GNU Emacs for MSDOS and MS Windows. You can download precompiled versions with the latest DJGPP archives:
Eli strongly recommends that you start with the emacs.README and emacs19.README files: They include detailed instructions about the files that are parts of the package, who needs what files, how and where to download the package, how to install them and get started with Emacs on MSDOS/MS-Windows platforms.
More from Eli:
It might be of interest to Windows users that this version of Emacs supports long filenames (Windows 9x only - not Windows NT, or Windows 2000) and the Windows clipboard (all versions of MS-Windows). It also supports multiple frames, but they all overlap, like when Emacs runs on a ``glass teletype'' terminal.People who would like to run Emacs on plain DOS (as opposed to Windows) will need to download and install a DPMI host at this URL:
Hisashi Miyashita <hisashi.miyashita@xemacs.org> maintains MULE, multilingual Emacs, and its descendant; Meadow. You can get distributions of MULE at ftp://ftp.m17n.org/pub/mule/Mule-UCS/. With the multilingual support now merged into NTEmacs in 20.4, it is no longer necessary to use a special version of Emacs for other languages, but MULE users may find upgrading to Meadow easier than to NTEmacs because of slight differences in the way they handle fonts. Meadow also has a couple of features that are still missing from NTEmacs, such as support for native IMEs and the special keys on Japanese keyboards.
There is a version of Emacs which has been compiled using the Free compiler, DJGPP, (a version of GCC), available at http://www.delorie.com.
The XEmacs for Windows NT/9X porting projects. See the XEmacs FAQ entry.
Occasionally I get requests for information about ports of Emacs to the Mac. Here are the ones that I know about:
The latest source distribution can be found in http://ftp.gnu.org/gnu/emacs/windows/. It is distributed as one large gzipped tar file (emacs*lisp.tar.gz).
In the same directory you should also find patch files that enable you to upgrade source distributions to the latest version. These patch files are mirrors of the ones on the FSF server at ftp://ftp.gnu.org/gnu.
You can also browse the source online; look in http://cvs.savannah.gnu.org/viewcvs/?cvsroot=emacs
For more information about the contents of the various files you should read the README file contained in the FTP directory.
Yes you can - Emacs sources can now be obtained via CVS. This will allow you to keep up to date with the latest bug fixes, and incremental updates.
In order to get source in this manner you'll need some form of CVS client - see here for details of where to find one.
Once you have a working CVS setup you can find download the source :
Emacs CVS repository can be checked out through anonymous (pserver) CVS with the following instructions. When prompted for a password for anonymous, simply press the Enter key.
The following commands should checkout the current version of the source:
c:\>cvs -d:pserver:anonymous@cvs.gnu.org:/sources/emacs login c:\>cvs -d:pserver:anonymous@cvs.gnu.org:/sources/emacs checkout emacs
Starting with Emacs 20.4, precompiled distributions are being hosted at ftp.gnu.org. Distributions for the latest version are at:
Distributions for all architectures and the source are now in the same directory; look for the architecture-specific binary distribution for your machine (e.g., Intel NT and Win9X have "bin-i386" in the distribution name).
Now that the precompiled distributions are hosted on ftp.gnu.org, they also take advantage of all of the gnu ftp mirrors. A list of gnu mirror sites can be found at http://www.gnu.org/order/ftp.html; once you are at one of those sites, look in the gnu/windows/emacs sudirectory to find the NT Emacs directory.
There are also a number of sites that just mirror the NT Emacs distributions:
Regarding ftp.cs.washington.edu: I've had numerous reports from people outside North America saying that their ftp connection aborts for no apparent reason roughly a third of the way through a transfer of a full distribution. Marc Haber <s_haber@ira.uka.de> said that he suffered from the same problem, and later found that a timeout configured into his WWW proxy would cancel the transfer when the link to the US was very busy. Going around his proxy solved the problem. Andy Moreton <ajm@atml.co.uk> describes his situation when using SOCKS:
The FAQ page mentions some people have problems downloading - I may be able to shed some light on it. Our site has a reasonably secure firewall, and so all access to the outside world requires use of SOCKS based connections via a SOCKS5 server (i.e. a circuit-level gateway).When doing an FTP transfer, two connections are up - a telnet for the control connection, and the data transfer on another. As the telnet connection is idle during the file transfer, the SOCKS server disconnects it. Some FTP servers get upset by this (especially the NT FTP server), and drop the data connection if the control connection goes down.
If you do have trouble downloading the full distribution, try downloading it in the 1.44MB chunks, or try one of the mirror sites.
To compile Emacs, you will need either Microsoft C compiler package or the Cygwin compiler.
For Windows NT the Microsoft C copmiler can be any of the SDK compilers from NT 3.1 and up, Microsoft Visual C++ for NT (versions 1.0 and up), or Microsoft Visual C++ (versions 2.0 and up). For Windows 95, this can be Microsoft Visual C++ versions 2.0 and up.
Download and place the source distribution in a directory (say, c:\emacs). Unpack the distribution, and go to the nt subdirectory of the emacs directory that gets created in the unpacking process. Read the README and INSTALL files included with the distribution for the full details of this process.
Emacs is just like any other Windows application compiled and linked using MSVC, and it can be debugged using Windows debuggers like DevStudio. By default, Emacs will compile with debugging options turned on. Once compiled, you should be able to load either temacs.exe, the undumped executable, or emacs.exe, the dumped executable, into the debugger (almost always you will want to debug emacs.exe).
Note that Emacs has conventions for naming built-in C identifiers corresponding to lisp functions and variables. You will, of course, need to use the C identifier names when examining variables and setting breakpoints. The C identifier versions of lisp identifiers have dashes converted to underscores, and they are prefixed with a capital letter denoting the type of lisp object that they refer to (functions use 'F', variables use 'V', etc.). For example, the C function implementing the lisp function expand-file-name is Fexpand_file_name, and the C variable corresponding to the lisp variable load-path is Vload_path.
There have been many changes from the older versions of Emacs, 19.x, and 20.x to the latest versions, 21.x.
These changes have been made in two main areas:
If you are using an older version of NTEmacs, and are having problems the recommended action is to upgrade to the latest version.
Then if you still have problems you should send mail to the list, describing your problem in as much detail as possible.
One of the biggest changes for the Windows version fo Emacs is the support for proportional fonts. Still to come is the support for inline images, tooltips, and toolbars, (which are present in the Unix version).
Open a command prompt (MSDOS) window. Decide on a directory in which to place Emacs. Move the distribution to that directory, and then unpack it. If you have the gzipped tar version, first use gunzip to uncompress the tar file, and then use tar with the "xvfm" flags to extract the files from the tar file:
% gunzip -c -d emacs*.tar.gz | tar xvf -
The "-d" flag forces gunzip to decompress (its behavior depends upon the case of the name of the executable, and sometimes it doesn't recognize that it is really gunzip), and the "-c" flag tells it to pipe its output to stdout. Similarly, the "-" flag to tar tells it to read the tar file from stdin. Unpacking the distribution this way leaves the distribution in compressed form so it takes up less space.
You may see messages from tar about not being able to change the modification time on directories, and from gunzip complaining about a broken pipe. These messages are harmless and you can ignore them.
If for some reason you also want to have the tar file gunzipped, then invoke gunzip without the -c option:
% gunzip -d emacs*.tar.gz
You can find precompiled versions of all of the compression and archive utilities in UnxUtils.zip file at http://unxutils.sourceforge.net/ (ftp mirrors).
After unpacking the archive there's very little left to do, you have the choice of:
See the section below on troubleshooting Emacs if, after downloading a precompiled distribution and unpacking it according to the instructions above, you have trouble running Emacs.
At its core Emacs contains a Lisp interpreter, this engine is used to implement most of the core functionality of Emacs.
To customize Emacs mostly involves writing extra functions in Lisp, or changing variables that affect the behaviour which is already present.
Emacs reads a file ".emacs" when it starts up, this is where it expects to find any customizations that you have made.
When Emacs starts up it attempts to load, and execute the contents of a file called ".emacs", or "_emacs". This file is where all the customizations are saved, and restored from when you restart Emacs. All of these settings are stored as Lisp expressions, for a general introduction to Lisp you could see : http://cons.org, more Emacs Specific information can be found in the Emacs Lisp Manuals.
Your startup file can be named either _emacs or .emacs, and should be placed in your "home" directory. If you have both files in your home directory, Emacs will load the .emacs file and ignore _emacs.
Your home directory is where the HOME configuration variable tells Emacs it is. As with the other Emacs configuration variables, HOME can be set in a number of ways:
If Emacs cannot find HOME set in any of the above locations, it will assume your HOME directory is "C:/".
The directory specified by HOME is also the directory substituted for tildes (~) in file names used in Emacs (so, by definition, you can always load your startup file in Emacs by doing C-x C-f "~/.emacs").
Troubleshooting: If you've set HOME to a directory using one of the above methods, and Emacs still doesn't load your startup file, the first thing you should do is check to see what Emacs thinks HOME is set to. You can do this by evaluating the following expression in the *scratch* buffer using C-x C-e:
(insert (getenv "HOME"))
Look carefully at what is printed and make sure the value is valid. For example, if the value has trailing whitespace, Emacs won't be able to find the directory. Also, be sure that the value isn't a relative drive letter (e.g., "d:" without a backslash); if it is, then HOME is going to be whatever the current directory on that drive is, which is likely not what you want to happen.
Ingo Koch <ingo.koch@ikoch.de> maintains a web site of sample .emacs files contributed by various users. His site is at http://www.dotemacs.de/.
There is also a small selection of sample .emacs files available at http://www.dotfiles.com
If you would like to have Emacs prompt you before closing, add the following to your startup file:
(setq confirm-kill-emacs 'yes-or-no-p)
You can use a package like gnuserv to associate files with Emacs so that opening a file outside of Emacs (e.g., by double-clicking on its icon) will create a new frame in a running Emacs displaying that file. It now works on all the Windows platforms that NTEmacs supports, and has a number of usefull features.
Be sure to place the gnuserv executables in your path (or modify your path or Emacs' exec-path to include them), and be sure that runemacs.exe is in your path if you use gnuserv to launch Emacs.
Note that you can set up file associations in Windows 95/98/NT 4.0 using Explorer by selecting the "View->Options..." menu operation, and then clicking on the "File Types" tab in the dialog that pops up. Clicking on a file type will allow you to edit it and associate the file with gnuclient.exe.
Warning: Be sure to quote the %1 in the association so that filenames with blanks in them are treated as one argument when sent to Emacs, e.g.:
C:\bin\gnuclientw.exe "%1"
[Discussion of other problems and solutions]
By default, gnuserv will load files into new frames. If you would rather have gnuserv load files into an existing frame, then evaluate the following in the chosen frame:
(setq gnuserv-frame (selected-frame))
Placing the above in your startup file, for example, will have gnuserv load files into the original Emacs frame. Note: one drawback of this approach is that if the frame associated with gnuserv is ever closed, gnuserv won't have a frame in which to place buffers.
You can use Emacs as the editor for composing mail for mailto: links, reading news for news: links, and editing HTML files in Internet Explorer. You first need to install the gnuserv utilities above, and then modify or create the following registry entries using regedit:
NewsKey: HKEY_CLASSES_ROOT\mailto\shell\open\command(Default) Value: gnudoit -q (message-mail (substring \"%1\" 7))
Edit HTMLKey: HKEY_CLASSES_ROOT\news\shell\open\command(Default) Value: gnudoit -q (gnus-fetch-group (substring \"%1\" 5))
Key: HKEY_CLASSES_ROOT\htmlfile\shell\edit\command(Default) Value: gnuclientw %1
Thanks to Jason Rumney <jasonr@gnu.org> and Sigbjorn Finne <sigbjorn@cse.ogi.edu> for these tips.
You can use Emacs to view document source from Netscape 3.1. First install the gnuserv utilities, and then edit the Preferences->Apps tab. In the "View Source" field, enter "gnuclientw.exe". Amy Abascal <vhchelp@wsos.com> describes what to do with Netscape 4.
I don't know of any way to have Netscape use Emacs for mailto: and news: links as with IE above.
Jerrad Pierce <belg4mit@mit.edu> has packaged together a PIF file and batch file for associating Emacs with file-types via gnuserv.
Files that you add to the desktop are stored in a directory somewhere under your Windows directory. On NT 4.0, this directory is %USERPROFILE%\desktop (in other words, c:\winnt\profiles(user)\desktop if you installed NT in c:\winnt).
If you're running Emacs in a windowing mode, and not in the console you may use a package called follow-mouse to make the current frame, or buffer the one with the mouse over it.
Find it here.
CapsLock and Control cannot be swapped from within Emacs, and Windows does not have a convenient mechanism like xmodmap to change virtual key bindings. Instead, new keyboard layouts or device drivers can be installed, or the registry can be modified, to swap the two keys.
WARNING: If you use a new keyboard layout to switch CapsLock and Control, beware of the option to use hotkey sequences to switch keyboard layouts. This option is in Control Panel->Keyboard under the Language (Windows 95) or Input Locales (Windows NT) tabs; the sequences themselves are "Left Alt+Control" and "Ctrl+Shift". If you enable one of these options, then you will likely at some point switch keyboard layouts while trying to use an Emacs key combination.
NT 4.0:
Windows 2000 can be treated in the same way as Windows NT, for swapping the Caps Lock.
Mark Russinovich has also written a freeware VxD that swaps CapsLock and Control under Windows 95. (I've been told that you might have to hit the real Control key once after installing the VxD to jumpstart the mapping.)
Windows 98: I've been told that the Windows 95 keyremap utility also works on Windows 98, despite the warnings on the web page.
There are several differences in the way in which Emacs behaves compared to a standard Windows application, however most of the functionality is already present within Emacs, its just a matter of enabling it.
Some behaviors typically found in other Windows apps, such as deleting typed-over highlighted selections, are not configured by default in Emacs. You can, however, enable them by loading various packages. If you would like to highlight the region between the point and the mark, see the help text for transient-mark-mode; if you would like highlighted selections to be deleted when you type over them, see the help text for delete-selection-mode; if you would like to change the semantics of keypad keys such as "home" and "end", see the help text for pc-selection-mode.
If you are used to standard Windows application keybindings, such as C-c for copy, C-v for paste, and C-x for cut, or selecting text with <shift>-movement, then you probably want to use Kim Storms <storm@cua.dk> cua.el.
(defun w32-restore-frame ()
"Restore a minimized frame"
(interactive)
(w32-send-sys-command 61728))
(defun w32-maximize-frame ()
"Maximize the current frame"
(interactive)
(w32-send-sys-command 61488))
Binu Jose Philip <binu@teil.soft.net> has written the dlgopen package to use the Windows Open File dialog box for opening files. Download dlgopen.zip, unpack, and read the top of the dlgopen.el file for directions on using the package.
The only thing that Emacs changes in your system is the registry (if you used addpm to install it). Emacs does not, for example, install any files in your system directory. If you don't mind the registry settings remaining in the registry, then you don't need to do anything to uninstall Emacs.
If you want to remove the registry settings, then you can use the regedt32 program to remove the Emacs registry keys. Depending upon what kind of permissions you have, the registry entries could have been installed in either HKEY_LOCAL_MACHINE\SOFTWARE\GNU\Emacs or HKEY_CURRENT_USER\SOFTWARE\GNU\Emacs.
Emacs could have failed to run for a number of reasons. The most common symptom is that, when Emacs is started, the cursor changes for a second but nothing happens. If this happens to you, it is quite likely that the distribution was unpacked incorrectly.
Check for the following to see if there was a problem during unpacking:
If you are in doubt about whether the utilities you used unpacked the distribution incorrectly, use the gunzip, tar, and unzip executables provided in the utilities directory. These are the ones I use to create and test the distributions. My advice would be to use these utilities from the start.
If it is still not working, send mail to the list, describing what you've done, and what you are seeing. (The more information you send the more likely it is that you'll receive a helpfull response..
I have received reports that, after upgrading the operating system (e.g., from NT 3.51 to NT 4.0), an installed Emacs will start but will not accept keyboard or mouse input. Apparantly, running addpm.exe as described in the installation section above fixes the problem.
Some anti-virus software seems to interact badly with older version of Emacs, these programs shouldn't cause any problems if you are running a version of Emacs newer than 20.3.
A number of users have reported that Dr. Solomon's WinGuard prevent shell-related commands from working properly within Emacs. Turning off "Scan all files" makes it work, though.
A similar report from Charles Curley. <ccurley@wyoming.com> It has also been reported that you only need to select "Programming Files Only" instead of "All Files" to prevent Emacs from hanging.
A third report from Peter Haas about Norton Antivirus 2000 (Emacs 20.5.1, Win98): a DOS shell cannot be started within Emacs without disabling the antivirus autoprotect feature (e.g., clicking on the icon in the system tray).
There have been reports from some people that the McAfee virus scanner, (versions unreported), claims that the latest version of NTEmacs contains a virus.
Assuming that you are downloading from the official gnu.org site, then these are false positives which you might see in the following files:
These warnings seem to be artifacts of the way in which Emacs is built - the process of compiling a program, then using a "dumping" process to ensure that things are pre-loaded in the emacs.exe executable - and can be safely ignored.
To remove these warnings, update your virus scanner to the latest version.
Have you installed an Iomega Zip drive recently? The Iomega driver and Emacs appear to have a conflict that causes this crash. At present, the only solution is to disable the driver, reboot, and then use Emacs normally. To do this, look in the Startup folder (inside the Programs folder in the taskbar), locate the Iomega-related programs, and move them to a different folder. Then reboot. Emacs will work normally. If you want to use the Zip drive, manually execute the Iomega programs you moved. Then reboot before you use Emacs again. It's not convenient, but at least ou won't crash. Thanks to Will Duquette for this information.
Emacs initializes the variable "system-name" with the name of your computer upon startup. However, Emacs uses two different methods for determining the computer name depending upon whether Winsock is loaded by default when Emacs starts up. If Winsock is automatically loaded, then Emacs uses gethostname, otherwise Emacs uses GetComputerName. Alternatively, you can override all of this by explicitly setting system-name in your startup file (also look at user-mail-address for composing mail messages).
By default, Emacs does not automatically load Winsock because doing so will cause Winsock to establish a connection to the network. If you are connected to a LAN, then nothing will happen, but if you dialup to an ISP then invoking Emacs (thereby loading Winsock) will prompt you to unexpectedly dialup to your ISP.
You can have Emacs automatically load Winsock by defining the environment variable PRELOAD_WINSOCK. You can set it to an arbitrary value; Emacs just checks to see if it is defined. Similarly, you can create a registry entry PRELOAD_WINSOCK with the other Emacs registry entries (in HKEY_LOCAL_MACHINE\SOFTWARE\GNU\Emacs or HKEY_CURRENT_USER\SOFTWARE\GNU\Emacs), which will do the same thing.
Emacs can run in two different interface modes: the Windows interface, which allows the flexible use and mixture of fonts and colors; and the console interface, which constrains Emacs to the limitations of console windows. The following two sections describe how to specify and change the size, position, font, and color attributes of Emacs in both interface modes.
With the Windows interface, you can change the size, position, font, and color attributes of Emacs using three different mechanisms: using the mouse with the user interface, by specifying them as command line arguments, or by invoking Emacs Lisp functions. You will probably find it convenient to specify command line arguments in the Properties of the shortcut to the runemacs.exe file, and to invoke the lisp functions in your startup file. For information on how to propagate attributes to new frames, see the section below on frames .
To customize the size of specific frames, including the initial frame, see the section on customizing frames below.
emacs -g 80x40
Note that the geometry command can be combined with the position command, as described below.
(set-frame-height (selected-frame) 40)
(set-frame-width (selected-frame) 80)
To customize the position of specific frames, including the initial frame, see the section on customizing frames below.
emacs -g +10+30
To combine the size with position, first specify the size and then the position. The two examples above can be combined as follows:
emacs -g 80x40+10+30
Note that you can also specify position offsets from any of the corners of the screen. See the GEOMETRY SPECIFICATIONS section of the X man page for complete details on the geometry command.
(set-frame-position (selected-frame) 10 30)
As with other windowing attributes, Emacs uses the X Windows color names for specifying colors on the command line and in elisp. One set of these names is a set of abstract color names, e.g., red, green, and blue. These names are the ones you will typically use as arguments on the command line or in elisp functions. Emacs also supports the use of numeric color names; see the COLOR NAMES section of the X man page for complete details on how to specify numeric color names and their color spaces.
To see the abstract color names that Emacs understands and the colors that they map to, use the menu command Edit->Text Properties->Display Colors, or invoke the list-colors-display function in the *scratch* buffer:
(list-colors-display)
If you would like to change the mapping of color names to RGB values, or to add new color names to Emacs, then you will want to modify the alist w32-color-map (win32-color-map in Emacs 19). To make changes, you can simply cons new mappings onto the head of the alist:
(setq win32-color-map (cons '("snow" . 16448255) win32-color-map)) ; Emacs 19
(setq w32-color-map (cons '("snow" . 16448255) w32-color-map)) ; Emacs 20
The number in the element is the logical OR of three values for the red, green, and blue components: (B << 16 | G << 8 | R). In the example above, red is 255, green is 250, and blue is 250. At some point there will be support for reading in files with color mappings to make this process a little easier.
To customize colors for specific frames, see the section on customizing frames below.
To customize colors for color syntax highlighting, see the section on font-lock .
emacs -fg yellow -bg black
This elisp changes the background color to black:
(set-background-color "black")
The following elisp changes the mode line foreground to firebrick:
(set-face-foreground 'modeline "firebrick")
The following elisp changes the cursor color to purple:
(set-cursor-color "purple")
Emacs uses two alists to determine the default appearances of frames, default-frame-alist and initial-frame-alist. The default-frame-alist variable sets the basic defaults of all frames. Since it is a common Emacs usage to have the initial frame have slightly different properties than other frames (e.g., its position), you can use the initial-frame-alist variable to override properties in default-frame-alist specially for the initial frame. You should definitely read the help text for these variables (C-h v) for more details on the differences between them and how they interact with each other.
Below is an example of using default-frame-alist and initial-frame-alist to configure the appearances of the initial frame and all other frames (you would place this code in your startup file ). With default-frame-alist, we set the top left corner of new frames to be at pixel offset +200+400, the width and height to be 80x40, the cursor to be white, the foreground to be yellow, the background to be black, and the font to be Courier 10. With initial-frame-alist, we override the top left corner of the initial frame to be at pixel offset +10+30, and inherit the remaining properties for the initial frame from default-frame-alist.
(setq default-frame-alist
'((top . 200) (left . 400)
(width . 80) (height . 40)
(cursor-color . "white")
(cursor-type . box)
(foreground-color . "yellow")
(background-color . "black")
(font . "-*-Courier-normal-r-*-*-13-*-*-*-c-*-iso8859-1")))
(setq initial-frame-alist '((top . 10) (left . 30)))
You can use the functions x-display-pixel-width and x-display-pixel-height to determine the resolution of your screen. For example:
(and window-system
(setq screen-width (x-display-pixel-width)
screen-height (x-display-pixel-height)))
Emacs can also run inside a console window. Simply invoke Emacs with the -nw command line option to do so. Although you cannot change the size, font, or color of the window from within Emacs, you can use the window's menu to do so. (If no icon has been created to invoke the Emacs batch file, then you'll have to create one to change these attributes.)
Under NT, go to the upper left hand corner and open the "-" menu of the console window. Select "Screen Size and Position...", and use the dialog to set the window to the size you want. Be sure to check the "Save Window Size and Position" checkbox so that future invocations will retain the new window size. After closing the dialog box, resize the window itself by dragging on the edges.
Under Windows 95, click on the properties icon in the icon toolbar at the top of the window. Go to the "Screen" tab and select the desired window size in the "Usage" panel. Click on "OK".
With Emacs 20.3 and previous version, Emacs uses the size of the console buffer as the frame size. If your console window has buffer larger than the window (e.g., it uses a verical scrollbar), then Emacs' frame will be larger than the console window. To work around this problem, make the console buffer the size of the console window. Or, if you have source, apply this patch to src/w32console.c.
Since version 20.4 this behaviour is now controlled via the variable "w32-use-full-screen-buffer".
So to fix this include the following lines in your .emacs file:
;; Make sure that Emacs in console mode doesn't go beyond the ;; size of the Dos box in use. ;; (Not needed in emacs 20.4+) (setq w32-use-full-screen-buffer nil)
To reposition Emacs, click on the title bar of the console window and drag it.
Under the NT interface, open the "-" menu. Select "Screen Colors...", and use the dialog to choose the colors you want to use for the window. Be sure to check the "Save Configuration" checkbox so that the colors are used in future invocations. Click on "OK". Unfortunately, the colors are not immediately used, but the changes have been made. To use the new colors, simply close the window and use the icon to start Emacs again. Emacs will then come up using the colors you chose before.
I'm not exactly sure how to change the colors on a per-console-window basis under Windows 95.
Font-lock mode is a mode that performs color syntax highlighting for other major modes in Emacs. To use font-lock, place the following in your startup file:
(cond ((fboundp 'global-font-lock-mode)
;; Turn on font-lock in all modes that support it
(global-font-lock-mode t)
;; Maximum colors
(setq font-lock-maximum-decoration t)))
The above code uses the default faces for decoration. If you would like to customize the attributes of the faces, you can use the following startup code to get started:
(cond ((fboundp 'global-font-lock-mode)
;; Customize face attributes
(setq font-lock-face-attributes
;; Symbol-for-Face Foreground Background Bold Italic Underline
'((font-lock-comment-face "DarkGreen")
(font-lock-string-face "Sienna")
(font-lock-keyword-face "RoyalBlue")
(font-lock-function-name-face "Blue")
(font-lock-variable-name-face "Black")
(font-lock-type-face "Black")
(font-lock-reference-face "Purple")
))
;; Load the font-lock package.
(require 'font-lock)
;; Maximum colors
(setq font-lock-maximum-decoration t)
;; Turn on font-lock in all modes that support it
(global-font-lock-mode t)))
Also see the help text for the function global-font-lock-mode and the variable font-lock-face-attributes.
To see a list of colors that Emacs understands by name, select the "Edit->Text Properties->Display Colors" menu command.
An alternative to useing font-lock-mode is to use lazy-lock, to do this use the following:
(setq font-lock-support-mode 'lazy-lock-mode)
You can use the htmlize.el package by Hrvoje Niksic to convert font-lock attributes in <hniksic@srce.hr> buffers to HTML markups. See the comments at the top of the file on how to use it.
If you are using a version of Emacs before 19.34.6 and an 8-bit display, then you should download this version of htmlize.el instead. However, this is likely to become out of date with respect to Hrvoje's version, so I would actually recommend upgrading to 19.34.6.
Gian Uberto Lauri <lauri@mail.eng.it> has modified html-helper-mode to enable font-locking and mode editing of code embedded in HTML documents (ASP, PHP).
The format of the mode line is determined by the variable mode-line-format, a buffer-local variable. To understand how to interpret the mode line, see the Info node "C-h i m emacs RET m mode line RET". For a description of minor modes that provide additional information on the mode line (like line and column number, current time, and mail status), see the Info node "C-h i m emacs RET m optional mode line features".
You can also directly customize the format by assigning a new format string to the mode-line-format variable in your startup file. For a description of the format codes, see the help string for the variable ("C-h v mode-line-format").
You can use either a two- or three-button mouse with Emacs. If you have trouble with either of these working with Emacs, see below.
Emacs assumes that you have a three-button mouse by default. However, if you have a two-button mouse, you can press both buttons at once to emulate the missing middle button expected by Emacs.
Three variables control mouse button emulation under Emacs: w32-num-mouse-buttons, w32-mouse-button-tolerance, and w32-swap-mouse-buttons (win32-num-mouse-buttons, win32-mouse-button-tolerance. If you use help on w32-num-mouse-buttons (i.e., with "C-h v"), it will tell you how many buttons Emacs thinks your mouse has; if w32-num-mouse-buttons is less than 3, then Emacs will emulate the middle mouse button.
Emacs emulates the middle mouse button by treating simultaneous button presses of the left and right buttons as a middle button press. Since both button presses cannot really be simultaneous, Emacs compares button presses within a specified window of time to determine whether it should emulate the middle button. This window of time is controlled using w32-mouse-button-tolerance. Help on this variable will show you the value Emacs uses by default, and you can change this value to suit your needs.
Depending upon the type of two-button mouse, you may find it useful to swap the mapping of middle and right mouse buttons. By default, the middle button is mapped to mouse-2 and the right button is mapped to mouse-3. If you set w32-swap-mouse-buttons to a non-nil value, then you can swap these two mappings.
If you have a three-button mouse, Emacs should recognize and support the third (middle) button automatically. However, some people find that they have a three button mouse, but the middle mouse button does not work for them. First check to see if w32-num-mouse-buttons is set correctly. If so, then check to see whether your mouse has been installed with the proper driver (open Control Panel->Mouse to examine the driver being used). If you have the right driver, then, on NT, check if HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Busmouse\Paramete rs\NumberOfButtons is set to 3, and change it to 3 if it is not. If nothing seems to be amiss, then at the very least you can have Emacs emulate the middle button by setting w32-num-mouse-buttons to 2.
Some people have reported that using a two-button mouse with Emacs sometimes causes problems when they go to click in other windows or the desktop (e.g., double left-clicks are interpreted as a right-click); apparently this is a known bug in Windows 95, and is not confined to using Emacs. If this is happening to you, you might want to flip through a discussion on the topic.
One workaround is to right-click on the desktop, and then left-click on the desktop, and the mouse should be back in its normal state.
To highlight the region between the point and the mark, use the function transient-mark-mode:
(transient-mark-mode t)
To highlight matching parentheses, add the following to your startup file:
(show-paren-mode 1)
Because of the way Emacs currently tries to share the clipboard with other Windows applications, you cannot cut and paste text with null characters embedded in it. David Biesack <sasdjb@unx.sas.com> describes a way to get around this, at least for cutting and pasting text just within Emacs.
You can use the function set-message-beep to change the sound that Emacs uses for its beep. Emacs allows you to specify one of the Windows system sounds for the beep. For example, to use the ok system sound, place the following in your startup file:
(set-message-beep 'ok)
Look up help for the function for a complete description of how to use the function and which sounds it recognizes.
`selection-coding-system' is most likely still at it's default of `iso-latin-1-dos'. You can change this to a more appropriate coding system using `set-selection-coding-system' (C-x RET x), or temporarily with `set-next-selection-coding-system' (C-x RET X). If you NEVER cut and paste between Emacs and other programs, you can make Emacs behave for all languages with:
(set-selection-coding-system 'emacs-mule)
To copy between Emacs and other apps, you may need to use the appropriate Windows codepage as your coding system. To do this, you need to set up the codepage first:
(codepage-setup 1251) (set-selection-coding-system 'cp1251)
Fonts in Emacs are named using the standard X Windows format for fonts.
For an explanation of what each element in a font string means and how Emacs on NT uses it, see Andrew's note.
These font names are the names that can be used as arguments on the command line or in lisp functions. To see the font name corresponding to a font chosen using the font selection dialog, execute the following elisp code in the *scratch* buffer:
(insert (prin1-to-string (w32-select-font))) ; Emacs 20
To see the complete list of fonts that Emacs has access to, execute the following elisp code in the *scratch* buffer:
(insert (prin1-to-string (x-list-fonts "*")))
The font support currently is a little rough around the edges. In particular, italic fonts give Emacs some problems; see below for more info about using italic fonts. Generally it performs as expected, but occasionally you might get unexpected results (e.g., Emacs didn't quite use the font you told it to use). Work is underway to fix these problems, but for now I suggest experimenting if you encounter problems.
Also, X Windows has the luxury of a set of font aliases (such as fixed) that are convenient names for referring to specific fonts. Work is underway to provide an equivalent alias mechanism under Windows so that naming fonts does not have to be as cumbersome as it currently is.
To customize fonts for specific frames, see the section on customizing frames below.
emacs -font "-*-Courier-normal-r-*-*-13-*-*-*-c-*-iso8859-1"
(set-default-font "-*-Courier-normal-r-*-*-13-*-*-*-c-*-*-iso8859-1")
To set the font of a particular face, use the set-face-font function.
Value Name: Emacs.Font
Value Type: REG_SZ
String: -*-Courier-normal-r-*-*-13-*-*-*-c-*-iso8859-1
Since the font strings are rather cumbersome, I would suggest cutting the font string into the kill-ring (which will place it in the clipboard, too) and pasting it (Ctrl-V) into the regedit dialog. (Note that you shouldn't place quotes around the font string in the registry.)
If you have Emacs frames with specific names, you can also specify a font for that frame. For the Value Name of the entry, use the name of the frame instead of Emacs (e.g., RMAIL.Font for your RMAIL frame).
Emacs currently requires that italic versions of fonts have the same width as the normal version of the font. However, most of the default fonts have italic and italic bold versions whose character widths are larger than the normal version (the only default font that appears to have viable italic and bold versions is Courier New). Because of this, Emacs by default disables the use of italic faces.
You can still enable the use of italic faces with Emacs by setting the variable w32-enable-italics to t in your startup file:
(setq w32-enable-italics t) ; This must be done before font settings! (Emacs 20.x) (set-face-font 'italic "-*-Courier New-normal-i-*-*-11-*-*-*-c-*-iso8859-1") (set-face-font 'bold-italic "-*-Courier New-bold-i-*-*-11-*-*-*-c-*-iso8859-1")
Although this works best with Courier New, there is still one minor glitch: the italics versions are one pixel higher than the other versions, so the line spacing is increased by a pixel when italics are enabled. FONT
Under NT, open the "-" menu. Select "Fonts...", and use the dialog to set the window font to the one you want. Be sure to check the "Save Configuration" checkbox so that your font change will be used in future invocations. Click on "OK", and the window will get resized.
Under Windows 95/98, simply use the popup font menu in the upper left-hand corner of the window. Or click on the font icon in the icon toolbar. Or click on the properties icon in the icon toolbar and go to the "Font" tab and choose the font that you want to use.
(Applies to version 20.4 and later)
If you have a Windows font for the script or language, then you should be able to display it using Emacs 20.4. Emacs 20.4 also supports the bdf fonts that were used with the older MULE for Windows version of Emacs and the more recent Meadow versions (as well as the X Windows versions of Emacs). For details on using the bdf fonts with Emacs, see below .
More about using Windows fonts:
There are a number of languages for which Windows fonts are not yet available, or are not in an appropriate format for Emacs to use, so you will not get every language to display. I also had some problem getting Japanese, Chinese, Cantonese and Korean to display all at once, but this was on Windows 95, and I suspect is a limitation of the OS, rather than a bug in Emacs, as those languages look fine when displayed one at a time (there is a note on the Microsoft language packs that only one may be installed at a time, which I suspect is because of this limitation).Because some languages can only use proportional fonts, limited support has been added for proportional fonts as the non-ASCII font in fontsets. It should be general enough to work with any font, but it is not full proportional support, so the characters may not appear exactly as you expect. You may need to try several fonts to find one that appears reasonably correct if you wish to use Emacs with languages like Thai which use composition and hence use only proportional Windows fonts.
If you are content with the size and style of font that Emacs uses at startup (Courier New 10), you could try using `fontset-standard', which will give you most languages that you have fonts for and Emacs supports. To use `fontset-standard' for all frames, place the following in your startup file:
(setq default-frame-alist
(append
'((font . "fontset-startup"))
default-frame-alist))
or, to change for the current frame only:
(set-frame-font "fontset-startup")
To have more control over which fonts are used in a fontset, you need to specify the fontset manually.
If only one character set is needed, the easiest way to do this is to use `create-fontset-from-ascii-font' whereever you define a font.
(setq default-frame-alist
(append
'((font . (create-fontset-from-ascii-font
"-*-Andale Mono-normal-r-*-*-13-*-*-*-c-*-iso8859-2")))
default-frame-alist))
If you require support for a number of languages, you should use `create-fontset-from-fontset-spec'. Note that installing more than one of the East Asian language packs is not supported by Microsoft, and does not work on Windows 95 at least. It is very difficult to get your system stable again after trying, so it is recommended that you only install the one that you will use the most, and use BDF fonts for the other languages:
(create-fontset-from-fontset-spec "-*-Courier New-normal-r-*-*-12-*-*-*-c-*-fontset-most, latin-iso8859-2:-*-Courier New-normal-r-*-*-12-*-*-*-c-*-iso8859-2, latin-iso8859-3:-*-Courier New-normal-r-*-*-12-*-*-*-c-*-iso8859-3, latin-iso8859-4:-*-Courier New-normal-r-*-*-12-*-*-*-c-*-iso8859-4, cyrillic-iso8859-5:-*-Courier New-normal-r-*-*-12-*-*-*-c-*-iso8859-5, greek-iso8859-7:-*-Courier New-normal-r-*-*-12-*-*-*-c-*-iso8859-7, latin-iso8859-9:-*-Courier New-normal-r-*-*-12-*-*-*-c-*-iso8859-9, japanese-jisx0208:-*-MS Gothic-normal-r-*-*-12-*-*-*-c-*-jisx0208-sjis, katakana-jisx0201:-*-MS Gothic-normal-r-*-*-12-*-*-*-c-*-jisx0208-sjis, latin-jisx0201:-*-MS Gothic-normal-r-*-*-12-*-*-*-c-*-jisx0208-sjis, japanese-jisx0208-1978:-*-MS Gothic-normal-r-*-*-12-*-*-*-c-*-jisx0208-sjis, korean-ksc5601:-*-Gulim-normal-r-*-*-12-*-*-*-c-*-ksc5601-*, chinese-gb2312:-*-MS Song-normal-r-*-*-12-*-*-*-c-*-gb2312-*, chinese-big5-1:-*-MingLiU-normal-r-*-*-12-*-*-*-c-*-big5-*, chinese-big5-2:-*-MingLiU-normal-r-*-*-12-*-*-*-c-*-big5-*" t)
If you leave character sets out of the fontset-spec above, a font will be chosen at random (not necessarily matching any of the other fonts in the fontset). The fontset name is used to generate the "default" font, which covers ASCII and iso8859-1.
To get a full list of character-sets use "M-x describe-fontset" to describe `fontset-standard'.
MS Windows fonts The Windows installation CDROM contains fonts for most European languages. If you did not install "Multilanguage Support" when you installed Windows, you can install it from the "Add Programs" Control Panel. East Asian Language (Chinese, Japanese, Korean) support for Microsoft Word and Internet Explorer can also be used by Emacs. These are available from http://www.microsoft.com, or on the installation CDROMs. IE5 also has fonts for Thai, Vietnamese and other languages, although it is not known how well these work with Emacs. Fonts for many other languages are available on the WWW; a good starting point is http://babel.uoregon.edu/yamada/guides.html.
X Windows fonts There is a collection of international fonts for use with X Windows, and a set can be found at ftp.gnu.org. They are distributed in the bdf font file format, a format that can be handled by Emacs starting with version 20.3.5.1. For details on how to use these fonts with Emacs, see the section below on using bdf fonts with Emacs.
Define a fontset ( see above ) listing any font of an appropriate size which works with the third party program for the appropriate character set(s). Change the character set to the character set you want displayed so Emacs knows how to display it. For example:
(create-fontset-from-fontset-spec "-*-Courier New-normal-r-*-*-13-*-*-*-c-*-fontset-asian, korean-ksc5601:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-ksc5601-*, chinese-gb2312:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-gb2312-*, chinese-big5-1:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-big5-*, chinese-big5-2:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-big5-*, japanese-jisx0208:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-jisx0208-sjis, katakana-jisx0201:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-jisx0201-sjis, latin-jisx0201:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-jisx0201-sjis, japanese-jisx0208-1978:-*-Courier New-normal-r-*-*-13-*-*-*-c-*-jisx0208-sjis")
If this doesn't work, you may need to set `w32-enable-unicode-output' to nil.
This is most applicable to East Asian users. Others can probably get their fonts working (with a strange looking name), but it is nice to have the names of fonts displayed correctly.
You need to use the function `set-w32-system-coding-system' before the font is specified. If you are setting the font from your .emacs, you will need to make sure the coding-system of your .emacs supports the character set for the font name. An example (for Traditional Chinese) follows:
;; Top line of .emacs: -*- coding: chinese-big-5; -*- (set-w32-system-coding-system 'chinese-big-5)
For Japanese, you would use japanese-shift-jis; for Simplified Chinese, chinese-iso-8bit; for Korean, korean-iso-8bit.
To use bdf fonts with Emacs, you need to tell Emacs where the fonts are located, create fontsets for them, and then use them. We'll use the 16 dot international fonts from ftp.gnu.org/intlfonts as an example put together by Jason Rumney <jasonr@gnu.org>
Download the 16dots.tar.gz file and unpack it; I'll assume that they are in "c:\intlfonts". Then set w32-bdf-filename-alist to the list of fonts returned by using w32-find-bdf-fonts to enumerate all of the font files. It is a good idea to set the variable bdf-directory-list at the same time so ps-print knows where to find the fonts:
(setq bdf-directory-list
'("c:/intlfonts/Asian" "c:/intlfonts/Chinese" "c:/intlfonts/Chinese-X"
"c:/intlfonts/Ethiopic" "c:/intlfonts/European" "c:/intlfonts/Japanese"
"c:/intlfonts/Japanese-X" "c:/intlfonts/Korean-X" "c:/intlfonts/Misc/"))
(setq w32-bdf-filename-alist
(w32-find-bdf-fonts bdf-directory-list))
Then create fontsets for the BDF fonts:
(create-fontset-from-fontset-spec "-*-fixed-medium-r-normal-*-16-*-*-*-c-*-fontset-bdf, japanese-jisx0208:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0208.1983-*, katakana-jisx0201:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0201*-*, latin-jisx0201:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0201*-*, japanese-jisx0208-1978:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0208.1978-*, thai-tis620:-misc-fixed-medium-r-normal--16-160-72-72-m-80-tis620.2529-1, lao:-misc-fixed-medium-r-normal--16-160-72-72-m-80-MuleLao-1, tibetan-1-column:-TibMdXA-fixed-medium-r-normal--16-160-72-72-m-80-MuleTibetan-1, ethiopic:-Admas-Ethiomx16f-Medium-R-Normal--16-150-100-100-M-160-Ethiopic-Unicode, tibetan:-TibMdXA-fixed-medium-r-normal--16-160-72-72-m-160-MuleTibetan-0")
Many of the international bdf fonts from gnu.org are type 0, and therefore need to be added to font-encoding-alist:
;; Need to add some fonts to font-encoding-alist since the bdf fonts
;; are type 0 not the default type 1.
(setq font-encoding-alist
(append '(("MuleTibetan-0" (tibetan . 0))
("GB2312" (chinese-gb2312 . 0))
("JISX0208" (japanese-jisx0208 . 0))
("JISX0212" (japanese-jisx0212 . 0))
("VISCII" (vietnamese-viscii-lower . 0))
("KSC5601" (korean-ksc5601 . 0))
("MuleArabic-0" (arabic-digit . 0))
("MuleArabic-1" (arabic-1-column . 0))
("MuleArabic-2" (arabic-2-column . 0))) font-encoding-alist))
You can now use the Emacs font menu (not the popup dialog; see below ) to select the "bdf: 16-dot medium" fontset, or you can select it by setting the default font:
(set-default-font "fontset-bdf")
Try loading the file etc/HELLO, and you should be able to see the various international fonts displayed (except for Hindi, which is not included in the 16-dot font distribution).
Place the following in your startup file:
(setq w32-use-w32-font-dialog nil)
If you have set w32-use-w32-font-dialog to nil, you can add fonts to the font menu by changing `w32-fixed-font-alist'. For example:
(setq w32-fixed-font-alist
(append w32-fixed-font-alist
'(("Monotype.com"
("8" "-*-Monotype.com-normal-r-*-*-11-*-*-*-c-iso8859-1")
("9" "-*-Monotype.com-normal-r-*-*-12-*-*-*-c-iso8859-1")
("10" "-*-Monotype.com-normal-r-*-*-13-*-*-*-c-iso8859-1")
("11" "-*-Monotype.com-normal-r-*-*-15-*-*-*-c-iso8859-1")))))
There are a number of methods by which you can control automatic CR/LF translation in Emacs, a situation that reflects the fact that the default support isn't very robust. For a discussion of this issue, take a look at this collection of email messages on the topic.
The first method is by file extension using the alist file-name-buffer-file-type-alist. This alist contains pairs of regular expressions and booleans that determine whether a file is opened in binary (untranslated) or text (translated) mode. The alist already contains a number of pairs that you can use as examples for creating your own; do a "C-h v" on the variable name to see the help text and the default pairs.
You could add your own pairs to the alist, or change the alist entirely. For example, if you wanted to open every file in binary mode except for batch files, you could add the following to your startup file:
(setq file-name-buffer-file-type-alist '(("\.bat$" . nil) (".*" . t)))
The first pair says anything ending with the .bat extension should be opened in text mode, and the second pair opens everything else that doesn't match the first pair in binary mode.
A second method for controlling translation is with the functions at the end of untranslate.el. These functions enable you to turn on and off translation on a filesystem basis (e.g., open anything on C: in translated mode, and anything on U: in untranslated mode). If you want to use these functions, download and place untranslate.el in your load-path and have it loaded from your startup file. Then you can place calls to add-untranslated-filesystem to selectively access filesystems in binary mode.
A third method for controlling translation is to have Emacs scan files and automatically determine whether they are binary or text by looking at the line breaks in the file (i.e., no line breaks or just linefeeds imply binary, carriage return/linefeed pairs imply text). Chris Weikart <chris@weikart.com> contributed the following code snippet from his .emacs file:
(defun set-buffer-file-eol-type (eol-type)
"Set the file end-of-line conversion type of the current buffer to
EOL-TYPE.
This means that when you save the buffer, line endings will be converted
according to EOL-TYPE.
EOL-TYPE is one of three symbols:
unix (LF)
dos (CRLF)
mac (CR)
This function marks the buffer modified so that the succeeding
\\[save-buffer]
surely saves the buffer with EOL-TYPE. From a program, if you don't want
to mark the buffer modified, use coding-system-change-eol-conversion
directly [weikart]."
(interactive "SEOL type for visited file (unix, dos, or mac): ")
(setq buffer-file-coding-system (coding-system-change-eol-conversion
buffer-file-coding-system eol-type))
(set-buffer-modified-p t)
(force-mode-line-update))
(global-set-key "\^Cu" (lambda () (interactive) (set-buffer-file-eol-type 'unix)))
(global-set-key "\^Cd" (lambda () (interactive) (set-buffer-file-eol-type 'dos)))
(global-set-key "\^Cm" (lambda () (interactive) (set-buffer-file-eol-type 'mac)))
;; Make the mode-line display the standard EOL-TYPE symbols (used above)...
(setq eol-mnemonic-undecided "(?)" ;; unknown EOL type
eol-mnemonic-unix "(unix)" ;; LF
eol-mnemonic-dos "(dos)" ;; CRLF
eol-mnemonic-mac "(mac)") ;; CR
Please read Andrew's note on how to print from Emacs in 20.4. What you need to do depends upon how you connect your printer to your machine.
Tim Sherrill <sherritp@sagian.com> has a very informative note on 2-up (n-up) printing from Emacs.
Holger Mueller <hmueller@bigfoot.de> has taken over maintaining print-NT.el [V 1.15, 6/29/98] (previously maintained by Brian Gorka <gorkab@cyberpass.net>).
Vinicius Jose Latorre <viniciusjl@ig.com.br> has some printing utilities, a relatively complete package for printing from Emacs on Windows systems (Postscript, plain-text, 2- and 4-up, 19.34.X and 20.X, UNC and local device paths, etc.).
Pascal Obry has a nice example of how to set up some variables to get printing to work on NT.
Anders Lindgren <andersl@csd.uu.se> has written a lpr.bat batch file that can be subsituted transparently for lpr on NT (Windows 95 batch files don't redirect stdin correctly).
A number of other people have put together packages to print from Emacs. I haven't had the time to go through them and piece everything together, but I recommend that you flip through this collection of messages.
For info on 2-up printing from Emacs, take a look at these messages.
For clever tricks for specific printers, take a look at these messages.
Bill Carpenter on printing in color:
It's relatively easy to set up the ps-print package, which can
generate color PostScript output. You can then run the results
through Ghostscript if you don't happen to have a color PS printer
laying around.
To try it manually, do something like this:
(require 'ps-print)
(ps-spool-buffer-with-faces)
and then look for the buffer "*PostScript*".
You can also turn your font-locked buffers into HTML, and then use a browser to print them out. See the section on htmlize.el.
Alec Clews reports success at using Ghostscript to perform his printing - using gsview version 3.4, and Ghostscript version 6.01
The configuration is straightforward, here's his settings, (which you should modify to suit).
(setq ps-lpr-command "c:\\Ghostgum\\gsview\\gsprint.exe")
;; THis line causes ghostscript to query which printer to
;; use - which you may not need if, for example, you only
;; have one printer.
(setq ps-lpr-switches '("-query"))
(setq ps-printer-name t)
The commandline options are documented in the gsprint.htm file which comes with Ghostscript.
Lennart Borgman has written a package to make an html view from any buffer in GNU Emacs, view in an web browser and print it. The package is htmlize-view.el and can be found here. Also, for more information on GNU Emacs w32 you can visit his GNU Emacs w32 wiki page.
Emacs 20.4 has the ability to print non Western languages in two ways. Both use the "Postscript Print" functions, so if you do not have a Postscript printer, you will need to configure Emacs to print through Ghostscript.
The variable `ps-multibyte-buffer' controls how non-latin characters are printed. If you are using built in support in the printer or Ghostscript, then setting this variable appropriately is all that needs to be done. To use BDF fonts, you will need to tell ps-print where to find them. This is done by setting `bdf-directory-list'. For example:
(setq ps-multibyte-buffer 'bdf-font
ps-mule-font-info-database ps-mule-font-info-database-bdf
bdf-directory-list '("c:/intlfonts/European" "c:/intlfonts/Chinese"
"c:/intlfonts/Japanese" "c:/intlfonts/Korean-X"))
By default, Emacs uses 24 dot BDF fonts for normal text, 16 dot for bold and italic and 40 dot for some (uncommon) Chinese and Japanese character sets.
If you have a printer which doesn't require a print server and is just connected directly to a hub you may find this information useful - it was contributed by Ed Grissom <egrissom@ziimaging.com>
While there may be better ways to do this, I have used the solution below to solve this problem if other Win32 apps _can_ print to the printer (Like Word or Notepad ).
Go to the printer properties and "share" the printer from your machine.
Then tell Emacs the printer is \\yourmachine\yoursharename and it should work
You may need more slashes or the opposite type of slash depending on which Emacs printing subsystem (i.e. lpr, ps-print, print-nt, w32-print, etc.) you are using. Just look at the subsystem's example for a networked printer, and substitute your machine name as the server and your share name as the printer name.
The quoting rules for Windows shells and Cygnus shells have some subtle differences. When Emacs spawns subprocesses, it tries to determine whether the process is a Cygnus program and changes its quoting mechanism appropriately. [Discussion]
Programs that explicitly use a handle to the console ("CON" or "CON:") instead of stdin and stdout cannot be used as subprocesses to Emacs, and they will also not work in shell-mode (the default ftp clients on Windows 95 and NT are examples of such programs - this ftp program is fine for use with ange-ftp, but not for M-x ftp). There is no convenient way for either Emacs or any shell used in shell-mode to redirect the input and output of such processes from the console to input and output pipes. The only workaround is to use a different implementation of the program that does not use the console directly (see the discussion on ange-ftp for a replacement for the default ftp clients).
You may notice that some programs, when run in a shell in shell-mode, have their output buffered (e.g., people have found this happening to them with sql-mode). When the program has a lot of output, it overflows the buffering and gets printed to the shell buffer; however, if the program only outputs a small amount of text, it will remain buffered and won't appear in the shell buffer.
Although it may at first seem like the shell is buffering the output from the program, it is actually the program that is buffering output. The C runtime typically decides how to buffer output based upon whether stdout is bound to a handle to a console window or not. If bound to a console window, output is buffered line by line; if bound to a block device, such as a file, output is buffered block by block.
In a shell buffer, stdout is a pipe handle and so is buffered in blocks. If you would like the buffering behavior of your program to behave differently, the program itself is going to have to be changed; you can use setbuf and setvbuf to manipulate the buffering semantics.
Some programs handle this by having an explicit flag to control their buffering behaviour, typically "-i". Other programs manage to detect that they are running under Emacs, by using getenve("emacs") internally.
A handy solution for Perl scripts is to use:
# Turn all buffering off.
select((select(STDOUT), $| = 1)[0]);
select((select(STDERR), $| = 1)[0]);
select((select(STDIN), $| = 1)[0]);
You can run DOS subprocesses under Emacs, with either the native command shell, or one of the alternatives, such as bash, tcsh, or 4NT, instead of command.com/cmd.exe; see the section below on other tools for pointers to other sites.
If you are finding that running 16-bit programs as subprocesses cause your A: drive to be accessed (hanging Emacs until a timeout occurs if no floppy is in the drive), check to see if you have McAfee Virus Shield installed. Users have found that disabling Virus Shield causes the problem to go away. Also, if you have a better fix for this problem, let me know or send mail to the list.
A followup from Bill Carpenter <bill@bubblegum.net>.
Emacs cannot guarantee that a subprocess gets killed on Windows 95/98, and is a difficult limitation to work around. For the forseeable future, you should always let subprocesses run to completion, including explicitly exiting interactive shells.
If you find that shutting down Windows 95/98 complains that there is a running cmdproxy even though you've exited all programs and it doesn't show up in the Task Manager until you shutdown, this could be a bad interaction with Norton VirusChecker.
Francis Wright has written a nice little package which tries to automatically tell shell buffer(s) to "exit" if you try to kill them, it is called msdos-shell-fix.el, and can be found at : http://centaur.maths.qmw.ac.uk/Emacs/.
When an eof is sent to a subprocess running in an interactive shell via process-send-eof, the shell terminates unexpectedly as if its input were closed. See this description for more info and an example.
You can use an interactive subshell in Emacs by typing "M-x shell". Emacs uses the SHELL configuration variable to determine which program to use as the shell. If you installed Emacs using the addpm.exe program, then addpm.exe will associate the value %COMSPEC% with SHELL in the registry. Emacs will then use the value of the COMSPEC environment variable when it starts up, unless the SHELL environment variable is explicitly defined (as when using the emacs.bat batch file).
If you would like to specify a different shell for Emacs to use, then you should do one of two things. You should either explicitly set the environment variable SHELL to be the shell you want to use, or, if you want to have the COMSPEC environment variable determine the shell, then you need to install Emacs using the addpm.exe program and ensure that the SHELL environment variable is not defined when you start up Emacs.
Any replacement shell should follow Unix convention for the -c option, or else be invoked via cmdproxy.exe if it follows the DOS convention.
Note that sh-script.el does not recognize shell names when they have the '.exe' extension on them. If you use sh-script, you should omit the '.exe' extension when specifying the SHELL variable.
Alternatively, if you do not want to mess with the SHELL or COMSPEC variables, you can explicitly place the following in your startup file:
;; For the interactive shell (setq explicit-shell-file-name "c:/bin/tcsh.exe") ;; For subprocesses invoked via the shell (e.g., "shell -c command") (setq shell-file-name "c:/bin/tcsh.exe")
You can get a version of bash with the Cygwin tools at http://www.cygwin.com/. To use bash with Emacs, place the following in your startup file:
(defun my-shell-setup () "For Cygwin bash under Emacs 20" (setq comint-scroll-show-maximum-output 'this) (setq comint-completion-addsuffix t) ;; (setq comint-process-echoes t) ;; reported that this is no longer needed (setq comint-eol-on-send t) (setq w32-quote-process-args ?\") (make-variable-buffer-local 'comint-completion-addsuffix)) (setq shell-mode-hook 'my-shell-setup)
Richard M. Heiberger's <rmh@fisher.stat.temple.edu> setup for Cygnus B19.
For more configuration information with bash, take a look at Jonathan Payne's <jpayne@marimba.com> setup.
If you find that you are having trouble with Emacs tracking drive changes with bash, see Mike Fabian's note <mike.fabian@it-mannesmann.de>
The package cygwin32-mount.el teaches Emacs about cygwin32 mount points.
WARNING:The latest version of bash sets and uses the environment variable PID. For some as yet unknown reason, if PID is set and Emacs passes it on to bash subshells, bash croaks (Emacs can inherit the PID variable if it's started from a bash shell). If you clear the PID variable in your startup file, you should be able to continue to use bash as your subshell:
(setenv "PID" nil)
For a version of ksh by David Korn, take a look at http://www.research.att.com/sw/tools/uwin. I haven't tried this shell with Emacs, but I'm guessing that it works under Emacs and that you need the following for it to work properly:
(setq w32-quote-process-args t) ; Emacs 20 (setq shell-command-switch "-c")
If you find out otherwise, let me know and I'll update this section.
WARNING: People have reported that UWIN 1.5 ksh doesn't work with Emacs. I do not know why yet. If you figure out why, please send mail to the list.
To use MKS ksh, place the following in your startup file:
(setq w32-quote-process-args t) ; Emacs 20 (setq shell-command-switch "-c")
You can find tcsh at ftp://ftp.astron.com/pub/tcsh/. To use tcsh, place the following in your startup file:
(setenv "SHELL" "tcsh.exe") (setq w32-quote-process-args t) ; Emacs 20 (setq shell-command-switch "-cf")
For more configuration information with tcsh, take a look at Chris McMahan's <cmcmahan@surefirev.com> setup.
You can find zsh at http://www.zsh.org/
To make dired, (the directory editor), use an external 'ls' program, which will allow you to see symbolic links, and such like you need to set two variables:
(setq ls-lisp-use-insert-directory-program t) ;; use external ls
(setq insert-directory-program "c:/cygwin/bin/ls") ;; ls program name
;; Change this to your absolute path --^
Some shells echo the commands that you send to them, and the echoed commands appear in the output buffer. In particular, the default shells, command.com on Windows 95 and cmd.exe on NT, have this behavior.
To prevent echoed commands from being printed, you can place the following in your startup file:
(defun my-comint-init () (setq comint-process-echoes t)) (add-hook 'comint-mode-hook 'my-comint-init)
If shell-mode still is not stripping echoed commands, then you'll have to explicitly tell the shell to not echo commands. You can do this by setting the explicit-SHELL-args variable appropriately, where SHELL is the value of your shell environment variable (do a "M-: (getenv "SHELL")" to see what it is currently set to). Assuming that you are on NT and that your SHELL environment variable is set to cmd.exe, then placing the following in your startup file will tell cmd.exe to not echo commands:
(setq explicit-cmd.exe-args '("/q"))
The comint package will use the value of this variable as an argument to cmd.exe every time it starts up a new shell (as in shell-mode); the /q is the argument to cmd.exe that stops the echoing (in a shell, invoking "cmd /?" will show you all of the command line arguments to cmd.exe).
Note that this variable is case sensitive; if the value of your SHELL environment variable is CMD.EXE instead, then this variable needs to be named explicit-CMD.EXE-args instead.
The character appended to directory names when completing in shell-mode is determined by the value of the variable comint-completion-addsuffix. If the value of this variable it t, then a '/' is appended to directory names. If the value of this variable is a cons pair, then the first value of the pair is appended.
This might happen if, for example, you invoke nmake in a shell and it tries to create subshells. The problem is related to the one above where, again, when the shell is initially created, the first argument to the shell is not the directory in which the shell program resides. When this happens, command.com fabricates a value for its COMSPEC environment variable that is incorrect. Then, when other programs go to use COMSPEC to find the shell, they are given the wrong value.
The fix for this is to either prevent any arguments from being sent to the shell when it starts up (in which case command.com will use a default, and correct, value for COMSPEC), or to have the first argument be the directory in which the shell executable resides.
Chris Boucher <chris@sorted.org> reports that Dr. Solomon's WinGuard prevents any shell related commands from working. He found that turning off "Scan all files" makes it work, though.
You do not need to do much to use mail with Emacs under Windows, but you do need to be able to communicate with local mail daemons and mail servers (they do most of the work) to both receive and send mail from your system. These daemons and servers are typically running on the machines in your local network that are already handling mail for you and/or other users on other systems.
For outgoing mail, you need to use smtpmail.el, which enables Emacs to talk SMTP with mail daemons (smtpmail.el was originally written by Tomoji Kagatani <kagatani@rbc.ncl.omron.co.jp> and is now included in the Emacs distribution). You also need to add the following to your startup file (be sure to customize for you and your system):
(setq user-full-name "Your full name") (setq user-mail-address "Your email address") (setq smtpmail-default-smtp-server "Domain name of machine with SMTP server") (setq smtpmail-local-domain nil) (setq send-mail-function 'smtpmail-send-it) (load-library "smtpmail")
Note that if you want to change the name of the smtp server after you've loaded smtpmail.el, you'll want to change the variable smtpmail-smtp-server.
If you are using GNUS to send mail, then you will also need:
(load-library "message") (setq message-send-mail-function 'smtpmail-send-it)
If you are experiencing problems with sending large messages, check the value of the variable smtpmail-debug-info. If it is non-nil, you should set it to nil:
(setq smtpmail-debug-info nil)
If you would like to queue your outgoing mail so that you can then later send it all as a batch (e.g., when you are working disconnected on a laptop), you can use the feedmail package written by Bill Carpenter <bill@bubblegum.net>.
Feedmail comes with Emacs 20.
Fabio Somenzi <Fabio@Colorado.EDU> also sent the following as an example of setting up Feemail:
(setq send-mail-function 'feedmail-send-it) (autoload 'feedmail-send-it "feedmail") (autoload 'feedmail-run-the-queue "feedmail") (setq feedmail-buffer-eating-function 'feedmail-buffer-to-smtpmail) (setq feedmail-enable-queue t) ; optional (setq feedmail-queue-chatty nil) ; optional
Fabio also redefined the function make-auto-save-file-name to auto-save files in one local directory ($HOME/.save) and to strip out invalid characters in file names . Note that all files will auto-save to this directory; this allows Emacs to auto-save even when the folder files are on an inaccessible remote machine. Place the following definition of make-auto-save-file-name in your startup file to override the definition in winnt.el.
Lastly, if you would like to protect the primary folder from crashes while it is being written back to disk, then also place the following in your startup file (assuming you use VM):
(add-hook 'vm-mode-hook
'(lambda ()
(make-local-variable 'file-precious-flag)
(setq file-precious-flag t)))
For incoming mail using the RMAIL package and a POP3 mail server, you need only place the following in your startup file (again, be sure to customize):
(setenv "MAILHOST" "Domain name of machine with POP3 server")
(setq rmail-primary-inbox-list
'("po:Your login") rmail-pop-password-required t)
Note that you will need to customize the Domain name of machine with POP3 server and Your login fields to be the name of your POP server and your login name.
For incoming mail using the VM package and a POP3 mail server, you first need the vm package (check any elisp archive) and then you need to place the following in your .vm configuration file:
(setq vm-spool-files
(list
(list "~/INBOX"
"POP3 server:110:pass:POP user name:*"
"~/INBOX.CRASH")))
Note that you will need to customize the POP3 server and POP user name fields to be your login name and the name of your POP server. You will also probably want to customize the name of your inbox and crash files (~/INBOX and ~/INBOX.CRASH in the example above.)
You should be able to use Gnus 5.2 and above as a mail reader. The following was sent as an example by Marc Fleischeuers <Marc.Fleischeuers@kub.nl>:
(load-library "message") ;; For sending mail (setq message-send-mail-function 'smtpmail-send-it) ;; For reading mail (other backends can be substituted for nnml) (setq gnus-secondary-select-methods '((nnml ""))) (setq nnmail-spool-file "po:POP user name") (setq nnmail-pop-password-required t)
Be sure to customize the POP user name field appropriately.
Setting up Gnus for reading IMAP email.
There are a number of different mail packages available within emacs. Unfortunately, only two of them (Gnus and Vm) currently support IMAP. Of those, only Gnus supports IMAP as intended (leaving the messages on the server so that they can be accessed from multiple clients). Since our decision is made for us, here's how to set up Gnus for reading IMAP mail at LLNL.
(setq load-path (cons (expand-file-name
"~/emacs/elisp/gnus-5.8.7/lisp/") load-path))
;;
;; Gnus for IMAP
;;
; setup nnimap to read the correct mailspool
(setq gnus-select-method
'(nnimap "mail-imap"
(nnimap-address "YOUR.IMAP.SERVER.HERE")))
(setq nnimap-list-pattern "INBOX")
; I don't read usenet, so don't bother setting up a server for it
; If you do read usenet, just move the stuff above to here.
(setq gnus-secondary-select-methods nil)
(setq gnus-check-new-newsgroups nil)
; configure nnfolder to save sent messages and drafts
; in this case it uses folders named ``sent.YEAR'' which
; are created and rotated automatically
(setq nnfolder-active-file (expand-file-name "~/News/archive/active"))
(setq nnnfolder-directory (expand-file-name "~/News/archive/"))
(setq gnus-message-archive-method
'(nnfolder "archive"
(nnfolder-inhibit-expiry t)))
(setq gnus-message-archive-group (concat "sent." (format-time-string "%Y")))
(setq nndraft-directory (expand-file-name "~/News/drafts"))
If you want to share your rmail folders between Unix and Windows NT/95, you'll want to handle all your mail in binary format. This includes mail stored in folders as well as incoming mail. For mail stored in folders, you'll want to treat the directory in which you store your mail as an untranslated file system; see the section on translation below on how to do this.
For incoming mail using RMAIL, you'll need to make a small patch to rmail.el. See Don Erway's <derway@ndc.com> message describing the patch and what else he did to setup sharing between Unix and Windows NT/95.
Mail packages often provide some way to notify you when email has arrived (a la "biff" in Unix), conveniently distracting you from getting any real work done. There are myriad ways to do this, and as people tell me them I will try to mention them here.
Franklin Lee <lee.franklin@worldnet.att.net> has extended the pop3 package so that you can have your mail left on the server instead of always being downloaded (it also has a biff-mode with international "barks", which can be used whether or not you download or leave your mail on the server). You'll need to download a zip archive containing a patched pop3.el and some additional elisp files:
If you unpack on Unix, be sure to use "unzip -a" to strip any carriage returns.
For instructions on how to install and configure this package so that you can leave your mail on your pop3 servers, see the instructions in epop3mail.el file.
This should potentially work with other mail packages that rely upon the pop3 elisp code. If you find that it does, or implement the glue necessary to make it work, let me know and I'll update this FAQ entry.
vm doesn't use pop3 (it has its own code) and leaving email on the server runs 'out of the box'. use:
(setq vm-pop-expunge-after-retrieving nil)
There's also a vm-pop-auto-expunge-alist variable.
19.34 Metamail is a package that allows you to receive and send MIME attachments using Emacs. For details, see the README file:
* win32 symbols are now w32. (That is all symbols, and functions that used to have a "win32" prefix now begin with "w32". * new support for coding systems should be taken advantage of and old references to binary vs. text for files and processes should be upgraded to the v20 approach. * deal with the references to mule and junet which are now wildly out of date.
I don't know of any complete ports of tm to the Windows environment, but Fabrice Popineau <popineau@esemetz.ese-metz.fr> has made some modifications to the OS2 version of tm. See his description of what he has done for more info. The support programs mentioned can be found in mm.zip (note that they have only been tested on NT 4.0, through).
Gian Uberto Lauri <lauri@eng.it> has written a win-biff tool for use with pop mail servers. [More Info]
To read news with Emacs, you can use the Gnus package. To invoke Gnus, type "M-x gnus" and Emacs will prompt you for a news server to connect to. For more information about using Gnus, take a look at:
In your HOME directory create a file called ".mailcap", place the following in it:
application/* start "" %s
After restarting Emacs, then you can open the default viewer for all attatchments by hitting return on the attatchment. Note this will RUN any .exe attatchments - which may not be, quite, what you want.
If you need to connect and post to an authenticated news server, you'll need to give Gnus a password to send along to the server. To have Gnus prompt for a password, add the following to your startup file:
(add-hook 'nntp-server-opened-hook 'nntp-send-authinfo)
For more discussion and other methods of giving Gnus a password, see a discussion on the topic.
See the "Does Gnus have MIME support?" question from the Gnus FAQ.
To save messages untranslated (no carriage returns), you must set the default-buffer-file-type to binary:
(setq default-buffer-file-type t)
Some of the package that makes it easy to read online newspapers through Emacs:
Recent versions of GNUS can also handle reading some web sites as news, Slashdot.org for example.Download the latest version from the W3 homepage, ftp://ftp.xemacs.org/pub/xemacs/emacs-w3/ and follow the directions in the README.NT file.
20.4 and later You should be able to use the browse-url package that comes with the Emacs distribution. It uses a new function to replace the external shellex helper program (see `w32-shell-execute' for details.
Peter Breton <pbreton@i-kinetics.com> wrote a small package for using browse-url to do dictionary lookups, internet word searches, etc. The package is called simple-web.
Some packages that can be used for translating text among a number of languages.
Emacs 20.3 comes with an ange-ftp.el that can use the standard Windows ftp.exe, so you should not need to download anything to use ange-ftp.
If you are behind a firewall you may have problems, because the native FTP client doesn't support passive mode, if this is the case then you'll need to download ftp.exe, and follow the instructions below.
Place the ftp.exe executable in a directory where you keep your local executables. Then be sure that the exec-path variable is set so that, when Emacs runs the ftp.exe program, it runs the one you downloaded (and not the default one). As an example, assuming that you placed ftp.exe in, say, %HOME%\bin, you could set exec-path as follows in your startup file:
(setq exec-path (cons (expand-file-name "~/bin") exec-path))
As another alternative, you can tell ange-ftp exactly which ftp program to use by customizing ange-ftp-ftp-program-name, e.g.:
(setq ange-ftp-ftp-program-name "c:/bin/ftp.exe")
With this method you don't have to worry about the wrong ftp program being picked up through exec-path.
You will also want to customize the temporary directory that ange-ftp uses to cache files:
(setq ange-ftp-tmp-name-template
(concat (expand-file-name (getenv "TEMP")) "/ange-ftp"))
(setq ange-ftp-gateway-tmp-name-template
(concat (expand-file-name (getenv "TEMP")) "/ange-ftp"))
Before you can use telnet-mode from within Emacs, you need a telnet client other than the one found on the system; the system telnet is a windows app, and cannot be used as a subprocess since it does not use stdio for input and output.
Two possible telnet clients that you can use are:
Unfortunately, this telnet program requires that the host be specified on the command line, but telnet-mode wants to specify the host using the "open" command once telnet has started. Zoltan Kemenczy <zoltan@nabu.isg.mot.com> has written a version of the telnet-mode function that does this. To use it, place "(require 'telnet)" in your startup file, followed by Zoltan's new telnet-mode code.
If the new telnet-mode still does not work for you, then you will probably find it easiest to run telnet inside of a shell buffer (instead of using telnet-mode). If you use the Borland C compiler and want to do a little hacking, it would be great if you could change this telnet to be able to start up without requiring a host on the command line. The source is included in the above zip file, and Naftali has some tips for making this change.
The jtelnet page describes how to set it up for use with Emacs. For the other telnet client, you can either place the telnet.exe program in your exec-path (e.g., anywhere in your PATH, or in the Emacs bin directory) or set the telnet-program variable in your startup file to point to the executable.
(Note: If you use anti-virus software, see the warnings above.)
You will need to get an implementation of TeX The TeX User's Group (TUG) maintains a list of TeX implementations at:
MiKTeX is a native Windows implementation of the TeX document processing system. The MiKTeX project page is at http://www.miktex.org.
The project page has instructions on where to download the distribution and how to install it.
AUCTeX is a package for writing LaTeX files in Emacs. The AUCTeX project page is at http://sunsite.auc.dk/auctex, and has links for downloading the distribution and reading the manual. Lars Schmidt-Thieme <lschmidt@ix.urz.uni-heidelberg.de> has written instructions on how to use AucTex with MikTex and Emacs.
FTTex is another port of a TeX system for windows - it is much closer to the Unix TeX, for more details please see : http://www.tug.org/interest.html#free.
Willem Minten <Willem.Minten@esat.kuleuven.ac.be> has put together a page that has everything you need to get MiKTex, AucTeX, and Emacs working together. If you're starting from scratch, look here first.
Ispell version 3 is the latest official supported version of the ispell package for Windows.
Ispeel 3.1 has support for multiple languages, and may be used in flyspell-mode.
The Cygnus port of ispell 3.1 works well with Emacs and the flyspell package. [Details]
Lennart Staflin has written a mode called PSGML for editing SGML documents. The latest beta release also supports XML. All releases may be found at:
An SGML validator is included in James Clark's DSSSL Engine, Jade.
Another good source of information for creating, managing, and processing TEI documents in SGML or XML. is:
GNU Privacy Guard is a free replacement for PGP which runs on many Unix systems, and also Windows. GPG can be found at http://www.gnupg.org.
GPG, and PGP can both be used with the version of mail-crypt find mailcrypt at ...
The Emacs 20.3 pretests and above support the Intellimouse on both NT and Win9X. Emacs 19.34.6 supports it on NT, but not on Windows 95.
Clicking the mouse wheel is interpreted as a mouse-2 event, which is normally bound to mouse-yank-at-click (i.e., paste). Since it is easy to accidentally click the mouse wheel, you might find that you inadvertantly paste text as you scroll the wheel. To prevent this from happening, you can disable the mouse-2 binding in your startup file:
(global-unset-key [mouse-2])
Walt Buehring <buehring@i2.com> has extended the implementations of mouse-wheel-scroll-line and mouse-wheel-scroll-screen. To use, download and place in your startup or site-init files.
For more details on interpreting mouse-wheel events in elisp, see Michael Duggan's <md5i@schenley.com> description of the implementation.
Apparently, FlyWheel and Emacs Intellimouse support don't work together. You can selectively disable FlyWheel for Emacs using a registry entry; see the FlyWheel README for how to disable it for a specific application.
Emacs is incompatible with the latest versions of mouse wheel devices. To get your mouse wheel to work with Emacs, you'll need to select some options in the device setup panels.
A perl-mode comes with the Emacs distribution, and will be used when you load and edit Perl files.
Users have also recommended an alternate mode named cperl-mode. You can get this from http://www.emacswiki.org/cgi-bin/wiki/CPerlMode.
From Jay Rogers <jay@rgrs.com>:
There are potentially two problems that cause the perl debugger to hang when started in emacs. One's an emacs problem while the other's a perl problem.First, get Emacs 19.34.4 or later for Windows 95/NT. It contains a fix that allows emacs to read all ASCII characters from the perl debugger, including the dreaded ^Z (aka EOF in DOS). It also groks the "drive:path" filename notation.
Second, some versions of the perl debugger itself need to be patched to work with emacs. They are perl versions 5.001 and less, and version 5.004_01. To fix, locate and change the code similar to the following code in lib/perl5db.pl
if (-e "/dev/tty") { $console = "/dev/tty"; $rcfile=".perldb"; } elsif (-e "con") { $console = ""; <---- change "con" to "" $rcfile="perldb.ini"; } else { $console = "sys\$command"; $rcfile="perldb.ini"; }
Doug Campbell <soup@ampersand.com> also has some suggestions for improving the interaction of perldb and Emacs.
The python-mode shipped with Python 1.5 requires a new custom.el before it can be used with Emacs 19.34. For more information, see the description of python-mode at http://www.python.org/emacs/python-mode/.
To use grep with Emacs, you first need to obtain a version of grep. Many of the packages listed in the section below on Unix Tools come with a version of grep (and cousins egrep and fgrep). Once you have grep, be sure that it is in your system path or in Emacs' exec-path. Then you should be able grep from within Emacs using "M-x grep".
If you can't get access to grep, then you can use the findstr program that comes with Windows NT and Windows 95 instead. It is much more limited in its searching ability, but if you have simple needs it may be adequate. Peter Breton <pbreton@i-kinetics.com> shows you how to do this.
Some users find the igrep package to be a more useful package for using grep (for example, it supports recursive greps directly). Here are some pointers from other users on what you need to do to get igrep working on your system. You can download igrep from the elisp archive at http://mirrors.sunsite.dk/gnu/elisp-archive/misc/igrep.el.gz.
To do a recursive grep, you need the help of some other utilities. Probably included in the same package that has grep will be find, a program that can recursively traverse directories and invoke programs on the files it finds. To do a recursive grep with find, invoke "M-x grep" and run the following command:
find . -name pattern -exec grep -n string NUL {} ;
The pattern argument determines which files are matched (e.g., "*.c" for all .c files). The string argument specifies the string that you are searching for. And the NUL argument is a standard way to ensure that grep reports filenames in the matches (grep reports filenames when it is invoked on more than one file, and the NUL device is simply another file that will never contain matches; on Unix, you would use /dev/null).
If you also have the xargs program, than you can make the recursive grep more efficient. Instead of the above command, use:
find . -name pattern -print | xargs grep -n string NUL
The xargs command collects lines from its input and concentates them together as one list of arguments, and invokes the specified program with the argument list (breaking the arguments up into multiple lists and invocations if necessary). The above command first uses find to print out the set of filenames that match pattern, which then gets passed to xargs. xargs concatenates the lines of filenames into lists of arguments and invokes grep on them.
To use the EDT emulation package distributed with Emacs, place the following in your startup file:
(setenv "TERM" "pc") (setq term-setup-hook 'edt-emulation-on)
You might want to also browse through the EDT emulation documentation in etc/edt-user.doc. It describes which keys are emulated, how they are mapped onto the keypad and function keys, etc.
Desktop saving refers to the ability to save and restore editing sessions (state of frames and buffers) between uses of Emacs. Kevin Greiner <kgreiner@geosys.com > has collected some elisp for using the desktop saving features of Emacs that should prove useful for others interested in the feature.
Jari Aalto <jari.aalto@poboxes.com> also has collected references to packages that http://tiny-tools.sourceforge.net/emacs-elisp.html.
Chuck Siska <chuck.siska@conexant.com> wrote his own desktop frame window layout save and restore package called desktop-frame.el.
For a close coupling of Emacs and MSVC, Christopher Payne wrote a Visual Studio add-in that makes Emacs the default text editor, this has now been taken over by Jeff Paquette <paquette@mediaone.net> See the following two URLS for details:
The section of code in .emacs for MSVC written by Charles Curley with a lot of help from: David Biesack, Caleb T. Deupree, John Huxoll Gardner, Anders Lindgren, and John Yates.
This is an app note on how to use Microsoft Visual C++ with Emacs. The experiments done below were done with Emacs 19.34.1 on Windows 95, using Visual C++ 4.0 Standard Edition. Your mileage may vary.
This writeup assumes minimal knowledge of Emacs hacking on the part of the reader.
First, Emacs requires any environmental variables to be set at boot time, in autoexec.bat (for Windows 95). This includes variables such as HOME. So if you haven't already done so, set the environment up so that Emacs' compile mode will correctly run VC++. There is a batch file in your VC++ installation's bin directory called "vcvars32.bat". Call it from your autoexec.bat file. Make sure you use the "call" keyword, or execution never returns from the called batch file. Here is what the relevant portion of my autoexec.bat looks like:
rem set up for MS C++ 4.0 call d:\msdevstd\bin\vcvars32.bat
Under NT, you can set the HOME and other environment variables in the System applet of the Control Panel.
John Huxoll Gardner writes that
These environment variables can be set through the control panel. Control Panel->System->Environment tab set include to d:\msdev\include;d:\msdev\mfc\include (or whatever) set lib to d:\msdev\lib;d:\msdev\mfc\lib (or whatever) set MSDevDir to d:\msdev
You should now be able to compile from Emacs. Load a source file from a VC++ project. Type M-X compile. Replace the proposed command line with:
nmake -f MyProject.mak
You will find that this defaults to a win 32 debug build. You can change it to a release build with:
nmake -f MyProject.mak CFG="MyProject - Win32 Release"
By the way, you can scroll in the M-X command buffer with up and down arrows. You can also scroll in the compile command buffer with the up and down arrows. Both seem to be fully editable as well.
Now set up the default value for the compile command line. Add the following to your .Emacs:
; Set up for Visual C++ compiling
(setq compile-command '("nmake -f .mak " . 10))
If you work on the same project extensively, toss that in to the default string. You can always override it when you work on another project.
By the way, many if not all Microsoft command line programs now accept a dash (-) as a switch specifier as well as a slash (/). This was true as long ago as Mess-DOS 6.0, I believe. I use it because that eliminates one area where I have to remember which OS I am using. :-)
David Biesack suggests that perhaps it's easy to define Makefile in the project directory which does
PROJECT=MyProject
all: debug
debug: FORCE
nmake /f $(PROJECT).mak CFG="$(PROJECT) - Win32 Debug"
release: FORCE
nmake /f $(PROJECT).mak CFG="$(PROJECT) - Win32 Release"
FORCE:
and then you can simply change compile-command to "nmake".
Caleb T. Deupree reports that on VC++ 5.0 and up, "You can also set an option on Options/Build to export a makefile every time the project is saved, which you can then use to compile with 'nmake -f project.mak'." VC++ 4.0 builds the make file every time, and there is no option.
Those of you who never get compile time errors can skip this section.
One of the things that compile.el provides is the ability to scan the output from a compile session, and move from error message to error message. This facility depends on a series of regular expressions ("regexes") which are applied to search the compiler output. Normally, you shouldn't have to do anything. However, if you have problems with this facility, you can comment out the regexes you don't need and recompile. Search the file for "compilation-error-regexp-alist" and comment out as needed.
To recompile, make the file the active buffer. Emacs will recognize it as an elisp file, and add a pull-down menu for elisp functions. One is for compiling, the other will compile and then load.
By the way, the best (and so far, only :-) book I've seen on regular expressions is Jeffrey E. F. Friedl, *Mastering Regular Expressions*, O'Reilly & Assoc, Inc, 1997. It covers regex syntax and usage for Emacs, perl and other tools that regexes.
Then there is the problem that sometimes you modify the source from Microsoft's IDE. Here's some help for that.
Occasionally, you need to add a new function or variable from the Visual C++ IDE. This means that the copy of the file in your Emacs buffer is now obsolete. The simplest thing to is a two part manual effort. First, before you leave Emacs for VC++, make sure you save all your buffers (C-X S). When you return, you can revert buffers you know have been changed with M-X revert-buffer. If you try to modify a file that has been changed from outside Emacs (say, by VC++), Emacs will warn you and offer you the chance to revert the buffer, so you can safely try modifying files after making a change from VC++.
However, this depends on the user remembering to do something, always a hazard. The obvious way to handle the problem is to automate it, which Anders Lindgren has already done. He writes:
This feature will be present in the next version of Emacs. There will be
two modes, `global-auto-revert-mode' that applies to all buffers while
`auto-revert-mode' can be activated for individual buffers.
Please note that this feature comes with a prize: Normally Emacs acts like
an extra backup system, keeping a copy of the files you are editing.
Should some external program mess up a file, you can always save the copy
you're editing. When using Auto-Revert mode Emacs will happily load the
corrupt file, perhaps ruining you last chance to restore the original file
content!
-- Anders
;; .signature -- File added to the end of mail, containing joke or info.
(defvar me '((profession . "Compiler Designer") (company . "IAR Systems")
(age . 27) (country . "Sweden") (hair . "Long") (water-skier . t)))
;; .signature ends here.
(Now, *that* is an elisp hacker's sig line! :-)
The next version of Emacs to which Anders refers is, I believe, 20. I don't know when it will be released.
If you can't wait, you can scarf the source for autorevert.el in from Anders' web page. However, it is dependent on another Emacs package, Custom, which is not in the version of Emacs I have (19.34.1). Custom is available at http://www.dina.kvl.dk/~abraham/custom/. Installing the Custom package is beyond my meager elisp hacking skills, so you are on your own there. The next release will also include Custom.
Caleb T. Deupree also writes, "You might also mention a package mode-compile.el, which is a wrapper around compile mode and is available from the Emacs lisp archive. It detects makefiles in directories and parses them for valid targets, performing many of the same tasks which you do in your hooks."
Also, there is a small note on - Reverting a Buffer
You can also set up VC++ to import a file into Emacs for you, all ready for editing. You will need the Gnuclient package, which is used to associate file extensions with Emacs. In VC++, go to the Tools pulldown menu, and click on Customize.... In the Tools tab, click on Add. Use Browse to locate your gnuclientw.exe file, and select it. For arguments, use +$(CurLine) "$(FilePath)" and for the directory use the $(WkspDir) (the quotes around FilePath handle paths with spaces in them). Set the Menu Text to say "Em&acs". The "+$(CurLine)" will set point in Emacs to the same line as the cursor position in VC++. The ampersand in the word "Em&acs" allows you to select emacs from the keyboard. (E is already used for the OLE control test container.)
You should now be able to go to any source file in your project. Then, use the pull-down menu Tools->Emacs. The active file in your VC++ ide should now be front and center in Emacs, all ready to edit as you wish. If you use keystrokes to work the menus, try <alt>T A to move the file into Emacs. Binding this tool to a keystroke will be left as an exercise for the student.
If you have the option of saving files before running tools, make sure this option is set. (I don't see it on VC++ 4.0.)
Jonathan Arnold's <jdarnold@buddydog.org> EmacsEdit "expert" for interfacing C++ Builder and Emacs.
Howard Melman <howard@silverstream.com> has put together some elisp to get imenu working with Java.
To create TAGS files for Java source files, use Paul's JDE below.
Paul Kinnucan <paulk@mathworks.com> has also implemented a Java Development Environment:
The JDE is an Emacs Lisp package that provides a highly configurable Emacs wrapper for command-line Java development tools, such as those provided in JavaSoft's JDK. The JDE provides menu access to a Java compiler, debugger, and API doc.
The JDE can be found at http://jdee.sunsite.dk/ (also mirrored at http://www.geocities.com/SiliconValley/Lakes/1506/).
Since NT Emacs version 20.3.1: Support for jdb has been added to gud.el package.
Jacob is a Java class browser and project manager for Emacs written by Clemens Lahme <Clemens.Lahme@gmd.de>. For details about Jacob, see http://www.kclee.de/clemens/jacob/.
David Fellows' <fellows@roo.cs.unb.ca> recipe for installing Emacs, JDE, and the Sun JDK: http://www.cs.unb.ca/courses/gen/getit-iz.html.
It provides emacs-19.34-6/jde-2.0.9/jdk-1.1{6,7}/rcs-5.7 plus some customizatins we feel are suitable for java begginners. Installation is supposed to be a "no-brainer"; most times it is.A caveat: Sun has just released jdk1.1.7 (and withdrawn 1.1.6) so the install file takehome.bat needs to be revised accordingly - the comments should make it obvious what to change. I will be updating the distribution to reflect this no later than this weekend.
There are a number of RCS x86 executables floating about. There is an "official" port of GNU RCS available.
The "official" port of GNU RCS can be found in the following places:
DOS, Win95/NT and OS/2 32-bit executables (including diff), as well as formatted documentation files:
ComponentSoftware CS-RCS is a Windows front end to GNU RCS. Single user use of their software is free, and they even have directions on how to use it with Emacs:
David Matyas <davidm@ComponentSoftware.com> By default, CS-RCS check-out files using the Windows line-break conventions (<cr><lf>), as this mode is reasonable for most of the users. A "UNIX-Style" mode is available as well. (This mode is used mainly by users uses the Windows workstation as an X-Terminal.)
The Reed Kotler toolset can be found at http://www.reedkotler.com/RKTOOLS/rktools.html.
Note: If the version of RCS you are using does not append the traditional ",v" to RCS files, try setting the environment variable "RCSINIT" to "-x,v" ("set RCSINIT=-x,v").
You can find a free port of CVS from Cyclic Software.
If you use the pcl-cvs package, you'll need to fix a couple of things in the elisp to make it work on NT; Michael M. Schmitz <ms@col.sw-ley.de> has some instructions describing what you need to do. John D. Amidon <jda@jhk.com> gives an example of what he used to set up pcl-cvs in his .emacs.
If you are having trouble getting vc-mode working with RCS or CVS, take a look at Peter Cherna's <peter.cherna@scala.com> problem description and fix.
Andy Eskilsson <andy.eskilsson@telelogic.se> has modified vc-mode to work with Clearcase, and it reportedly works very well; see http://www.fukt.hk-r.se/~flognat/vc/.
Kevin Esler <kaesler@us.ibm.com> has an Emacs/ClearCase Integration and Summary of features listed out. see http://members.verizon.net/~vze24fr2/EmacsClearCase/.
A perl-mode comes with the Emacs distribution, and will be used when you load and edit Perl files.
Users have also recommended an alternate mode named cperl-mode. This is installed with Emacs 21.3 - if you are running an older version of Emacs you can find it online at: http://www.emacswiki.org/cgi-bin/wiki/CPerlMode.
From Jay Rogers <jay@rgrs.com>:
There are potentially two problems that cause the perl debugger to hang when started in emacs. One's an emacs problem while the other's a perl problem.First, get Emacs 19.34.4 or later for Windows 95/98/NT. It contains a fix that allows emacs to read all ASCII characters from the perl debugger, including the dreaded ^Z (aka EOF in DOS). It also groks the "drive:path" filename notation.
Second, some versions of the perl debugger itself need to be patched to work with emacs. They are perl versions 5.001 and less, and version 5.004_01. To fix, locate and change the code similar to the following code in lib/perl5db.pl
if (-e "/dev/tty") { $console = "/dev/tty"; $rcfile=".perldb"; } elsif (-e "con") { $console = ""; <---- change "con" to "" $rcfile="perldb.ini"; } else { $console = "sys\$command"; $rcfile="perldb.ini"; }
Doug Campbell <soup@ampersand.com> also has some suggestions for improving the interaction of perldb and Emacs.
The python-mode shipped with Python 1.5 requires a new custom.el before it can be used with Emacs 19.34. For more information, see the description of python-mode at http://www.python.org/emacs/python-mode/.
If you have general questions about Emacs, the best places to start looking are the Emacs manual and the standard Emacs FAQ. If you already have Emacs, you can browse the manual using Info by typing "C-h i m Emacs RET", and you can view the FAQ by typing "C-h F". Or you can browse both of them online:
NTEmacs has a vibrant and helpfull mailing list, for people to report problems, and suggest improvements.
The name of the NT Emacs mailing list is help-emacs-windows@gnu.org. It's a majordomo administered list, so, if you would like to subscribe to the mailing list, send a message to help-emacs-windows-request@gnu.org with the word "subscribe" in the body of the message.
To unsubscribe from the list, send a message to help-emacs-windows-request@gnu.org with the word "unsubscribe" in the body of the message. Please do not send the unsubscribe message to the list itself, but to the request alias instead. Sending the message to the list does not unsubscribe you from it, and it tends to be annoying to people on the list.
The mailing list has a web based interface, and an archive of the list..
The home site of MULE that may be of interest to users of MULE: http://www.m17n.org/mule/Mule.en.html". and http://www.m17n.org/ is another site with Multilingual info.
I've recently discovered that there are also two MULE mailing lists, one in Japanese and another one in English. The English list is low traffic but alive. To subscribe, send
subscribe
to mule-ctl@m17n.org.
The best place to start looking is in the newsgroup gnu.emacs.sources, this can be searched online via Google
After that the Emacs Lisp List, which is maintained by Stephen Eglen <stephen@anc.ed.ac.uk> , is another good starting point, this lists several hundred lisp files, and a brief description, and thanks to ell.el can be used from within Emacs.
Many people maintain small pages of packages that they have written, or maintain - the best way to
WoMan allows Unix MAN pages to be browsed within Emacs, this lisp package requires no external programs.
This is included with the latest Emacs, if you're running an older version you can find it online at; http://centaur.maths.qmw.ac.uk/Emacs/WoMan/.
You'll need a port of diff before you can use the ediff package in Emacs. Each of the GNU-Win32, UWIN, and Reed-Kotler toolsets have a port of diff that you can use with Emacs; see the Unix tools port section below. If you just want diff and aren't in the mood for switching to a new toolset environment, then you can download the RK toolset and use the diff from there in isolation.
Patch 2.5 based upon mods by Tim Smith <tzs@halcyon.com> and a few by Andrew Innes <andrewi@harlequin.co.uk>:
Probably the first place you should look for more GNU tools is at Cygwin toolset. The toolset is a port of the GNU tools to the Windows API, as well as a set of libraries that allow Unix programs to compile to Windows with little or no modification. The project is at http://www.cygwin.com/
Michael Main <main@cs.colorado.edy> has collected together ports of various Unix programming environments and languages to Windows for classes that he teaches. See http://www.cs.colorado.edu/~main/plcd.html for an overview; e.g., a version of the mingw32 port of Unix tools is at http://www.mingw.org/.
There is also a directory of GNU software which has been ported to the Windows platform, which is available at http://www.cs.wisc.edu/twiki/bin/view/CSDocs/WindowsSoftwareCatalogInfo.
The UWIN project at AT&T Research is another project whose goal is to enable UNIX applications to build and run with little or no modification on Windows NT/95. Part of the UWIN project includes a port of ksh done by David Korn. For more information, see http://www.research.att.com/sw/tools/uwin.
A set of the GNU tools that I have seen offered on ftp sites for NT and Windows 95 have been based on the Congruent tools (I have heard mixed reviews of these ports, so use with your own discretion). An ftp site that seems to offer the full set of these tools is http://gnuwin32.sourceforge.net/.
Microsoft also has a collection of tools for use with NT, including Unix tools such as cron, ps, kill, and nice, as well as a number of NT specific tools. A list of these tools is at http://www.microsoft.com/windowsserversystem/sfu/default.mspx.
If you're a perl user, then you probably want the port of perl to Windows. You can download a perl distribution from any of the CPAN mirror sites, such as http://www.cpan.org/ports/. For a complete list of CPAN mirrors, see http://www.cpan.org/SITES.html.
David Wihl is maintaining a FAQ about porting Unix applications to NT. It can be found at http://www.informatik.uni-stuttgart.de/menschen/sommersn_public/unix2nt.html.
NTWare.com collects free software for NT (Win9X?).
|
Combined Document
| Split Document
$Author: ramprasadb $ <ramprasad@gnu.org> |
Updated: $Date: 2006/10/01 11:40:14 $ |