Custom Query (1030 matches)

Backup files in Cocoa have names of the form "foo~.lisp". Whatever advantage this may have over the Emacs convention (backup files have the same extension as the original) seems to be outweighed by the disadvantage (backup files have the same extension as the original), so things like "grep FOO *.lisp" require extra effort and things like filename completion get unnecessarily confused.

I don't know how to influence the naming convention, but we can probably bypass the automatic mechanism and figure out how to rename the original file (when applicable) just before saving. (There may be issues with preserving Finder aliases and such unless this is done carefully, but I assume that it's doable.)

(In short, I vote for "foo.lisp~" ...)

A break loop message references :-commands. Those commands are in effect in the IDE, but menu-based equivalents are often available.

> Break: interrupt signal
> While executing: FD-INPUT-AVAILABLE-P, in process Listener(4).
> Type :GO to continue, :POP to abort, :R for a list of available restarts.
> If continued: Return from BREAK.
> Type :? for other options.

Certainly the 3rd line could be changed to something like:

> Type cmd-/ to continue, cmd-. to abort, cmd-\ for a list of available restarts.

possibly using the Apple clover-key character instead of "cmd".

Some versions of Emacs create lock files - broken symbolic links named something like ".#real-file". grep (and many other things) choke on them. The --no-messages argument can be used to ... suppress warnings about inaccessible files, but grep's exit status will be 2 if it encounters any file-access problems.

We probably want to move away from grep, so it's not clear if it's worth putting much effort into fixing this. It "works" (for some value of "works") to pass --no-messages and to treat an exit code of 2 as a non-error.