bugGNU nano - Bugs: bug #45724, nano does not show block...

 
 

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

bug #45724: nano does not show block characters where other editors do

Submitted by:  Benno Schulenberg <bens>
Submitted on:  Sat 08 Aug 2015 06:40:12 PM UTC  
 
Severity:  2 - Minor Status:  None
Assigned to:  None Open/Closed:  Open

Mon 09 Dec 2019 07:03:40 PM UTC, comment #5: 

I think Craig has cleaned up dex to be even more frugally clean and correct, plus boosted the functionality and configurability..!

Peter Passchier <pepa65>
Mon 09 Dec 2019 06:57:20 PM UTC, comment #4: 

(Thanks for the link.  I didn't know that dex had been taken up by someone else.  At that time (mid 2015), I had followed dex for a while, as its code was so beautifully clean.  And it hadn't seemed abandonned yet.  I'm glad to see that Craig has added control keystrokes like ^Q, because the ^C quit <Enter> was just as infuriating as the :q! of vim.)

Benno Schulenberg <bens>
Project Administrator
Mon 09 Dec 2019 04:26:15 PM UTC, comment #3: 

Sad...
The other option is to trick curses by asking it to display a (different) placeholder, but that is a hack...

Interesting by the way that you're using dex as a reference. It is completely unmaintained for years, but dte (https://gitlab.com/craigbarnes/dte/) is an excellent fork/rewrite with fully uptodate unicode support.

Peter Passchier <pepa65>
Mon 27 Jun 2016 07:37:13 PM UTC, comment #2: 

Ncurses is unwilling to bend to nano.  See: https://lists.gnu.org/archive/html/bug-ncurses/2016-01/msg00006.html.

Benno Schulenberg <bens>
Project Administrator
Sun 09 Aug 2015 09:07:52 AM UTC, comment #1: 

A small reason not to show these placeholder "block characters" is that the relevant code points have not been assigned.  But still, it's much better to show something than deceptive blank space.

Benno Schulenberg <bens>
Project Administrator
Sat 08 Aug 2015 06:40:12 PM UTC, original submission:  

Open the attached file in nano, and see how the first line (after the A:) appears to be empty.  But when you open it in vim or emacs or dex or joe, there are four "block characters" there, showing the codes 0A1000, 0B2000, 0C3000 and 0D4000.

I think nano should show these blocks too, just like on the D: line.  There is no reason why the codes on the A: line should be treated different; they are valid code points.

(The B: and C: line contain some invalid Unicode code points, to compare how different editors handle these.  The representation by vim is the nicest.  Line E: contains two accented characters, plus two with a combining accent.  No problems there.)

Benno Schulenberg <bens>
Project Administrator

 

Attached Files
file #34608:  stuff added by bens (114B - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pepa65 (Posted a comment)
  • -email is unavailable- added by bens (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 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-02-24 bens Assigned tobens => None
    2015-08-09 bens Severity3 - Normal => 2 - Minor
    2015-08-08 bens Attached File- => Added stuff, #34608

    Back to the top


    Powered by Savane 3.5