1. Forum
  2. USENET
  3. comp.sys.mac.system

  • how can I use mac for working on terminal client?

    From pheonix1t@gmail.com@pheonix1t@gmail.com to comp.sys.mac.system on Saturday, April 15, 2006 17:42:53
    From Newsgroup: comp.sys.mac.system

    hello,
    I'm trying to see a way to use my mac for work stuff.

    AT work, we have a unix system that uses a windows terminal client to
    access it.

    I can connect to the terminal server from my mac, but when I try to use
    the function keys (F1-F12) none of them work! They seem to only work
    from a windows machine.

    Is there something I can buy or do so I can make my mac's function keys
    work like a windows workstation?

    If I can do this, I can get away from having to use windows to get the
    terminal client at work.

    Thanks,

    Dave

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Roger Johnstone@news2006@roger.geek.nz to comp.sys.mac.system on Sunday, April 16, 2006 00:57:56
    From Newsgroup: comp.sys.mac.system

    In <1145148173.951277.106320@z34g2000cwc.googlegroups.com> pheonix1t@
    gmail.com wrote:
    hello,
    I'm trying to see a way to use my mac for work stuff.

    AT work, we have a unix system that uses a windows terminal client to
    access it.

    I can connect to the terminal server from my mac, but when I try to
    use the function keys (F1-F12) none of them work! They seem to only
    work from a windows machine.

    Is there something I can buy or do so I can make my mac's function
    keys work like a windows workstation?

    If I can do this, I can get away from having to use windows to get the terminal client at work.

    Thanks,

    Dave

    Apple's Terminal sends an escape sequence for the function keys. For
    example pressing F1 sends 'escape O P'. Presumably the program on the
    server is expecting some other sequence. If you can find out what it is, perhaps by looking at the Windows terminal program, you can easily
    change it in Terminal's windows settings.

    --
    Roger Johnstone, Invercargill, New Zealand
    http://roger.geek.nz/ ________________________________________________________________________
    No Silicon Heaven? Preposterous! Where would all the calculators go?

    Kryten, from the Red Dwarf episode "The Last Day"
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Tim McNamara@timmcn@bitstream.net to comp.sys.mac.system on Saturday, April 15, 2006 20:45:44
    From Newsgroup: comp.sys.mac.system

    In article <20060416125745535+1200@News.Individual.NET>,
    Roger Johnstone <news2006@roger.geek.nz> wrote:

    In <1145148173.951277.106320@z34g2000cwc.googlegroups.com> pheonix1t@ gmail.com wrote:
    hello, I'm trying to see a way to use my mac for work stuff.

    AT work, we have a unix system that uses a windows terminal client
    to access it.

    I can connect to the terminal server from my mac, but when I try to
    use the function keys (F1-F12) none of them work! They seem to
    only work from a windows machine.

    Is there something I can buy or do so I can make my mac's function
    keys work like a windows workstation?

    If I can do this, I can get away from having to use windows to get
    the terminal client at work.

    Apple's Terminal sends an escape sequence for the function keys. For
    example pressing F1 sends 'escape O P'. Presumably the program on the
    server is expecting some other sequence. If you can find out what it
    is, perhaps by looking at the Windows terminal program, you can
    easily change it in Terminal's windows settings.

    With more specifics about the Unix system being accessed, the question
    might be more specifically answered.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From D P Schreber@schreberdp@rayban.net to comp.sys.mac.system on Sunday, April 16, 2006 11:22:52
    From Newsgroup: comp.sys.mac.system

    On 2006-04-16, pheonix1t@gmail.com <pheonix1t@gmail.com> wrote:
    I can connect to the terminal server from my mac, but when I try to use
    the function keys (F1-F12) none of them work! They seem to only work
    from a windows machine.

    Try running in 'screen'. In other words, open a terminal window in Terminal.app, run 'screen' in that terminal window, then run whatever
    command you use to connect to your server.

    You can also try changing your TERM setting to nsterm. In bash:

    export TERM=nsterm

    In tcsh

    setenv TERM nsterm

    If you want to set the default TERM type to be nsterm you need to use
    the 'defaults' command, since for some reason Terminal.app's preferences
    don't include that option:

    defaults write com.apple.Terminal TermCapString nsterm
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steve W. Jackson@stevewjackson@charter.net to comp.sys.mac.system on Monday, April 17, 2006 15:10:47
    From Newsgroup: comp.sys.mac.system

    In article <-aCdnfU7ScPB8t_ZnZ2dnUVZ_tidnZ2d@comcast.com>,
    D P Schreber <schreberdp@rayban.net> wrote:

    On 2006-04-16, pheonix1t@gmail.com <pheonix1t@gmail.com> wrote:
    I can connect to the terminal server from my mac, but when I try to use
    the function keys (F1-F12) none of them work! They seem to only work
    from a windows machine.

    Try running in 'screen'. In other words, open a terminal window in Terminal.app, run 'screen' in that terminal window, then run whatever
    command you use to connect to your server.

    You can also try changing your TERM setting to nsterm. In bash:

    export TERM=nsterm

    In tcsh

    setenv TERM nsterm

    If you want to set the default TERM type to be nsterm you need to use
    the 'defaults' command, since for some reason Terminal.app's preferences don't include that option:

    defaults write com.apple.Terminal TermCapString nsterm

    Of course, there's always the simple use of .profile, .bashrc and
    similar files to set the TERM variable rather than changing it that way.
    And Terminal does support specifying the .term file as well as remapping
    keys.
    --
    Steve W. Jackson
    Montgomery, Alabama
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From D P Schreber@schreberdp@rayban.net to comp.sys.mac.system on Tuesday, April 18, 2006 07:37:31
    From Newsgroup: comp.sys.mac.system

    On 2006-04-17, Steve W. Jackson <stevewjackson@charter.net> wrote:
    You can also try changing your TERM setting to nsterm.

    Of course, there's always the simple use of .profile, .bashrc and
    similar files to set the TERM variable rather than changing it that way.

    If he really wants a different TERM value all the time, it's certainly
    simpler and cleaner to change the Terminal.app preference. That's what
    it's for. If he only wants the new setting in one specific context,
    best to do it only in that context. Setting it in a shellrc is
    suboptimal either way.

    And of course changing TERM was my second recommendation. The best and simplest approach is trivial: run the connection in 'screen'. Voila,
    standard function key behavior. No preference changes, no .term file
    (though he could make one running 'screen ssh <whatever>' as a
    shortcut), no shellrc changes. The 'screen' command has other nice
    features as well -- anyone running command line apps should get familiar
    with it.
    --- Synchronet 3.18b-Win32 NewsLink 1.113