zsh-users
 help / color / mirror / code / Atom feed
From: Aaron Davies <agdavi01@louisville.edu>
To: zsh-users@sunsite.dk
Subject: Re: Problem with Named Dirs & GNU Screen
Date: Sat, 5 Jun 2004 17:35:29 -0400	[thread overview]
Message-ID: <43C39A74-B738-11D8-9326-000A95EDC31A@louisville.edu> (raw)
In-Reply-To: <80332FAE-B728-11D8-A891-000502631FBD@louisville.edu>

On Jun 5, 2004, at 3:42 PM, Aaron Davies wrote:

> On Saturday, June 5, 2004, at 03:39 PM, Dan Nelson wrote:
>
>> In the last episode (Jun 05), Aaron Davies said:
>>
>>> I've been trying to figure out the named dirs issue I wrote about
>>> several weeks ago, but I'm still having problems. The situation is
>>> this: I would like to create a named dir "palmfiles" expanding to
>>> "~/Documents/Palm/Users/Aaron Davies/Files to Install". To this end, 
>>> I
>>> have in my .zprofile the following line:
>>>
>>> export palmfiles=~/Documents/Palm/Users/Aaron\ Davies/Files\ to\ 
>>> Install
>>>
>>> and in my .zshrc:
>>>
>>> setopt AUTO_NAME_DIRS
>>
>> Try putting that setopt in .zprofile, _above_ your variable 
>> definition,
>> or move the variable definition into .zshrc.  The execution order of
>> startup scripts is:
>>
>> .zshenv .zprofile .zshrc .zlogin
>
> I moved the variable definition into zshrc, which did it. I could have 
> sworn I'd tried that before . . . . Thanks!

BTW, I also tried putting them both in zprofile, which didn't work from 
within screen. It looks like it's not called again when zsh is started 
by screen--I guess it must be started as a non-login shell?
-- 
Aaron Davies
agdavi01@louisville.edu


  reply	other threads:[~2004-06-05 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 19:30 Aaron Davies
2004-06-05 19:39 ` Dan Nelson
2004-06-05 19:42   ` Aaron Davies
2004-06-05 21:35     ` Aaron Davies [this message]
2004-06-06  3:41       ` Dan Nelson

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=43C39A74-B738-11D8-9326-000A95EDC31A@louisville.edu \
    --to=agdavi01@louisville.edu \
    --cc=zsh-users@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).