Thanks Juhamatti Niemelä for the hack. I think it would be user-friendly
that identically looking commands work same way by default, too.
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You received this bug notification because you are a member of Ubuntu
I did a little more searching and found out, that altgr+space behaviour
can be altered with xkb option nbsp. Adding following line to the
keyboard InputDevice section in xorg.conf avoids this issue by disabling
the nbsp.
Option XkbOptions nbsp:none
In KDE systems this can be done alternatively
Problem seems to be in keyboard layout. ie. AltGr + space produces
different byte sequence in us- and fi-layouts. This can be verified with
following commands. (In both cases the space between quotes is typed by
pressing AltGr+space)
$ setxkbmap us
$ echo | hexdump
000 0a20
002
$
The bug is not about shift+space, but altgr+space. You can not configure
it in Xubuntu's desktop environment. Can anybody tell why is the effect
of altgr+space changed in (X)ubuntu 8.04?
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You received this bug
i am sorry about invalidating your bug! feel free to reopen the bug and
file it against the relevant packages. this greatly increases the chance
of being noticed by the right guys.
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You received this bug
under system - preferences - keyboard - layouts - layout options you
can choose what shift+space should do. marking this as invalid.
** Changed in: ubuntu
Status: New = Invalid
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You received this bug
I can confirm this!
Clean install of Hardy 64bit.
[EMAIL PROTECTED]:~$ lspci | grep VGA
bash: grep: command not found
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$ ls -l / | grep home
bash: grep: command not found
[EMAIL PROTECTED]:~$ ls -l / | /bin/grep home
bash: /bin/grep: No such file or
I am using the i386 version.
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Are you sure you aren't inserting an altgr+space character after the
pipe character instead of just the normal space? I'm suspecting this
because there is an additional empty space after bash: (somecommand):
command not found
If grep wasn't found, bash would say:
bash: grep: command not found
you
Looks like Flyspray ate the double space from my previous comment.
Anyway, you are seeing double empty space after the first colon in the
bash error message, which you shouldn't.
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You received this bug
crwl, you are right about the altgr+space character. But it didn't
matter in ubuntu 7.10 terminals xterm and xfce4-terminal tested. Why is
the change? I guess I'll have to quit using any space there.
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You
Is there possibility that hard disk is working unreliably? Is there a
way to check the drive? It has ext3 filesystem.
--
[Hardy] Piping commands does not work always
https://bugs.launchpad.net/bugs/218637
You received this bug notification because you are a member of Ubuntu
Bugs, which is
12 matches
Mail list logo
