Hello all,
I originally reported this issue to the msys2 team:
https://github.com/msys2/MSYS2-packages/issues/1839
https://github.com/msys2/MSYS2-packages/pull/4477
But I find that this issue is coming from Cygwin Bash, so I'm reporting
here.
When I use \n after command substitution in $PS1
On 2024-05-21 07:19, Jon Turney via Cygwin-apps wrote:
On 03/05/2024 14:40, Jon Turney via Cygwin-apps wrote:
On 29/04/2024 22:13, Brian Inglis via Cygwin-apps wrote:
I would like to co-maintain or adopt and revive the above package, which was
adopted by Eric but not updated since Yaakov.
On 03/05/2024 14:40, Jon Turney via Cygwin-apps wrote:
On 29/04/2024 22:13, Brian Inglis via Cygwin-apps wrote:
I would like to co-maintain or adopt and revive the above package,
which was adopted by Eric but not updated since Yaakov.
Thanks.
I added this to your packages.
I guess I need to
Command options and arguments auto-completion under the Bash shell
The following packages have been upgraded in the Cygwin distribution:
* bash-completion 2.14
* bash-completion-devel 2.14
bash-completion provides auto-completion for options of and arguments to
hundreds
Command options and arguments auto-completion under the Bash shell
The following packages have been upgraded in the Cygwin distribution:
* bash-completion 2.13
* bash-completion-devel 2.13
bash-completion provides auto-completion for options of and arguments to
hundreds of commands
to further improve the sdesc and ldesc provided to reflect that
completions are provided for thousands of commands and their options and
arguments.
Bash Completions and development
Existing source package:
https://cygwin.com/packages/summary/bash-completion-src.html
Updated cygport:
https
.
Bash Completions and development
Existing source package:
https://cygwin.com/packages/summary/bash-completion-src.html
Updated cygport:
https://cygwin.com/cgit/cygwin-packages/bash-completion/tree/bash-completion.cygport?h=playground
A few comments:
DEPEND="automake dejagnu make s
to reflect that
completions are provided for thousands of commands and their options and arguments.
Bash Completions and development
Existing source package:
https://cygwin.com/packages/summary/bash-completion-src.html
Updated cygport:
https://cygwin.com/cgit/cygwin-packages/bash-completion/tree
On Mon, 1 Apr 2024 at 16:29, Chris Elvidge via Cygwin wrote:
>
> Using bash builtin printf '%(fmt)T', when fmt contains %-d (or %_d),
> there is no output - should print daynumber with no preceding 0 (or with
> preceding space). Similarly %-e. date +"%B %-d" works OK.
>
Using bash builtin printf '%(fmt)T', when fmt contains %-d (or %_d),
there is no output - should print daynumber with no preceding 0 (or with
preceding space). Similarly %-e. date +"%B %-d" works OK.
$ uname -a
CYGWIN_NT-10.0-19045 ASUS-X550C-WIN 3.5.1-1.x86_64 2024-02-27 11:54 U
On 26/01/2024 08:22, Cedric Blancher via Cygwin wrote:
Good morning!
Where can I find the source code for the Cygwin bash package? Not the
bash source itself, I am looking for the data which is used to build
the Cygwin bash package.
Ced
https://cygwin.com/cgit/cygwin-packages/bash/tree
Good morning!
Where can I find the source code for the Cygwin bash package? Not the
bash source itself, I am looking for the data which is used to build
the Cygwin bash package.
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports
The following packages have been uploaded to the Cygwin distribution:
* bash-5.2.21-1
* bash-devel-5.2.21-1
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
The easiest way to unsubscribe is to visit
<https://cygwin.com/mailman/options/cygwin-announce>, and click 'Unsub
On 2023-10-01 22:49, Cedric Blancher via Cygwin wrote:
Where (URL!!) can I find the package config for the Cygwin bash package?
On the Cygwin site, go to Search Packages, enter the package name, select a link
to the package, select the package link at the top of that file list, select
Good morning!
Where (URL!!) can I find the package config for the Cygwin bash package?
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
On 2023-09-22 06:39, Christian Franke via Cygwin wrote:
Martin Wege via Cygwin wrote:
On Fri, Sep 22, 2023 at 9:42 AM Christian Franke via Cygwin
wrote:
Martin Wege via Cygwin wrote:
Hello,
Does Cygwin have a tool to run a bash script as SYSTEM user if my
account already have admin rights
Martin Wege via Cygwin wrote:
On Fri, Sep 22, 2023 at 9:42 AM Christian Franke via Cygwin
wrote:
Martin Wege via Cygwin wrote:
Hello,
Does Cygwin have a tool to run a bash script as SYSTEM user if my
account already have admin rights?
No (AFAIK).
I use psexec from Sysinternals tools
(https
On Fri, Sep 22, 2023 at 9:42 AM Christian Franke via Cygwin
wrote:
>
> Martin Wege via Cygwin wrote:
> > Hello,
> >
> > Does Cygwin have a tool to run a bash script as SYSTEM user if my
> > account already have admin rights?
>
> No (AFAIK).
>
> I u
Martin Wege via Cygwin wrote:
Hello,
Does Cygwin have a tool to run a bash script as SYSTEM user if my
account already have admin rights?
No (AFAIK).
I use psexec from Sysinternals tools
(https://learn.microsoft.com/sysinternals/downloads/psexec)
This starts a Cygwin terminal as SYSTEM
Hello,
Does Cygwin have a tool to run a bash script as SYSTEM user if my
account already have admin rights?
Thanks,
Martin
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info
t; >>>> On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz wrote:
> >>>>> Is there an official way to enter the Cygwin command line (e.g. bash
> >>>>> login) from Windows cmd.exe, e.g. if someone ssh's into a Windows
> >>>>> machine he/she e
command line (e.g. bash
login) from Windows cmd.exe, e.g. if someone ssh's into a Windows
machine he/she ends/up in a cmd.exe and not bash...
You may run your favourite shell from the bin directory of your Cygwin
installation:
"C:\Program Files\Cygwin\bin\bash.exe"
"C:\Program F
On Sun, Aug 13, 2023 at 12:53 AM Roland Mainz via Cygwin
wrote:
>
> On Mon, Aug 7, 2023 at 7:38 AM KAVALAGIOS Panagiotis (EEAS) via Cygwin
> wrote:
> >
> > > On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz
> > > wrote:
> > > > Is there an official wa
On 12/08/2023 23:52, Roland Mainz via Cygwin wrote:
Roland
P.S.: Which reminds me - is there a way to contribute a Cygwin ksh93 package ?
https://cygwin.com/packaging-contributors-guide.html
--
Problem reports: https://cygwin.com/problems.html
FAQ:
On Mon, Aug 7, 2023 at 7:38 AM KAVALAGIOS Panagiotis (EEAS) via Cygwin
wrote:
>
> > On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz
> > wrote:
> > > Is there an official way to enter the Cygwin command line (e.g. bash
> > > login) from Windows cmd.exe, e.g
Thomas Wolff via Cygwin writes:
> Am 07.08.2023 um 06:02 schrieb Roland Mainz via Cygwin:
>> On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz
>> wrote:
>>> Is there an official way to enter the Cygwin command line (e.g. bash
>>> login) from Windows cmd.exe, e.g
Am 07.08.2023 um 06:02 schrieb Roland Mainz via Cygwin:
On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz wrote:
Is there an official way to enter the Cygwin command line (e.g. bash
login) from Windows cmd.exe, e.g. if someone ssh's into a Windows
machine he/she ends/up in a cmd.exe and not bash
On 8/7/23, Roland Mainz via Cygwin wrote:
> On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz wrote:
>> Is there an official way to enter the Cygwin command line (e.g. bash
>> login) from Windows cmd.exe, e.g. if someone ssh's into a Windows
>> machine he/she ends/up in a
> On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz
> wrote:
> > Is there an official way to enter the Cygwin command line (e.g. bash
> > login) from Windows cmd.exe, e.g. if someone ssh's into a Windows
> > machine he/she ends/up in a cmd.exe and not bash...
>
> pin
On Sat, Jul 29, 2023 at 6:18 AM Roland Mainz wrote:
> Is there an official way to enter the Cygwin command line (e.g. bash
> login) from Windows cmd.exe, e.g. if someone ssh's into a Windows
> machine he/she ends/up in a cmd.exe and not bash...
ping!
Bye,
Roland
--
__ .
Hi!
Is there an official way to enter the Cygwin command line (e.g. bash
login) from Windows cmd.exe, e.g. if someone ssh's into a Windows
machine he/she ends/up in a cmd.exe and not bash...
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.ma...@nrubsig.org
\__\/\/__/ MPEG
I have a new Windows 11 machine. I ran setup V2.925 with command-line
options for my default set of packages, clicked through installation,
and specified start menu but no desktop icon. Install seemed to go
smoothly, but while there was a start menu folder for Cygwin with
documentation, there
Greetings, Brian Inglis via Cygwin!
> On 2023-04-06 06:21, Andrey Repin via Cygwin wrote:
>>> I have a "hash bang" bash shell script i.e. first line
>>> #! /bin/sh
>>> or equivalently
>>> #! /bin/bash
>> By default, sh is bash in base Cygwin
On 2023-04-06 06:21, Andrey Repin via Cygwin wrote:
I have a "hash bang" bash shell script i.e. first line
#! /bin/sh
or equivalently
#! /bin/bash
By default, sh is bash in base Cygwin installation.
Q3 - at 1/8 the size of bash and sh, I am not at all sure of the role and reac
,
text tools, etc - had to be tested and usage adjusted accordingly. It
wasn't uncommon to have a starter script that performed compatibility tests
and forked to the appropriate version... of the same code, functionally.
Back to the OP's problem.
I haven't seen the bash source, but if I had
On Thu, Apr 06, 2023 at 04:43:51AM +, Fergus Daly via Cygwin wrote:
> I have a "hash bang" bash shell script i.e. first line
> #! /bin/sh
> or equivalently
> #! /bin/bash
> For various reasons I want this file to be identified as binary so its second
> line
> is
Greetings, Fergus Daly!
> I have a "hash bang" bash shell script i.e. first line
> #! /bin/sh
> or equivalently
> #! /bin/bash
By default, sh is bash in base Cygwin installation.
> Q3 - at 1/8 the size of bash and sh, I am not at all sure of the role and
> reac
Place the nul on the third line. For example:
#!/bin/bash
#
# ^@ identify as a binary file
...
On Thu, Apr 6, 2023 at 4:03 AM Corinna Vinschen via Cygwin <
cygwin@cygwin.com> wrote:
> On Apr 6 04:43, Fergus Daly via Cygwin wrote:
> > I have a "hash bang" bash she
On Apr 6 04:43, Fergus Daly via Cygwin wrote:
> I have a "hash bang" bash shell script i.e. first line
> #! /bin/sh
> or equivalently
> #! /bin/bash
> For various reasons I want this file to be identified as binary so its second
> line
> is the single charact
I have a "hash bang" bash shell script i.e. first line
#! /bin/sh
or equivalently
#! /bin/bash
For various reasons I want this file to be identified as binary so its second
line
is the single character null \x00 showing up in some editors e.g. nano as
^@
This does not prevent the s
The following packages have been uploaded to the Cygwin distribution:
* bash-5.2.15-2
* bash-devel-5.2.15-2
v2: Make /usr/bin/sh.exe a hardlink to /usr/bin/bash.exe, as required.
The v1 installer script accidentally created a symlink.
This is a long overdue update of the bash shell. Given
The following packages have been uploaded to the Cygwin distribution:
* bash-5.2.15-2
* bash-devel-5.2.15-2
v2: Make /usr/bin/sh.exe a hardlink to /usr/bin/bash.exe, as required.
The v1 installer script accidentally created a symlink.
This is a long overdue update of the bash shell. Given
[first announcement was a bit... incomplete...]
The following packages have been uploaded to the Cygwin distribution:
* bash-5.2.15-1
* bash-devel-5.2.15-1
This is a long overdue update of the bash shell. Given the big step in
the version, this is a TEST release for now. Please give it a try
[first announcement was a bit... incomplete...]
The following packages have been uploaded to the Cygwin distribution:
* bash-5.2.15-1
* bash-devel-5.2.15-1
This is a long overdue update of the bash shell. Given the big step in
the version, this is a TEST release for now. Please give it a try
The following packages have been uploaded to the Cygwin distribution:
* bash-5.2.15-1
* bash-devel-5.2.15-1
This is a long overdue update of the bash shell. Given the big
step in the version, this is a TEST release for now. Please give
it a try.
This release is based on the Fedora Linux 37
The following packages have been uploaded to the Cygwin distribution:
* bash-5.2.15-1
* bash-devel-5.2.15-1
This is a long overdue update of the bash shell. Given the big
step in the version, this is a TEST release for now. Please give
it a try.
This release is based on the Fedora Linux 37
On 2023-01-15 14:24, Nouman Shahid via Cygwin wrote:
Bash 1876 error occured
That's neither a command line or an actual error message that tells anyone
anything about what your problem was, what command caused it, and what versions
of bash, Cygwin, and Windows you are running.
Ideally
We're running into this same issue on my project. We're trying to
shorten path names to get around Visual Studio limitations in path
lengths, which are unfortunately very long for us since we're
generating filenames based on package names and the like.
If subst won't work to let us shorten path
On 9/5/2022 2:43 PM, Mauro Zallocco wrote:
I upgraded my cygwin install recently on my windows 10 machine.
CYGWIN_NT-10.0-19044 DESKTOP-CTVRG06 3.3.5-341.x86_64 2022-05-13 12:27 UTC
x86_64 Cygwin
When pasting the following commands into the cygwin terminal:
echo 1
echo 2
echo 3
I get the text
I upgraded my cygwin install recently on my windows 10 machine.
CYGWIN_NT-10.0-19044 DESKTOP-CTVRG06 3.3.5-341.x86_64 2022-05-13 12:27 UTC
x86_64 Cygwin
When pasting the following commands into the cygwin terminal:
echo 1
echo 2
echo 3
I get the text appearing on the cygwin terminal, highlighted,
On Tue, Jul 5, 2022 at 6:18 AM Takashi Yano wrote:
>
> On Mon, 4 Jul 2022 08:57:09 +0300
> Orgad Shaneh wrote:
> > Sure,
> >
> > Install VS Code and Node.JS.
> >
> > Clone this repository: https://github.com/orgads/cygtest
> >
> > Open the directory in VS Code and run (F5). Wait for it to finish,
On Mon, 4 Jul 2022 08:57:09 +0300
Orgad Shaneh wrote:
> Sure,
>
> Install VS Code and Node.JS.
>
> Clone this repository: https://github.com/orgads/cygtest
>
> Open the directory in VS Code and run (F5). Wait for it to finish,
> then run again.
>
> I've noticed that even the first execution
Sure,
Install VS Code and Node.JS.
Clone this repository: https://github.com/orgads/cygtest
Open the directory in VS Code and run (F5). Wait for it to finish,
then run again.
I've noticed that even the first execution has some mistyped
characters (moved from ** to ##):
waitForDeb**u**gge**r**
On Sun, 3 Jul 2022 16:02:46 +0300
Orgad Shaneh wrote:
> On Sun, Jul 3, 2022 at 2:18 AM Takashi Yano wrote:
> >
> > On Sat, 2 Jul 2022 08:34:06 +0900
> > Takashi Yano wrote:
> > > Thanks. I could reproduce the issue. I will submit a patch
> > > for this issue shortly.
> >
> > Does the patch I
On Sun, Jul 3, 2022 at 2:18 AM Takashi Yano wrote:
>
> On Sat, 2 Jul 2022 08:34:06 +0900
> Takashi Yano wrote:
> > Thanks. I could reproduce the issue. I will submit a patch
> > for this issue shortly.
>
> Does the patch I pushd to cygwin-3_3-branch solve the
> VS Code issue?
Hi Takashi,
Thank
On Sat, 2 Jul 2022 08:34:06 +0900
Takashi Yano wrote:
> Thanks. I could reproduce the issue. I will submit a patch
> for this issue shortly.
Does the patch I pushd to cygwin-3_3-branch solve the
VS Code issue?
--
Takashi Yano
--
Problem reports: https://cygwin.com/problems.html
FAQ:
On Fri, 1 Jul 2022 01:02:43 +0300
Orgad Shaneh wrote:
> I might have found a way to reproduce on Cygwin (3.3.5). I can
> reproduce this on both Windows Terminal and the native console (Just
> running Cygwin.bat).
>
> Open Cygwin terminal. Paste the following text (can either be with
> Shift-Ins
Adam Dinwoodie
> > > > > > wrote:
> > > > > > >
> > > > > > > On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > &
ote:
> > > > On Fri, May 27, 2022 at 11:06 AM Orgad Shaneh wrote:
> > > > >
> > > > > On Fri, May 27, 2022 at 10:59 AM Adam Dinwoodie
> > > > > wrote:
> > > > > >
> > > > > > On Fri, May 27, 2022 at 10:1
> > > > On Fri, May 27, 2022 at 10:59 AM Adam Dinwoodie
> > > > wrote:
> > > > >
> > > > > On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I'm u
; > >
> > > > On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> > > > > Hi,
> > > > >
> > > > > I'm using Git Bash as the default terminal in VS Code. Using Git for
> > > > > Windows 2.36.1 with the latest ru
On Fri, 27 May 2022 15:22:23 +0300
Orgad Shaneh wrote:
> On Fri, May 27, 2022 at 11:06 AM Orgad Shaneh wrote:
> >
> > On Fri, May 27, 2022 at 10:59 AM Adam Dinwoodie wrote:
> > >
> > > On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> > >
On Fri, May 27, 2022 at 11:06 AM Orgad Shaneh wrote:
>
> On Fri, May 27, 2022 at 10:59 AM Adam Dinwoodie wrote:
> >
> > On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> > > Hi,
> > >
> > > I'm using Git Bash as the default terminal i
On Fri, May 27, 2022 at 10:59 AM Adam Dinwoodie wrote:
>
> On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> > Hi,
> >
> > I'm using Git Bash as the default terminal in VS Code. Using Git for
> > Windows 2.36.1 with the latest runtime, based on cygwi
On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> Hi,
>
> I'm using Git Bash as the default terminal in VS Code. Using Git for
> Windows 2.36.1 with the latest runtime, based on cygwin 3.5.0.
Hi Orgad,
Git for Windows and Git Bash are based in part on Cygwin,
Hi,
I'm using Git Bash as the default terminal in VS Code. Using Git for
Windows 2.36.1 with the latest runtime, based on cygwin 3.5.0.
I have a launch configuration that executes a Node.JS application in
the integrated terminal.
When I launch it for the first time, it spawns a new terminal
en attempting to reference a network drive. There have been a couple of
> >> other
> >> threads reporting this and talk about patches. Is there a fix coming for
> >> this
> >> in the production version of cygwin?
> >>
> >> $ cd /cygdrive/w
patches. Is there a fix coming for this
in the production version of cygwin?
$ cd /cygdrive/w
bash: cd: /cygdrive/w: Too many levels of symbolic links
$ mount
C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin64 on / type ntfs (binary
re a fix coming for
> this
> in the production version of cygwin?
>
> $ cd /cygdrive/w
> bash: cd: /cygdrive/w: Too many levels of symbolic links
> $ mount
> C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
> C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
> C:
bash: cd: /cygdrive/w: Too many levels of symbolic links
$ mount
C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin64 on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,noacl,posix=0,user,noumount,auto)
D: on /cygdrive/d
Greetings, James!
> Never mind I'd say. I got the error when launching
> C:\Appz\Cygwin\Cygwin.bat
> Which is just
> @echo off
> C:
> chdir C:\Appz\Cygwin\bin
> bash --login -i
> If however I run
> C:\cygwin64\bin\mintty.exe
> It works fine.
This means you have
rt this problem to the public mailing list cygwin@cygwin.com"
message in 'bash' with something like:
"Please visit
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
for help with this issue"
This has been done in recent releases for some years, but ancient legacy
rele
rt this problem to the public mailing list cygwin@cygwin.com"
message in 'bash' with something like:
"Please visit
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
for help with this issue"
This removes the need for an autoresponder and is more helpful at the
same
cygwin@cygwin.com"
message in 'bash' with something like:
"Please visit
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
for help with this issue"
This removes the need for an autoresponder and is more helpful at the
same time. Users might be reluctant to joi
Voila, thanks!
Have a nice weekend ya'all
On Sat, Apr 2, 2022 at 8:31 AM wrote:
> >Hi there,
>
>
> >I just got that error message, asking me to report it here.
>
> > 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute
> FAST_CWD
> >
Never mind I'd say. I got the error when launching
C:\Appz\Cygwin\Cygwin.bat
Which is just
@echo off
C:
chdir C:\Appz\Cygwin\bin
bash --login -i
If however I run
C:\cygwin64\bin\mintty.exe
It works fine.
On Sat, Apr 2, 2022 at 8:28 AM James wrote:
> Hi there,
>
>
> I just go
>Hi there,
>I just got that error message, asking me to report it here.
> 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer. Please report this problem to the public mailing list
>cygwin@cygwin.com
>Not sure if it's interesting?
>
Hi there,
I just got that error message, asking me to report it here.
1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
pointer. Please report this problem to the public mailing list
cygwin@cygwin.com
Not sure if it's interesting?
Kind regards,
James
--
Problem
On 2022-03-11, Gary Johnson wrote:
> On 2022-03-11, Gary Johnson wrote:
> > On 2022-03-11, Adam Dinwoodie wrote:
> > > On Thu, Mar 10, 2022 at 04:55:40PM -0800, Gary Johnson wrote:
>
> > > > So, does anyone know why is takes so much longer for bash to run the
>
On 2022-03-11, Gary Johnson wrote:
> On 2022-03-11, Adam Dinwoodie wrote:
> > On Thu, Mar 10, 2022 at 04:55:40PM -0800, Gary Johnson wrote:
> > > So, does anyone know why is takes so much longer for bash to run the
> > > vim I built than the official Cygwin vim? More
ptions such as Ruby that I don't have support
> > for on my system.
> >
> >
> >
> > So, does anyone know why is takes so much longer for bash to run the
> > vim I built than the official Cygwin vim? More importantly, how do
> > I fix this?
>
> There are
>
> So, does anyone know why is takes so much longer for bash to run the
> vim I built than the official Cygwin vim? More importantly, how do
> I fix this?
There are a few differences that jump to mind between the Cygwin
packaged Vim and your locally built Vim. This isn't my area of
ex
to be in Vim itself, I thought
the difference might be in bash, so I ran both programs using strace
like this.
$ strace -o strace_bash_cygwin_vim bash -c "/usr/bin/vim -N -u NONE -i NONE
-cq"
$ strace -o strace_bash_local_vim bash -c
"/usr/local/src/vim-debug/vim/src/vim -N -u N
Greetings, Claude TETE!
> Hi all,
> A bash in a local mounted drive, use realpath instead of mounted one
> for all child processes.
> Example, mount a local folder on Z: drive, go in there and run any
> external command:
> $ subst Z: C:\\Users
> $ cd /cygdrive/z/
>
n testing, I've been unable to
> > > build a version that doesn't crash/dump core on linux and don't
> > > really think the 5.x series has had a thorough vetting such
> > > that it would be regarded as being as stable as 4.3/4.4.
> >
> > fyi, we've been
Does bash 5.1 crash in cygwin? Please let us know so we can help - bash 4.4 is
now over 5 years old
On 3/5/2021 2:23 PM, Christoph Reiter wrote:
On Fri, Mar 5, 2021 at 5:50 PM L A Walsh wrote:
Really I don't see a compelling reason there should be
any hurry to update. In my own
On Feb 21 09:40, Takashi Yano wrote:
> On Mon, 21 Feb 2022 01:05:32 +0100
> Thomas Wolff wrote:
> > pwd -P will also work like /bin/pwd - but: subst is more comparable to
> > mount than to ln -s
>
> Ah, indeed, mount --bind a/b/c c in Linux does not behave
> like this.
>
> Corinna, what do you
On Mon, 21 Feb 2022 01:05:32 +0100
Thomas Wolff wrote:
> Am 21.02.2022 um 00:56 schrieb Takashi Yano:
> > On Mon, 21 Feb 2022 08:41:52 +0900
> > Takashi Yano wrote:
> >> On Sun, 20 Feb 2022 22:38:53 +0100
> >> Claude TETE wrote:
> >>> A bash i
Am 21.02.2022 um 00:56 schrieb Takashi Yano:
On Mon, 21 Feb 2022 08:41:52 +0900
Takashi Yano wrote:
On Sun, 20 Feb 2022 22:38:53 +0100
Claude TETE wrote:
A bash in a local mounted drive, use realpath instead of mounted one
for all child processes.
Example, mount a local folder on Z: drive
On Mon, 21 Feb 2022 08:41:52 +0900
Takashi Yano wrote:
> On Sun, 20 Feb 2022 22:38:53 +0100
> Claude TETE wrote:
> > A bash in a local mounted drive, use realpath instead of mounted one
> > for all child processes.
> >
> > Example, mount a local folder on Z:
On Sun, 20 Feb 2022 22:38:53 +0100
Claude TETE wrote:
> A bash in a local mounted drive, use realpath instead of mounted one
> for all child processes.
>
> Example, mount a local folder on Z: drive, go in there and run any
> external command:
> $ subst Z: C:\\Users
> $ cd
Hi all,
A bash in a local mounted drive, use realpath instead of mounted one
for all child processes.
Example, mount a local folder on Z: drive, go in there and run any
external command:
$ subst Z: C:\\Users
$ cd /cygdrive/z/
$ /bin/pwd
/cygdrive/c/Users
Expected
/cygdrive/w
Issue since Cygwin
Cool, thanks.
-Original Message-
From: Cygwin On Behalf Of
Corinna Vinschen
Sent: 13 December 2021 15:06
To: cygwin@cygwin.com
Subject: Re: Starting CMD from a bash shell with current directory on a
mounted/network drive results in an incorrect current directory
On Dec 13 20:06, Takashi
On Dec 13 20:06, Takashi Yano wrote:
> On Mon, 13 Dec 2021 10:53:41 -
> "john daintree" wrote:
> > I've just upgraded a machine from Windows 10 to Windows 11. Part of my work
> > process is now broken because when starting cmd from Cygwin with the current
> > directory on a mounted drive I get
Excellent news, thank you. I apologise if I should have seen that
somewhere.
/John
-Original Message-
From: Cygwin On Behalf Of
Takashi Yano
Sent: 13 December 2021 11:06
To: cygwin@cygwin.com
Subject: Re: Starting CMD from a bash shell with current directory on a
mounted/network drive
On Mon, 13 Dec 2021 10:53:41 -
"john daintree" wrote:
> I've just upgraded a machine from Windows 10 to Windows 11. Part of my work
> process is now broken because when starting cmd from Cygwin with the current
> directory on a mounted drive I get the following error/warning/issue:
>
>
>
>
Hello All,
I've just upgraded a machine from Windows 10 to Windows 11. Part of my work
process is now broken because when starting cmd from Cygwin with the current
directory on a mounted drive I get the following error/warning/issue:
/cygdrive/j$ cmd
'\\nas00.\devt\users\johnd'
On Nov 3 15:14, Takashi Yano wrote:
> - Currently, bash occasionally exits by Ctrl-C with the following
> scenario.
> 1) Start bash in the command prompt.
> 2) Run 'exec bash'.
> 3) Press Ctrl-C several times.
> This patch fixes the issue.
> ---
> wins
- Currently, bash occasionally exits by Ctrl-C with the following
scenario.
1) Start bash in the command prompt.
2) Run 'exec bash'.
3) Press Ctrl-C several times.
This patch fixes the issue.
---
winsup/cygwin/sigproc.cc | 8
1 file changed, 8 insertions(+)
diff --git
ions under /usr/local/{share/,}man/ nor
under /usr/share/man/linux/ (man -m linux)!
I could probably look at bash-completion if I can get around to bash,
as I would worry about dependencies, fixes, and tweaks. There are big
challenges in bash and coreutils being years out of date as parts of
1 - 100 of 5883 matches
Mail list logo
