From: "Littlefield, tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Slackware 11 aliases, anyone?
Date: Sun, 24 Jun 2007 19:42:58 -0700 [thread overview]
Message-ID: <004c01c7b6d2$8e4f7d70$6c01a8c0@tdsportable> (raw)
In-Reply-To: <467EADB7.8030908@clearwire.net>
you can always remove them from your .bashrc file, or .aliases, what ever
your using.
----- Original Message -----
From: "Gaijin" <gaijin@clearwire.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, June 24, 2007 10:45 AM
Subject: Re: Slackware 11 aliases, anyone?
> Steve Holmes wrote:
>> Like Chuck said, use .profile; that's what I do. Not sure about
>> .bashrc; I've heard of it but never make use of it.
>
> I've always used ~/.bashrc because it was less global in nature. I
> had my user profile and my admin profile, and didn't mix the two. It
> was already set up that way in Debian, and I liked it. Sometimes it was
> a hassle, but it kept me on the straight and narrow for security
> purposes. I'd rather move things to /etc/skel and not interfere with
> how others might want to do things. The global settings are doing that
> to me now, forcing me to keep aliases I don't want. <laughs> Thank you
> for the info.
>
> Michael
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Gaijin
` Littlefield, tyler
` Chuck Hallenbeck
` Doug Smith
` Steve Holmes
` Gaijin
` Littlefield, tyler [this message]
` Gregory Nowak
` Gaijin
` Doug Smith
` Doug Smith
` Doug Sutherland
` Gaijin
` Gregory Nowak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004c01c7b6d2$8e4f7d70$6c01a8c0@tdsportable' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).