Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: That darn pipe symbol?

  1. #1

    Default That darn pipe symbol?

    Sorry to keep banging on about this problem, but I hate letting this vindictive computer get the better of me!

    If I ask the question in a different way, maybe it will trigger a few neurons somewhere? Here goes ...

    If I take four different display routes on to this SuSE 11.1 box, I get different results. Why? Now it seems that from the little research that I have done, that this is a particularity thorny topic, so if I am using the wrong terminology, forgive me.

    Base conditions: Desktop manager (when applicable is KDE 4), keyboards are UK styles and the same user login in each case.

    To make sure that I am not confusing the "|" (pipe, 0x7c, 124) symbol with the "" (broken bar, 0xa6, 166), I will use the simple test of piping to grep, like this:cat /etc/motd grep -v "fun". If it is not the pipe symbol, grep will not be called and the motd will be printed.

    a) telnet. FAIL - its a ""
    b) putty. PASS - its a "|"
    c) xrdp/mstsc. In Konsole FAIL - its a ""
    d) hardware console. In Konsole PASS - its a "|"

    Help! Where do I look to resolve this?

    Best regards, Martin

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,244
    Blog Entries
    15

    Default Re: That darn pipe symbol?

    Quote Originally Posted by martinprowe
    Sorry to keep banging on about this problem, but I hate letting this
    vindictive computer get the better of me!

    If I ask the question in a different way, maybe it will trigger a few
    neurons somewhere? Here goes ...

    If I take four different display routes on to this SuSE 11.1 box, I get
    different results. Why? Now it seems that from the little research that
    I have done, that this is a particularity thorny topic, so if I am using
    the wrong terminology, forgive me.

    Base conditions: Desktop manager (when applicable is KDE 4), keyboards
    are UK styles and the same user login in each case.

    To make sure that I am not confusing the "|" (pipe, 0x7c, 124) symbol
    with the "" (broken bar, 0xa6, 166), I will use the simple test of
    piping to grep, like this:cat /etc/motd grep -v "fun". If it is not
    the pipe symbol, grep will not be called and the motd will be printed.

    a) telnet. FAIL - its a ""
    b) putty. PASS - its a "|"
    c) xrdp/mstsc. In Konsole FAIL - its a ""
    d) hardware console. In Konsole PASS - its a "|"

    Help! Where do I look to resolve this?

    Best regards, Martin
    Hi
    You might want to look at the TERM environment variable. Thin putty
    uses vt100? You could try an export of either xterm or vt100.
    Code:
    env |grep TERM
    or;
    echo $TERM
    then;
    export TERM=vt100
    or
    export TERM=xterm
    --
    Cheers Malcolm (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.39-0.3-default
    up 2 days 23:52, 3 users, load average: 0.14, 0.09, 0.06
    GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.18


  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,399

    Default Re: That darn pipe symbol?

    And the systems you type from may not all be UTF-8 capable (just a guess).
    Henk van Velden

  4. #4

    Default Re: That darn pipe symbol?

    Quote Originally Posted by malcolmlewis View Post
    Hi
    You might want to look at the TERM environment variable. Thin putty
    uses vt100? You could try an export of either xterm or vt100.
    Thanks for the suggestion Malcom,
    BUT, in all the quotes cases, the $TERM environment variable is "xterm". Additionally, changing it to "vt100" does not change the display character.

    Regards, Martin

  5. #5

    Default Re: That darn pipe symbol?

    Quote Originally Posted by hcvv View Post
    And the systems you type from may not all be UTF-8 capable (just a guess).
    The remote system is the same in all three cases.

    Oh, and one more test that I've just thought of.
    If I logon the the hardware console, the pipe character displays/functions correctly.
    Additional, from that same hardware console, if I rdesktop localhost, I also get a working pipe symbol.

    This seems to confirm your suspicion that the problem is at the "remote" end? I'm going to investigate the "may not all be UTF-8 capable" angle.

    Regards, Martin
    PS - Any thoughts on how I can do that ...?

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,399

    Default Re: That darn pipe symbol?

    You ask how. Do not know exactly. My brain is just slowly starting on this, maybe I missed something.

    That telnet case. Does it mean you telnet from systema to systemb and then send a command containing a "|" and the command arrives at the other end having a ""? How about starting vi (in that telnet session) and inserting a line with a "|". As vi is UTF-8 consious by default.
    Henk van Velden

  7. #7
    graham NNTP User

    Default Re: That darn pipe symbol?

    martinprowe wrote:


    > a) telnet. FAIL - its a "¦"
    > b) putty. PASS - its a "|"
    > c) xrdp/mstsc. In Konsole FAIL - its a "¦"
    > d) hardware console. In Konsole PASS - its a "|"
    >
    > Help! Where do I look to resolve this?
    >
    > Best regards, Martin
    >

    Perhaps a Alt Gr ` (backtick) works i.e. |


  8. #8

    Default Re: That darn pipe symbol?

    Quote Originally Posted by graham View Post
    Perhaps a Alt Gr ` (backtick) works i.e. |
    Thanks Graham,

    But nope! That produces the broken bar as well.

  9. #9

    Default Re: That darn pipe symbol?

    Quote Originally Posted by hcvv View Post
    That telnet case. Does it mean you telnet from systema to systemb and then send a command containing a "|" and the command arrives at the other end having a ""? How about starting vi (in that telnet session) and inserting a line with a "|". As vi is UTF-8 consious by default.
    Hi HCVV(?),

    Yes, I telnet from System_a to System_b. I am now in a bash shell (I think), if I then hit the pipe key (on my UK keyboard, it is left of the "z" key), I see a broken bar displayed on the screen. The telnet session is in key-by-key mode, so I am assuming that there is no translation by System_a before being sent to System_b. I am trying to find out what code is in fact being sent between System_a and System_B now.

    In your second question, running vi in the telnet session. Same results as above. If I hit the pipe key, I see a broken pipe in vi.

  10. #10
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,399

    Default Re: That darn pipe symbol?

    I see what you mean. I can not help with recreating it here. I have an US keyboard. There is a key left from the zZ and it does <> (for which I use normaly keys right from mM) but the characters on it are \| (I never ever used that key before). I also have a key right from the lL (with ;: and '" in between) that says also and does \|. That is the one I normaly use for a pipe.

    IIRC there is some program that shows you the key-codes (not the ASCII or Unicode) generated when a key is hit. Found showkey(1) with google, but it was another one. At least
    Code:
    showkey -a
    shows you the ASCII codes.

    BTW you have a UK keyboards, but is your system aware of it?


    PS the name is Henk, but the acronym for my full name Hendrik Cornelis van Velden is OK.
    Henk van Velden

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •