Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (517 - 519 of 1030)

Ticket Resolution Summary Owner Reporter
#191 fixed Return sometimes doesn't add a newline Gary Byers Andrew Shalit
Description

In Hemlock windows, there are times when pressing the return key doesn't insert a newline. Instead it moves the insertion point down a line. This may be a Hemlock dwim feature, but I'd call it a bug.

To duplicate this, open a lisp source code file and find (or create) two top-level forms separated by six blank lines. Place the cursor in the middle of those blank lines, and press return. The cursor will move down. If you place the cursor on the last or second-to-last empty line, hitting return will insert a newline.

#557 fixed Return key behavior is kerfliggered mikel Ron Garret
Description

The behavior of the return key in the listener in the latest release seems to have changed in a very annoying way. The previous behavior was:

  1. If the cursor was on the last line of the listener, and there was

a complete sexpr on that line, that sexpr would be evaluated.

  1. If the cursor was on the last line of the listener and there was

not a complete sexpr on that line, a newline would inserted.

  1. If the cursor was anywhere else in the buffer, the sexpr to the

left of the cursor would replace the last line in the buffer. (IMHO, this was not the correct behavior. The correct behavior is what Fred used to do: append the sexpr to the left of the cursor to the last line. But that's another issue.)

The new behavior, as best I can make out, is:

  1. If the cursor is at the end of the buffer (not merely on the last

line) and there is a complete sexpr to the left of the cursor then the sexpr is evaluated. This is as it should be. However...

  1. If the cursor is on a line other than the last, then the sexpr on

that line is copied to the last line AND it is evaluated. This is badly broken IMHO because there is no opportunity to edit the line. Now to re-use a previous line of input with changes you have to select, copy, click, and paste. Very annoying. Worse...

  1. If the cursor is on the last line but not at the end of the line,

then a newline is inserted. In addition, if there was a complete sexpr on the last line, it is evaluated. However, the cursor does not drop down to the new last line. It stays where it is. This is just b0rken. It's particularly annoying because there's a bug in the listener scrolling code so that if you do this at the bottom of a window, you get output that you don't see unless you manually scroll the window down.

I'm rating this "major" because it's really messing me up, especially the last item.

#560 fixed Return doesn't self-insert in listener Ron Garret
Description

There have been some changes recently to the behavior of the RETURN key in the IDE. By and large these changes have been improvements, but there is a small lingering bug: when RETURN is pressed with the cursor at the end of a listener buffer and there's a form to evaluate, the return character does not self-insert. As a result, if you PRINC something instead of PRINTing it, it ends up on the same line as the form being evaluated, which is a little weird. The problem is particularly evident when doing an apropos:

Welcome to Clozure Common Lisp Version 1.4-dev  (DarwinX8664)!
? (apropos :foo) HI::FOO
GUI::FOO
CCL::FOO
    :FOO,  Value: :FOO
? 
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.