home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!umn.edu!noc.msc.net!uc.msc.edu!raistlin!ems!ems.cdc.com!ghart
- From: ghart@ems.cdc.com (Geoffrey Hart)
- Newsgroups: comp.os.linux
- Subject: Re: X-windows & aliases
- Message-ID: <31514@nntp_server.ems.cdc.com>
- Date: 8 Jan 93 22:40:39 GMT
- References: <1159.1189.uupcb@satalink.com> <fluet.726525307@ee.ualberta.ca>
- Sender: sys@ems.ems.cdc.com
- Reply-To: ghart@ems.cdc.com
- Organization: Empros Systems International, a division of CDC
- Lines: 23
- Nntp-Posting-Host: nyh4.ems.cdc.com
-
- In article <fluet.726525307@ee.ualberta.ca>, fluet@ee.ualberta.ca (Kevin Blaine Fluet) writes:
- |> john.will@satalink.com (John Will) writes:
- |> >Can anyone tell me how you get your aliases that appear in .profile to
- |> >be recognized when you're running X-Windows? I have X running like a
- |>
- |> Me too, please. Not being able to type ll in an X terminal is driving me
- |> nuts! Am I missing some file somewhere? (I'm running SLS .99 with
- |> Xfree1.1 by the way).
-
- It seems to me that the standard window manager or the standard X resources
- for Xterm try and use /bin/sh as the shell. I changed mine to /bin/bash
- and everything works. On my system, /bin/sh was a link to /bin/bash, so
- apparently bash was detecting it's name, and turning on only the
- appropriate features (aliases aren't sh).
-
- Another note: I don't think aliases are normally exported to subshells,
- whereas .bashrc (or whatever's in ENV) is executed by subshells, so my rule
- is to put alias definitions in .bashrc. I'm more familiar with ksh, but I
- think the bash behavior matches ksh in this case. Perhaps some bash
- experts would expand on this?
-
- --
- geoff hart ghart@ems news@ems library@ems x4273 s/ems/ems.cdc.com/
-