Igor Pechtchanski said:
Does anyone know of a way to get a `-` at the start of $0? I believe
this will force all the shells to start as login shells and is the
most generic solution.
Sure. 'bash -c exec -l $PROG $ARGS'. :-)
Ya beat me to it :) Although, in the current design, this would
The new (very cool!) chere package doesn't work with tcsh, at least on my
system. The problem is that tcsh -l doesn't work with any additional
arguments. There is even a comment to that effect in the script:
tcsh )
# Apparently -l only applies if it is the only argument
# so
Actually I made a minor goof, the order should be:
/etc/csh.cshrc
/etc/csh.login
~/.tcshrc
~/.login
There is also the possibility that ~/.tcshrc does not exist, if that is
the case ~/.cshrc should be read (but not both). I didn't bother with
that as I use
On Wed, Oct 13, 2004 at 07:02:13PM -0400, Christopher Faylor wrote:
Actually, All shells which support -l seem to cd to the home directory.
I'm not sure what the -l adds to the above since the above code just
calls the shell again after cd'ing to the directory.
I think the purpose of that is to
First off, it looks like the postinstall for lftp-2.6.8-1 is expecting
user input, and therefore hangs when run in the Cygwin installer (which no
longer pops up a postinstall output window).
Also (and it might just be me, I dunno) I can download/install gcc-core
and gcc-testsuite-3.3.1-3, but
My recently-updated Cygwin WindowMaker is whining to me:
TIFFReadDirectory: Warning, /usr/X11R6/share/WINGs/Images.tiff:
unknown field with tag 317 (0x13d) encountered.
TIFFReadDirectory: Warning, /usr/X11R6/share/WindowMaker/Icons/Terminal.tiff:
unknown field with tag 317 (0x13d) encountered.
This package includes /etc/csh.login which has the line:
set TERM=cygwin
This should instead read:
set term=cygwin
which will set the shell variable term and the environment variable
TERM correctly when tcsh is used as the base shell for the Cygwin shell
window.
Thanks for
This package includes /etc/csh.login which has the line:
set TERM=cygwin
This should instead read:
set term=cygwin
which will set the shell variable term and the environment variable TERM
correctly when tcsh is used as the base shell for the Cygwin shell window.
-Andy
--
Specify one mirror only when downloading. Notice that some mirrors do
not have 4.3.0-1 yet, so mixing updated mirrors and out of date mirrors
causes problems.
See this message I wrote describing the problem:
http://cygwin.com/ml/cygwin-xfree/2003-08/msg8.html
Harold
*sheepish look*
The major problem is that $shell and $SHELL are now getting set to
/tmp/install/usr/bin/tcsh instead of /usr/bin/tcsh. This is causing the
shell to fail, say in an xterm, trying to exec $SHELL.
I verified that this problem resides in the executable rather than my
configuration files by examining
There is a problem with the /etc/csh.login included in Cygwin package
tcsh-6.11.0-4 (current). Embedded spaces in path elements are not
preserved when the path is modified. As a UNIX user I naturally try to
avoid spaces in pathnames as bad form, but the inherited Windows path
is likely to have
I was having the exact same problem starting X under the newest Cygwin
release. I also found this very frustrating as I have been running X for
quite some time with no problems, then *boom* it suddenly broke.
One option that worked for me was to downgrade to the previous version of
the DLL
This is not really an XFree problem, rather it is a global Cygwin issue
caused by a policy change that took most people by surprise.
Sounds like most people need to read the cygwin release announcements a
little more closely rather than just blindly upgrading.
cgf
It was not my intention
13 matches
Mail list logo
