From: Oliver Wienand <[EMAIL PROTECTED]>
Date: Tuesday, November 22, 2005 10:41 am
Subject: Re: Proper distribution of cygwin-dependent software.
> Hello,
>
> had I to ship the sources or it is sufficient to install an
> unmodified
> version of Cygwin setup, which allows to get all the sources?
Is the path to Cygwin bin directory available in windows registry?
It would be nice if it were there since that would make it easier to use
Cygwin from other programs.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Docu
Christopher Faylor wrote:
On Tue, Nov 22, 2005 at 07:20:26PM +0100, Lennart Borgman wrote:
Is the path to Cygwin bin directory available in windows registry?
It would be nice if it were there since that would make it easier to use
Cygwin from other programs.
"man cygpath&
I think the little correction suggested here never got done for some reason:
http://lists.gnu.org/archive/html/help-emacs-windows/2002-05/msg00079.html
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
I am having trouble with patch. My Cygwin patch (and my GnuWin32 patch)
says it is version 2.5.9. But where is the sources for this? I looked at
ftp://ftp.gnu.org/gnu/patch and they only have version 2.5.4. How can
that be?
Who maintains patch?
--
Unsubscribe info: http://cygwin.com/ml/#
Corinna Vinschen wrote:
On Dec 14 19:30, Lennart Borgman wrote:
I am having trouble with patch. My Cygwin patch (and my GnuWin32 patch)
says it is version 2.5.9. But where is the sources for this? I looked at
ftp://ftp.gnu.org/gnu/patch and they only have version 2.5.4. How can
that be
René Berber wrote:
Lennart Borgman wrote:
I am having trouble with patch. My Cygwin patch (and my GnuWin32 patch)
says it is version 2.5.9. But where is the sources for this? I looked at
ftp://ftp.gnu.org/gnu/patch and they only have version 2.5.4. How can
that be?
The latest GNU
I do not know if I missed something when I installed Cygwin, but I do not have
a shortcut to setup.exe in the Cygwin group in the start menu. I think it
should be there. It is not a command line tool.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http
Joe Smith wrote:
Actually considering that the changelog of 2.5.9 indicates that it is
an actual release, it seems likely that it was never moved over to the
main site only because it was in the wrong directory.
What do I need to be able to build patch 2.5.9 for Cygwin? I downloaded
gcc-co
Dave Korn wrote:
Lennart Borgman wrote:
What do I need to be able to build patch 2.5.9 for Cygwin? I downloaded
gcc-core and make and some other things. Trying to run ./conficure I get
>>>>>>>>>>>>>>>>>>>>>>>>>&g
Dave Korn wrote:
Setup.exe doesn't actually install a copy of itself anywhere, but then again
we could always get it to create a shortcut to http://cygwin.com/setup.exe,
which would also have the advantage of making sure people use the latest
version all the time...
Doesn't it check this ever
Dave Korn wrote:
What do I need to be able to build patch 2.5.9 for Cygwin? I downloaded
gcc-core and make and some other things.
OK, so what happens if you try a command like
as -o /cygdrive/d/temp/foo.o < /dev/null
or a command like
touch /cygdrive/d/temp/ccXbQKlo.o
cheers,
Dav
Dave Korn wrote:
Heh, that's true, although there is a handy trick for the package search:
since cygwin runs on windows, all executables use the ".exe" ending in cygwin
packages. Compare:
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=as
Cygwin Package List
Search Results
Found 755 matches
Brian Dessent wrote:
Lennart Borgman wrote:
Thanks! There is a hit, I did not have "as" from Cygwin. Changed my path
a bit. But how do I find "as"? I would get the package search as it is
now is of no big use for such a name? ;-)
Sigh. 'as' is part
Lennart Borgman wrote:
Dave Korn wrote:
And the answer is that as is the GNU assembler, and it is part of the
binutils package, which lives under the 'Devel' category in setup.
Thanks for this! That trick is so handy in my opinion so it ought to
be as a tip on the search page r
Dave Korn wrote:
Hooray!
Thanks ;-)
1) You didn't say if you've run "make install" yet though, you should do that
rather than attempting to manually copy all the files to their correct
locations.
I tried a just to copy patch.exe. Then I saw this that I just wish I did
not. Here is a c
Dave Korn wrote:
This is (one of the reasons) why you should never put "." in your $PATH!
Thanks, but I did not.
Also, after installing new software, you need to use "hash -r" to refresh
bash's cached list of locations of executables.
Ah, there it is. This is what I needed.
--
Unsub
Brian Dessent wrote:
I am not sure I understand what you mean. What is the "requires" line?
It is in the setup.ini file (which is generated from the individual
setup.hint files), which are not directly seen by the user but parsed by
setup.exe.
Where is it? Should binutils have been d
What is the minimum sequence of operations needed to switch default text
type in Cygwin?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygw
Lennart Borgman wrote:
What is the minimum sequence of operations needed to switch default
text type in Cygwin?
I answer myself here: It seems to me to be to start setup.exe and run it
to its end. Maybe it would be good to make it a bit more clear?
--
Unsubscribe info: http
line endings with patch 2.5.9.
(The only thing that did not work was preservation of line endings in
the patched file, but that seems to be a small problem here.)
To see more of the result see here:
http://ourcomments.org/GNU/patchcrlf/readme.txt
Lennart Borgman wrote:
After finishing the
Eli Zaretskii wrote:
The result is that the only option that seems to be able to handle the
mix of line endings is Cygwin using DOS line endings with patch 2.5.9.
(The only thing that did not work was preservation of line endings in
the patched file, but that seems to be a small problem here.)
Eli Zaretskii wrote:
What's wrong with the patched file having CRLF on Windows?
It is the default line endings on Windows so normally that is what you
want. However if you have a file with LF line endings instead then don't
you probably have that for a reason? I can of course not know the
I use cygwin perl to create some html files from cygwin sh. When I then
later from cmd.exe (or cygwin sh) try to open one of these files from
the command line with
temp.html
I get the error "Access denied". This does not happen if I use the same
trivial script from cmd.exe using ActiveStat
Igor Peshansky wrote:
On Tue, 14 Feb 2006, Lennart Borgman wrote:
I use cygwin perl to create some html files from cygwin sh. When I then
later from cmd.exe (or cygwin sh) try to open one of these files from
the command line with
temp.html
I get the error "Access denied". Thi
Dave Korn wrote:
Or you can chmod +x it. That's longer lasting! ;-)
Plus it could even be done as part of the perl script, and then the problem
would just /never/ arise again and wouldn't need to remember to use 'start' or
'cygstart' to launch it.
Thanks Dave, but what would "chmod +x" b
Igor Peshansky wrote:
"perldoc -f chmod".
Igor
Yes, but it does not know the +x syntax.
Not that particular syntax (hey, you can always 'system("chmod +x $f")'),
but it does allow Fcntl constants (e.g., 'chmod
S_IRWXU|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH $f' -- still from the ab
Igor Peshansky wrote:
Cygwin-created files are not executable unless they are explicitly created
with executable permissions on. Perl doesn't do that, so you get a
non-executable HTML file (and can't run this from CMD). ActiveState perl
lets Windows pick the file ACLs, which are usually based o
I read in the archives that there has been some discussions about
accessibility and Cygwin setup.exe. Are there any plans to improve this?
Keyboard support was not mentioned there but is also an important
accessibility feature for many people. Are there any plans for keyboard
support?
Kind re
Igor Pechtchanski wrote:
On Tue, 18 Oct 2005, Lennart Borgman wrote:
I read in the archives that there has been some discussions about
accessibility and Cygwin setup.exe. Are there any plans to improve this?
Keyboard support was not mentioned there but is also an important
accessibility
llation vs. all not installed. The radio
buttons for prev cur and exp distrobutions work fine. Finally, the check boxes
for add icon to desktop and add icon to start menu do not toggle with the space
bar.
----- Original Message -
From: "Lennart Borgman" <[EMAIL PROTECTED]>
T
Igor Pechtchanski wrote:
If and when I have some working code, I will request that people
interested in accessibility test that code for the features they need.
I would be glad to test, but just the keyboard part.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem re
Sean McMahon wrote:
Well, getting decent keyboard access is naturally an interest of mine. I'll see
what I can dig up about this from my screen-reader manufacturer. More then
likely your assumption is correct, but if it doesn't work with "standard"
windows controlls, that's also something I ne
If I do
info bash
from the bash prompt and try to open "*Bash Features::" I get the error
message in the subject line.
Is this expected or a known bug?
Kind regards,
Lennart
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems
Ok, here is part of my .bash_profile now:
blackOnLightGrey='\[\e[47m\]'
blue='\[\e[1;34m\]'
red='\[\e[1;31m\]'
blackOnWhite='\[\e[0;0;37;30m\]'
# export PS1="${blackOnLightGrey}\n\s\v User \u on host \h in dir \w\n\d \@> "
export PS1="${blackOnLightGrey}\n\s\v User \u on host \h in dir \w\n\d \@
Brian Dessent wrote:
Lennart Borgman wrote:
I do not remember anything about this now, but comparing to my current
PS1 I can see that I has a \] after the last m. I have
PS1=\[\033[32;47m\w >\033[0m\]
That's incorrect. The \[ and \] are to be used only to delineate
non
Eric Blake wrote:
I don't know if you are reproducing the same problem as the OP, since the
OP didn't exactly print what error message he was getting, but you
certainly reproduced a problem.
...
This is probably because you've mounted / as textmode. I don't know if it
is a bug in info or
I am trying to get "bash -i" to start up with $PATH having
/usr/local/bin:/usr/bin:/bin
at the beginning. I believe I need to do this without any init file
running so I set the windows Path variable to contain the
corresponding windows directories first. So I set Path in cmd.exe with
set Pa
After installing cygwin 1.7 beta I tried to start msys sh (which I
have not been doing for a long while). I got the following error:
@c:\msys\1.0\bin\sh --login %*
AllocationBase 0x0, BaseAddress 0x715B, RegionSize 0x15, State 0x1
c:\msys\1.0\bin\sh.exe: *** Couldn't reserve spac
On Tue, Jun 9, 2009 at 12:28 AM, ABCD wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Lennart Borgman wrote:
>> I am trying to get "bash -i" to start up with $PATH having
>>
>> /usr/local/bin:/usr/bin:/bin
>>
>> at the beginnin
On Tue, Jun 9, 2009 at 1:05 AM, Mark Harig wrote:
> From the bash manual (in emacs: M-: (info "(bash) Bash Startup Files")):
>
> "When an interactive shell that is not a login shell is started, Bash
> reads and executes commands from `~/.bashrc', if that file exists.
> This may be inhibited by usin
Ok, thanks. I have reported it as a mingw bug then.
On Tue, Jun 9, 2009 at 2:22 AM, Christopher
Faylor wrote:
> On Mon, Jun 08, 2009 at 11:33:42PM +0200, Lennart Borgman wrote:
>>After installing cygwin 1.7 beta I tried to start msys sh (which I
>>have not been doing for a long wh
In current cygwin (just updated) I need to downcase the test for
CHERE_INVOKING in .profile to make it work, i.e. it need to look like:
if [ ! -z "${chere_invoking}" ]; then
unset CHERE_INVOKING
else
cd "${HOME}"
fi
This is on Windows XP.
--
Problem reports: http://cy
On Fri, Dec 3, 2010 at 6:51 AM, Andy Koppe wrote:
> On 2 December 2010 22:31, Lennart Borgman wrote:
>> In current cygwin (just updated) I need to downcase the test for
>> CHERE_INVOKING in .profile to make it work
>
> To make what work?
>
> /bin/xhere, the part of the
44 matches
Mail list logo
