Activity log for bug #218637

Date Who What changed Old value New value Message
2008-04-17 12:45:46 Jarno Suni bug added bug
2008-05-31 23:40:06 Michael Nagel None: status New Invalid
2008-09-16 08:25:49 Jarno Suni description E.g. grep does not work here (always): $ cat /etc/X11/xorg.conf | grep device bash:  grep: command not found $ grep Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help' for more information. Same thing with less command: $ lspci | less bash:  less: command not found $ less Missing filename ("less --help" for help) The following happen to me, if I still have Alt Gr key down when pressing space key (which happens easily): E.g. grep does not work here (always): $ cat /etc/X11/xorg.conf | grep device bash:  grep: command not found $ grep Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help' for more information. Same thing with less command: $ lspci | less bash:  less: command not found $ less Missing filename ("less --help" for help) I expect exactly same looking command lines work same way.
2008-09-16 08:25:49 Jarno Suni title [Hardy] Piping commands does not work always [Hardy] Whitespace in command line not always regural whitespace
2008-09-16 08:54:30 Jarno Suni None: status Invalid New
2008-09-16 08:54:30 Jarno Suni None: bugtargetdisplayname Ubuntu xorg (Ubuntu)
2008-09-16 08:54:30 Jarno Suni None: bugtargetname ubuntu xorg (Ubuntu)
2008-09-16 08:54:30 Jarno Suni None: statusexplanation under system -> preferences -> keyboard -> layouts -> layout options you can choose what shift+space should do. marking this as invalid.
2008-09-16 08:54:30 Jarno Suni None: title Bug #218637 in Ubuntu: "[Hardy] Whitespace in command line not always regural whitespace" Bug #218637 in xorg (Ubuntu): "[Hardy] Whitespace in command line not always regural whitespace"
2008-10-11 02:07:48 Bryce Harrington xorg: status New Incomplete
2008-10-11 12:08:52 Michael Nagel xorg: status Incomplete New
2008-10-11 12:08:52 Michael Nagel xorg: statusexplanation i think the above was a bulk reply and does not apply here, because those settings do not matter here at all. it is more a design question in x (or perhaps rather in your virtual terminal application or your shell or whereever) if it is good to have chars that look exactly the same but behave completely different. like 1 and I and l or O and 0, but just for whitespace (tab vs nl vs space vs nbsp ...)
2008-10-17 07:09:37 Bryce Harrington xorg: status New Incomplete
2008-10-17 07:57:49 Jarno Suni bug added attachment 'xorg.conf' (xorg.conf)
2008-10-17 07:58:15 Jarno Suni bug added attachment 'lspcivvv' (lspcivvv)
2008-10-17 08:04:45 Jarno Suni bug added attachment 'Xorg.0.log' (Xorg.0.log)
2008-11-02 14:57:46 Michael Nagel xorg: status Incomplete New
2008-11-02 14:57:46 Michael Nagel xorg: statusexplanation i think the above was a bulk reply and does not apply here, because those settings do not matter here at all. it is more a design question in x (or perhaps rather in your virtual terminal application or your shell or whereever) if it is good to have chars that look exactly the same but behave completely different. like 1 and I and l or O and 0, but just for whitespace (tab vs nl vs space vs nbsp ...)
2008-12-05 04:13:53 Bryce Harrington xorg: status New Confirmed
2009-01-01 23:32:00 Timo Aaltonen xorg: status Confirmed Invalid
2009-01-01 23:32:00 Timo Aaltonen xorg: statusexplanation The change was made to conform standards. The Finns of you can read the details here: http://kotoistus.tksoft.com/linux/space.html if the app doesn't show the difference, then it's a bug in the app, not X.
2015-02-02 15:43:56 Jarno Suni description The following happen to me, if I still have Alt Gr key down when pressing space key (which happens easily): E.g. grep does not work here (always): $ cat /etc/X11/xorg.conf | grep device bash:  grep: command not found $ grep Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help' for more information. Same thing with less command: $ lspci | less bash:  less: command not found $ less Missing filename ("less --help" for help) I expect exactly same looking command lines work same way. OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones  grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" to make <Alt Gr><space> type regular space character, and use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by <Ctrl><Shift>u 00a0<Enter>, if needed, but it looks exactly like a regular space. For me, <Super><Space> would be a good shortcut for non-breaking space.
2015-02-02 15:47:47 Jarno Suni summary [Hardy] Whitespace in command line not always regural whitespace Non-breaking space is easy to write accidentally and hard to distinguish from regular space.
2015-02-02 16:08:21 Jarno Suni summary Non-breaking space is easy to write accidentally and hard to distinguish from regular space. Non-breaking space is easy to write accidentally and impossibel to distinguish from regular space.
2015-02-02 16:08:36 Jarno Suni summary Non-breaking space is easy to write accidentally and impossibel to distinguish from regular space. Non-breaking space is easy to write accidentally and impossible to distinguish from regular space.
2015-02-02 16:26:46 Jarno Suni bug task added xfce4-terminal
2015-02-02 16:28:01 Jarno Suni bug task added gnome-terminal
2015-02-02 16:28:42 Jarno Suni bug task added geany
2015-02-02 16:29:29 Jarno Suni bug task added gedit
2015-02-02 23:57:20 Jarno Suni bug task added nano
2016-12-29 10:36:12 Michael Nagel removed subscriber Michael Nagel
2019-08-19 20:07:18 Jarno Suni description OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones  grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" to make <Alt Gr><space> type regular space character, and use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by <Ctrl><Shift>u 00a0<Enter>, if needed, but it looks exactly like a regular space. For me, <Super><Space> would be a good shortcut for non-breaking space. OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones  grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" to make <Alt Gr><space> type regular space character. To make this default setting, you could add XKBOPTIONS="nbsp:none" in '/etc/default/keyboard'. Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by <Ctrl><Shift>u 00a0<Enter>, if needed, but it looks exactly like a regular space. For me, <Super><Space> would be a good shortcut for non-breaking space.
2019-08-20 09:15:44 Jarno Suni summary Non-breaking space is easy to write accidentally and impossible to distinguish from regular space. Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.
2019-08-20 09:26:39 Jarno Suni description OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones  grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" to make <Alt Gr><space> type regular space character. To make this default setting, you could add XKBOPTIONS="nbsp:none" in '/etc/default/keyboard'. Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by <Ctrl><Shift>u 00a0<Enter>, if needed, but it looks exactly like a regular space. For me, <Super><Space> would be a good shortcut for non-breaking space. OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones  grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. WORKAROUNDS: Run setxkbmap -option "nbsp:none" to make <Alt Gr><space> type regular space character. Even better option is to use "classic", "mac" or "nodeadkeys" keyboard variant instead of "". This could be set up in /etc/default/keyboard and maybe in configuration dialog in your desktop environment. Non-breaking space can still be typed (in GTK apps) by <Ctrl><Shift>u 00a0<Enter>, if needed. Another option is to use compose key: <compose> <space> <space>. In Bash scripts you could also use `printf '\u00a0'` or `printf '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` instead of `printf`.) Or you could set up a variable `readonly nbsp=$'\u00a0'`.
2019-08-21 17:02:40 Timo Aaltonen affects xorg (Ubuntu) xkeyboard-config (Ubuntu)
2019-08-21 17:03:37 Timo Aaltonen xkeyboard-config (Ubuntu): importance Undecided Wishlist
2019-08-21 17:03:37 Timo Aaltonen xkeyboard-config (Ubuntu): status Invalid Opinion
2019-08-22 08:25:55 Jarno Suni description OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones  grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. WORKAROUNDS: Run setxkbmap -option "nbsp:none" to make <Alt Gr><space> type regular space character. Even better option is to use "classic", "mac" or "nodeadkeys" keyboard variant instead of "". This could be set up in /etc/default/keyboard and maybe in configuration dialog in your desktop environment. Non-breaking space can still be typed (in GTK apps) by <Ctrl><Shift>u 00a0<Enter>, if needed. Another option is to use compose key: <compose> <space> <space>. In Bash scripts you could also use `printf '\u00a0'` or `printf '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` instead of `printf`.) Or you could set up a variable `readonly nbsp=$'\u00a0'`. OS: from Hardy to at least Bionic. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones  grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. WORKAROUNDS: Run setxkbmap -option "nbsp:none" to make <Alt Gr><space> type regular space character. Even better option is to use "classic", "mac" or "nodeadkeys" keyboard variant instead of "". This could be set up in /etc/default/keyboard and maybe in configuration dialog in your desktop environment. Non-breaking space can still be typed (in GTK apps) by <Ctrl><Shift>u 00a0<Enter>, if needed. Another option is to use compose key: <compose> <space> <space>. In Bash scripts you could also use `printf '\u00a0'` or `printf '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en` instead of `printf`.) Or you could set up a variable `readonly nbsp=$'\u00a0'`. Yet another workaround would be to use a font that displays regular space and non-breaking space differently, but is there one?