From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: List of unresolved issues
Date: Thu, 13 Apr 2000 15:55:23 +0000 [thread overview]
Message-ID: <1000413155523.ZM17016@candle.brasslantern.com> (raw)
In-Reply-To: <200004131246.OAA14948@beta.informatik.hu-berlin.de>
On Apr 13, 2:46pm, Sven Wischnowsky wrote:
} Subject: Re: List of unresolved issues
}
}
} Bart Schaefer wrote:
}
} > Some of these may actually have been resolved and I just forgot/missed it.
} > Also, these are only issues raised in messages I sent myself.
} >
} > ...
} > 10187 combining multiple zstyle commands into one
}
} I offer to write it when you folks decide that we want it.
Actually, I now think the shell function implementation is fine. Maybe
just copy that function into Functions/Misc?
I don't care about the -L output part.
} > 10071 xtrace behavior of `.' and `source'
}
} I still find our behaviour much more consistent and it gives us both
} possibilities. So if at all, I think we should use a option for it
} (yet another `emulate ksh' thing).
I, too, think it should stay as it is, but I didn't want the decision to
be made by simply being overlooked.
} > 9778 hanging on loops with lots of output
}
} Oops. I had forgotten about this one. Does it still happen?
At last report it did, but then I've never been able to reproduce it
myself.
} > ...
} > 9062 suspending `.' / `source'
}
} An option? Tested only after the init scripts have been read?
Again, I don't care, this could stay the way it is. It's another bash/ksh
thing though, IIRC.
} > 8698 bad node type in freenode (related to 9095?)
}
} I sent a patch for this in 8721 (at least it solved it for me).
OK, that's fine; as I said, I may have missed the solutions to some of
these.
} And there is also still your FPATH-in-the-environment-and-then-that-if
} thing...
Yes, I was intending to look at that myself. However, I'm about to go
out of town for a week (starting tomorrow (i.e. Friday) morning) so if
somebody else has a chance to examine it, please go ahead.
I may answer some more mail tomorrow before heading out, but there's not
even a telephone where I'll be next week, so past tomorrow you won't hear
from me until after Easter.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-13 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-13 12:46 Sven Wischnowsky
2000-04-13 15:55 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-14 8:18 Sven Wischnowsky
2000-04-14 14:57 ` Bart Schaefer
2000-04-12 6:14 Bart Schaefer
2000-04-12 15:56 ` Andrej Borsenkow
2000-04-12 20:55 ` Peter Stephenson
2000-04-13 0:26 ` Bart Schaefer
2000-04-13 8:56 ` Peter Stephenson
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=1000413155523.ZM17016@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.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).