In a message dated 1/11/99 11:53:37 AM Central Standard Time, [EMAIL PROTECTED]
writes:
> You don't need any of that if you are running bash, and the other
> shells probably have equivalent ways of handling it. I simply put all
> aliases in my ~/.bashrc file, and they are always read by every
>
Nicholas Lee <[EMAIL PROTECTED]> writes:
> On Mon, 11 Jan 1999, Frank Barknecht wrote:
>
> > ...and none of these change the handling of aliasses.
> > If the aliasses get only read by a login shell (i.e. they are defined in
> > .bash_profile) the following Xresource makes every xterm a login shel
On Mon, 11 Jan 1999, Frank Barknecht wrote:
> ...and none of these change the handling of aliasses.
> If the aliasses get only read by a login shell (i.e. they are defined in
> .bash_profile) the following Xresource makes every xterm a login shell:
>
> xterm*loginShell: true
>
Alternatively, wit
Steven Baker hat gesagt: // Steven Baker wrote:
> The reason _why_ it doesn't read your alias requires a long winding
> explanation, so I won't go into detail here... but, the way to fix it, is by
> using X resources.
>
> Edit ~/.Xresources in your favorite text editor. ANd use these resources
[EMAIL PROTECTED] wrote:
>
> Well, I tried to start another xterm window from the first one, but for some
> reason, it doesn't recognize the aliases the first window does. What gives?
> I typed the xterm command line exactly as it came from the Xsession file, and
> it didn't help. Isn't the seco
The reason _why_ it doesn't read your alias requires a long winding
explanation, so I won't go into detail here... but, the way to fix it, is by
using X resources.
Edit ~/.Xresources in your favorite text editor. ANd use these resources
xterm*font:
xterm*background:
xterm*fo
6 matches
Mail list logo
