GNU nano - Bugs: bug #30397, The whitespace setting warns when...
You are not allowed to post comments on this tracker with your current authentication level.
bug #30397: The whitespace setting warns when two UTF-8 characters are used in a non-utf8 terminal.
Submitter: | Dan Mahoney <gushi> | ||
Submitted: | Fri 09 Jul 2010 03:20:11 AM UTC | ||
Severity: | 3 - Normal | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Tue 10 Jun 2014 08:14:18 PM UTC, comment #10: |
Benno Schulenberg <bens> |
Wed 26 Mar 2014 12:54:25 PM UTC, comment #9: Are you content with the locale-dependent whitespace-character seeting that is now in SVN? Will it do the job for you? |
Benno Schulenberg <bens> |
Wed 26 Feb 2014 07:12:12 PM UTC, comment #8: Actually -- I have a better answer than locale-specific whitespace options, which might be easier for me to implement, which is this:
|
Dan Mahoney <gushi> |
Wed 26 Feb 2014 09:14:06 AM UTC, comment #7: I don't know how hard it would be to implement -- I am not a C coder either. :)
|
Benno Schulenberg <bens> |
Tue 25 Feb 2014 07:58:44 PM UTC, comment #6: Right -- my question was as to how hard this would be to implement the way I asked. I don't have to do magic in /etc/profile (or the other various config files for the other shells my users may use) for any other piece of software currently -- admittedly, no other programs have utr-8 values in their config files.
|
Dan Mahoney <gushi> |
Tue 25 Feb 2014 04:56:46 PM UTC, comment #5: As a site admin, can't you do some magic in maybe /etc/profile and "redirect" things based on the locale of the user?
|
Benno Schulenberg <bens> |
Mon 24 Feb 2014 06:47:47 PM UTC, comment #4: My workaround has been to put the pure-ascii characters as a global, and then override them locally, but as the site admin, I'd like it if others using pure UTF-8 (i.e. anyone on a mac or anyone on ubuntu's default setup) could see the "better" characters, as they're not confusable with something you can type.
|
Dan Mahoney <gushi> |
Mon 24 Feb 2014 12:53:46 PM UTC, comment #3: Yes, well, if you use UTF-8 on a non-UTF terminal, you get misrepresentations, that is not nano's fault. If you wish whitespace representation to work across all encodings, you will have to choose plain ASCII characters -- maybe ":.".
|
Benno Schulenberg <bens> |
Sun 23 Feb 2014 09:10:26 PM UTC, comment #2: Sorry, please ignore that last comment, it was for another bug.
|
Dan Mahoney <gushi> |
Sun 23 Feb 2014 09:09:06 PM UTC, comment #1: Okay, so this is under FreeBSD, which is termcap, not terminfo based.
|
Dan Mahoney <gushi> |
Fri 09 Jul 2010 03:20:11 AM UTC, original submission:
I have a UTF-8 terminal, and have put in my global nanorc:
|
Dan Mahoney <gushi> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-06-10 | bens | Status | Need Info | Fixed | |
Open/Closed | Open | Closed | |||
2014-03-26 | bens | Status | None | Need Info | |
Assigned to | None | bens | |||
2014-02-25 | bens | Summary | Nano\'s whitespace handling throws errors when two UTF-8 characters are used in a non-utf8 terminal. | The whitespace setting warns when two UTF-8 characters are used in a non-utf8 terminal. | |
2010-07-09 | gushi | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-d3ae.
Corresponding source code
Considering this fixed.