bugGNU nano - Bugs: bug #55657, the prompt bar should use...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #55657: the prompt bar should use different characters for continuations and split characters

Submitted by:  David Lawrence Ramsey <dolorous>
Submitted on:  Wed 06 Feb 2019 05:55:50 PM UTC  
 
Severity:  2 - Minor Status:  Fixed
Assigned to:  Benno Schulenberg <bens> Open/Closed:  Closed

Fri 15 Feb 2019 04:48:14 PM UTC, comment #4: 

Fixed in git, commit ad505e7f, using "[" and "]" as the left and right half of a split double-width character.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Wed 06 Feb 2019 08:16:41 PM UTC, comment #3: 

For the record, I've experimentally hacked display_string() and update_line() to use those characters, and they do look nice.

David Lawrence Ramsey <dolorous>
Project Member
Wed 06 Feb 2019 06:45:41 PM UTC, comment #2: 

After a little experimenting, ◧> and <◨ look supremely ugly, whereas the simple [> and <] look nice.  So I propose to use "[" for the left and "]" for the right half of a two-column character (when it is split).

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Wed 06 Feb 2019 06:36:52 PM UTC, comment #1: 

As said in commit 6142ef87 that introduced the angular brackets as continuation marks, I like them better: they are lighter.  And implicit in the "work better": they indicate better what is meant: things continue on the right or left.  So I propose instead to replace the "$" continuation characters in the edit window with ">" and "<".

For split double-width characters we would then use something else.  At first I was thinking of an underscore, but it is too hard to see, especially when the cursor sits on it.  Now I am considering "#" or "%".  The latter one has a vague suggestion of something chopped in half.  Or we might use the Unicode characters U+25E7 (◧) and U+25E8 (◨).  Using Unicode ones is fine as double-width characters can only occur when using Unicode.

It is true that vim uses ">" as an indication that a double-width character is wrapped to the next line, but the ">" is colored, and  it is never followed by some other special character like in nano.  And I don't see vim using "<".

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Wed 06 Feb 2019 05:55:50 PM UTC, original submission:  

In the edit window, nano shows continuations using '$', as Pico does; and shows split characters using '<' and '>', as vi does.

However, in the prompt bar, nano shows both continuations and split characters as '<' and '>'.  The former is what Pico does, but it can be confusing when e.g. a split character is continued, since that displays '>>'.

The prompt bar should use different characters for continuations.  Possibly '$', as the edit window does, or something else, as long as both the edit window and prompt bar are consistent.

David Lawrence Ramsey <dolorous>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by bens (Posted a comment)
  • -email is unavailable- added by dolorous (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-03-25 bens Open/ClosedOpen => Closed
    2019-02-15 bens StatusIn Progress => Fixed
    2019-02-07 bens StatusNone => In Progress
        Assigned toNone => bens
    2019-02-06 bens Severity3 - Normal => 2 - Minor

    Back to the top


    Powered by Savane 3.5