Mercurial > emacs
view nextstep/INSTALL @ 107777:13c077500eb3
2010-04-04 John Wiegley <jwiegley@gmail.com>
* ido.el (ido-use-virtual-buffers): New variable to indicate
whether "virtual buffer" support is enabled for IDO. Essentially
it works as follows: Say you are visiting a file and the buffer
gets cleaned up by mignight.el. Later, you want to switch to that
buffer, but find it's no longer open. With virtual buffers
enabled, the buffer name stays in the buffer list (using the
ido-virtual face, and always at the end), and if you select it, it
opens the file back up again. This allows you to think less about
whether recently opened files are still open or not. Most of the
time you can quit Emacs, restart, and then switch to a file buffer
that was previously open as if it still were. NOTE: This feature
has been present in iswitchb for several years now, and I'm
porting the same logic to IDO.
(ido-virtual): Face used to indicate virtual buffers in the list.
(ido-buffer-internal): If a buffer is chosen, and no such buffer
exists, but a virtual buffer of that name does (which would be why
it was in the list), recreate the buffer by reopening the file.
(ido-make-buffer-list): If virtual buffers are being used, call
`ido-add-virtual-buffers-to-list' before the make list hook.
(ido-virtual-buffers): New variable which contains a copy of the
current contents of the `recentf-list', albeit pared down for the
sake of speed, and with proper faces applied.
(ido-add-virtual-buffers-to-list): Using the `recentf-list',
create a list of "virtual buffers" to present to the user in
addition to the currently open set. Note that this logic could
get rather slow if that list is too large. With the default
`recentf-max-saved-items' of 200, there is little speed penalty.
author | jwiegley@gmail.com |
---|---|
date | Sun, 04 Apr 2010 02:55:19 -0400 |
parents | 1d1d5d9bd884 |
children | 376148b31b5e |
line wrap: on
line source
Copyright (C) 2008, 2009, 2010 Free Software Foundation, Inc. See the end of the file for license conditions. Compilation ----------- In the top-level directory, use: ./configure --with-ns This will compile all the files, but emacs will not be able to be run except in -nw (terminal) mode. In order to run Emacs.app, you must run: make install This will assemble the app in nextstep/Emacs.app. If you pass the --disable-ns-self-contained option to configure, the lisp files will be installed under whatever 'prefix' is set to (defaults to /usr/local). The bundle will be smaller, but depend on these resources (may require 'sudo' for "make install"). Installation ------------ Move nextstep/Emacs.app to any desired install location. Xcode ----- On OS X Emacs can be built under Xcode. You need to run "configure" as described above first. There are two targets: 'temacs' and 'Emacs.app'. 'temacs' will build the undumped emacs executable, and copy it and the *.o files to the src directory. These steps are necessary so the next target works. 'Emacs.app' uses "Run Script" build phases to assemble the Emacs.app bundle. It uses the 'ns-app' target in src/Makefile together with the 'install' target in the top level Makefile. The source files under the temacs target must list "pre-crt0" first and "lastfile" last, so that dumping works. (Note, under GNUstep, you CAN'T use ProjectCenter, since PC cannot work with files outside of its project directory.) Distributions and Universal Binaries ------------------------------------ Building as outlined above will create ordinary binaries running on your architecture only. To create universal binaries, set CFLAGS to include "-arch ppc -arch i386". This file is part of GNU Emacs. GNU Emacs is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. GNU Emacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.