On Mon, Dec 12, 2011 at 01:13:02AM -0600, Tim McDaniel wrote:
> On Mon, 12 Dec 2011, Mike Brown wrote:
>> Doing some more digging I found
>> the following posting (via google):
>>
>>> Does changing 'bash' to '/bin/bash' make a difference?
>>
>>Answering my own question: yes.
>>
>>There
On Dec 11 21:32, Samuel Thibault wrote:
> Corinna Vinschen, le Thu 08 Dec 2011 09:47:45 +0100, a écrit :
> > Too bad. In that case, Samuel, can you please have a closer look to
> > see what broke brltty?
>
> The switch to mintty, simply. Brltty uses ReadConsoleOutputCharacter()
> to get the text
On Dec 12 05:56, Heiko Elger wrote:
> Here's a test from Win7/64 SP1 with MVFS version 7.1.1.7 (Wed Aug 3 22:33:34
> 2011).
>
> ente59@PCFX061 /cygdrive/c/MyDevelopment/cygwin/test-qfif
> $ ./test-
> qfif.exe /cygdrive/v/Stg_V5.108_ente59_iv/stg2/steuerung
> /cygdrive/v/Stg_V5.108
> _ente59_iv/
XP Pro SP3
I get the following failure whether I use the current cygwin1.dll
CYGWIN_NT-5.1 lunatick 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
or today's test cygwin1.dll
CYGWIN_NT-5.1 lunatick 1.7.10s(0.255/5/3) 20111212 01:22:59 i686 Cygwin
(as not certain what you were asking).
A
On Dec 12 09:57, Fergus wrote:
> XP Pro SP3
>
> I get the following failure whether I use the current cygwin1.dll
> CYGWIN_NT-5.1 lunatick 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
> or today's test cygwin1.dll
> CYGWIN_NT-5.1 lunatick 1.7.10s(0.255/5/3) 20111212 01:
Version 1.52-1 of cppcheck has been uploaded, following the upstream release.
cppcheck is a tool for static C/C++ code analysis. It tries to detect bugs that
your C/C++ compiler doesn't see. The goal is no false positives.
cppcheck is versatile. You can check non-standard code that includes var
The results for NcFsd (with NovellClient 2 SP2):
$ uname -s
CYGWIN_NT-6.1-WOW64
$ /usr/lib/csih/getVolInfo //OESI2/VOL_MISC1
Device Type: 7
Characteristics: 30
Volume Name:
Serial Number : 1549160268
Max Filenamelength : 255
Filesystemname :
Flags : a2
On Dec 12 14:03, Franz Sirl wrote:
> The results for NcFsd (with NovellClient 2 SP2):
>
Thanks, but...
> NtQueryFullAttributesFile(\??\J:\FRA\xyz.tst) by name works
> NtQueryFullAttributesFile(\??\J:\FRA\xyz.tst) by handle works
>
>
> and for NWFS (with NovellClient 4.91 SP5 IR1 + followup pat
On Dec 8 14:31, Enrico Forestieri wrote:
> Enrico Forestieri writes:
> >
> > However, I experimented a bit with the last snapshot, and even using Greek
> > or Japanese characters in file names, lyx seems to be working fine.
>
> Sorry, it was a cursory test. Actually, cygwin_conv_path is only cal
hi
when launching cygwin's programs from within windows's cmd
if the command line parameter has two backslashes and is double quoted (e.g. a
path to local network drive)
then inside cygwin's program the corresponding ARGV element has single
backslash only
but without double quotes all is ok - b
> Btw., can you please provide the output from
> /usr/lib/csih/getVolInfo /x/wrk
> I never saw the volume information returned by this ext2 driver yet.
~> /usr/lib/csih/getVolInfo.exe /x/wrk
Device Type: 7
Characteristics: 20
Volume Name: <>
Serial Number : 2548180820
Max
On 12/12/2011 1:31 AM, Mike Brown wrote:
On Sun, Dec 11, 2011 at 11:48:01PM -0600, Mike Brown wrote:
Suggestions for document improvement:
FAQ addition to show how to modify the cygwin.bat file, or a copied file for
modification, in order to be able to run rxvt to start a better terminal.
This w
Greetings, Dmitry Bolshakov!
> when launching cygwin's programs from within windows's cmd
> if the command line parameter has two backslashes and is double quoted (e.g.
> a path to local network drive)
> then inside cygwin's program the corresponding ARGV element has single
> backslash only
> bu
On Mon, Dec 12, 2011 at 10:45:12AM -0500, Ken Brown wrote:
> There is no longer a default BAT file, and the Windows console is no longer
> the default terminal. The default terminal is now mintty. The current
> setup.exe creates desktop and start menu shortcuts to start it. This was
> announce
On 12/9/2011 3:35 PM, Corinna Vinschen wrote:
> I have a well-known problem. I just don't have all filesystems
> available for testing. What I need are testers for a certain, very
> simple functionality on any filesystem you can get hold of.
I've got a variety of file systems here.
netapp:
De
On 12/12/2011 11:44 AM, Mike Brown wrote:
snipped doc references...
> In other words, no where in the documentation is it stated that mintty is now
> the default startup. It all leans toward cygwin.bat as being the way things
> are started.
>
> So, just what is a user supposed to think when rea
On 12/12/2011 12:44 PM, Mike Brown wrote:
On Mon, Dec 12, 2011 at 10:45:12AM -0500, Ken Brown wrote:
There is no longer a default BAT file, and the Windows console is no longer
the default terminal. The default terminal is now mintty. The current
setup.exe creates desktop and start menu shortc
On Mon, Dec 12, 2011 at 03:28:39PM -0500, Ken Brown wrote:
> There's nothing to set up. You just click on the start menu shortcut. You
> can then right click in the mintty window and select "Options" if you want
> to change some of the defaults.
In my case that is a no go. That is because, as
On 12/12/2011 03:23 PM, Mike Brown wrote:
> In my case that is a no go. That is because, as mentioned, I told the
> installer not to create the desktop shortcut or the start menu option, as I
> already had them. So, the start menu currently points to the BAT file.
Hmm, it seems that my messages
The attached patches address some of the documentation problems mentioned in
http://cygwin.com/ml/cygwin/2011-12/msg00277.html .
I think the other problems have already been fixed in CVS.
Ken
--- faq-using.xml.orig 2011-12-08 16:42:26.0 -0500
+++ faq-using.xml 2011-12-12 16:40:
Corinna Vinschen writes:
>
> Would it be ok if it works the old way (WIN_A uses the Cygwin codeset)
> for applications built under 1.7.9 and earlier, and the new way (WIN_A
> uses Win32 ANSI/OEM codepage) for applications built under 1.7.10 and
> later? That means the current lyx continues to wor
On 2011-12-12, Jeremy Bopp wrote:
> On 12/12/2011 03:23 PM, Mike Brown wrote:
> > In my case that is a no go. That is because, as mentioned, I told the
> > installer not to create the desktop shortcut or the start menu option, as I
> > already had them. So, the start menu currently points to the
On Mon, Dec 12, 2011 at 04:11:48PM -0800, Gary Johnson wrote:
> General
> [Name:] Cygwin Terminal
> Shortcut
> Target: C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -
> Start in: [empty]
> Shortcut key: None
> Run: Normal window
> [Icon:] C
On Mon, Dec 12, 2011 at 07:37:46PM -0600, Mike Brown wrote:
> Is there a reason why Cygwin is not building a PATH with the needed info?
Not only that, it doesn't start out in the user's home directory.
MB
--
e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII
[I've been to Ear
[Sorry, I again accidentally replied to the OP instead of to the list.]
On 12/12/2011 8:37 PM, Mike Brown wrote:
On Mon, Dec 12, 2011 at 04:11:48PM -0800, Gary Johnson wrote:
General
[Name:] Cygwin Terminal
Shortcut
Target: C:\cygwin\bin\mintty.exe -i /Cygwin-Termina
On 12/12/2011 07:37 PM, Mike Brown wrote:
> On Mon, Dec 12, 2011 at 04:11:48PM -0800, Gary Johnson wrote:
>> General
>> [Name:] Cygwin Terminal
>> Shortcut
>> Target: C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -
>> Start in: [empty]
>> Shortcut key: Non
On Mon, Dec 12, 2011 at 04:57:10PM -0500, Ken Brown wrote:
>The attached patches address some of the documentation problems mentioned in
>
> http://cygwin.com/ml/cygwin/2011-12/msg00277.html .
>
>I think the other problems have already been fixed in CVS.
Patch applied along with a ChangeLog.
Th
On Mon, Dec 12, 2011 at 10:07:23PM -0500, Ken Brown wrote:
> [Sorry, I again accidentally replied to the OP instead of to the list.]
Easy to do the way this mail list is set up.
> Are you sure you didn't forget the `-' at the end of the target? That's
> what tells mintty to start your shell as
On Mon, Jul 25, 2011 at 07:27:23PM +0200, Marco Atzeri wrote:
>On 25/07/2011 19.05, Christopher Faylor wrote:
>
>>
>> "sleeping and waiting for signal" would mean that "bash is not waiting
>> for input". If bash isn't waiting for input that would explain the
>> problem. However, I would expect th
29 matches
Mail list logo
