Custom Query (1030 matches)

Open a largish file, e.g. cocoa-editor.lisp

Right click in it and select Duplicate this window.

Go back to the first window and scroll it down to near the end, and click somewhere in the text.

Go back to the second window, and scroll by large amounts and try to click in the text. For me, most of the time, clicking places the insertion point in an apparently random location in the buffer, instead of where I clicked.

SBCL has an option when you dump an executable image to have the new image start up with the same amount of reserved heap space, stack space, etc, as the current image. Also, using this option means that the all command-line arguments are passed directly to the executable image.

Currently, the CCL kernel handles some command-line arguments unconditionally, which is a nuisance for producing completely stand-alone applications. Having this option would both enable complete control of command-line argument handling, and would let a saved application start up with a specified amount of heap space, stack space, etc, rather than the defaults.

Example:

; Currently (ccl:save-application "frob-text"

:prepend-kernel t :toplevel-function #'main)

... $ ./frob-text document.txt Couldn't load lisp heap image from document.txt

; Ideally (ccl:save-application "frob-text"

:prepend-kernel t :toplevel-function #'main :save-runtime-options t)

... $ ./frob-text document.txt <frobs document.txt>

Open the same file open in two windows, put them in different positions on the screen, then make a change in one of the windows and Save. One of the windows moves and resizes to be on top of the other, i.e. their screen positions and dimensions get unified.