unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Matthew Flaschen <matthew.flaschen@gatech.edu>
To: emacs <help-gnu-emacs@gnu.org>
Subject: Re: "source" shell commands
Date: Sun, 25 Mar 2007 20:44:39 -0400	[thread overview]
Message-ID: <46071777.9000502@gatech.edu> (raw)
In-Reply-To: <6A88E31C-15DF-4589-9D89-F5C572080230@Web.DE>

Peter Dyballa wrote:
> 
> Am 25.03.2007 um 12:55 schrieb Matthew Flaschen:
> 
> What is pstree showing? For me, on Mac OS X, and launched from some
> menu, I get:
> 
>     pete 123 /\ pstree -p $$
>     -+= 00001 root /sbin/launchd -v
>     \-+- 01695 pete -bin/tcsh -i -c /usr/local/bin/emacs-23.0.0
> -geometry  100x57+666+44
>        \-+- 01700 pete /usr/local/bin/emacs-23.0.0 -geometry 100x57+666+44
>          \-+= 01701 pete -bin/tcsh -i
>            \-+= 04001 pete pstree -p 1701
>              \--- 04002 root ps -axwwo user
> 
> An interactive tcsh stands at my beginning.

All I get from that (run from a VT) is

bash(12773)--pstree(12790)

Clearly, it's not showing the initial shell.

> When the login bash hits the first of the many personal RC files, it
> only executes the first one. So, IMO, it's best to put everything
> personal in Bourne shell syntax into ~/.profile, which a Bourne shell or
> Bourne shell bash will read (and execute) also.

I moved ~/.bashrc to ~/.bash_profile .  I primarily use zsh , so I don't
want to use generic profile.

>> Should I source ~/.rc in ~/.profile instead?
> No. Keep it simple, let bash do its job right.

That's not desirable, because ~/.rc is supposed to be usable by multiple
shells.

Thanks,

Matt Flaschen

  reply	other threads:[~2007-03-26  0:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1360.1174733204.7795.help-gnu-emacs@gnu.org>
2007-03-24 13:33 ` "source" shell commands Tassilo Horn
2007-03-24 14:35   ` David Kastrup
2007-03-24 15:24     ` Barry Margolin
2007-03-24 21:21       ` Matthew Flaschen
2007-03-25  0:08         ` Matthew Flaschen
2007-03-25 10:33           ` Peter Dyballa
2007-03-25 10:55             ` Matthew Flaschen
2007-03-25 11:53               ` Peter Dyballa
2007-03-26  0:44                 ` Matthew Flaschen [this message]
2007-03-26  8:16                   ` Peter Dyballa
2007-03-26  9:59                     ` Matthew Flaschen
     [not found]               ` <mailman.1412.1174823876.7795.help-gnu-emacs@gnu.org>
2007-03-25 22:36                 ` Tim X
2007-03-26  0:53                   ` Matthew Flaschen
     [not found]                   ` <mailman.1432.1174870550.7795.help-gnu-emacs@gnu.org>
2007-03-26 11:30                     ` Tim X
     [not found]       ` <mailman.1381.1174771402.7795.help-gnu-emacs@gnu.org>
2007-03-25  2:46         ` Tim X
2007-03-25  4:03           ` Matthew Flaschen
     [not found]           ` <mailman.1397.1174795525.7795.help-gnu-emacs@gnu.org>
2007-03-25 10:56             ` Tim X
2007-03-26  8:13             ` Tassilo Horn
2007-03-26  8:57               ` Matthew Flaschen
     [not found]               ` <mailman.1436.1174899596.7795.help-gnu-emacs@gnu.org>
2007-03-26  9:08                 ` Tassilo Horn
2007-03-26  9:55                   ` Matthew Flaschen
2007-03-25  2:32 ` Tim X
2007-03-25  2:59   ` Matthew Flaschen
2007-03-24 10:44 Matthew Flaschen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46071777.9000502@gatech.edu \
    --to=matthew.flaschen@gatech.edu \
    --cc=help-gnu-emacs@gnu.org \
    /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).