Am 08.11.2021 um 01:04 schrieb Bryan Higgins:
mintty 3.5.1-1: -p center no longer works. Reverted to 3.5.0, which is fine.:
Yeah, this is already fixed for 3.5.2, to be released in a few days.
(Actually, it didn't work properly in 3.5.0 and before already on
high-DPI monitors.)
--
Pr
mintty 3.5.1-1: -p center no longer works. Reverted to 3.5.0, which is
fine.:
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Mark Geisert writes:
> What I've figured out is that it's not the cygstart code itself that's
> been mis-compiled, it's apparently code pulled in from libcygwin.a as
> cygstart.exe is being built (on my machine before packaging).
…in other words, the compiler used to create that has probably switc
Hi Achim,
Achim Gratz wrote:
Achim Gratz writes:
The Cygwin gcc is configured to use -mtune=generic,
…and -march=x86_64 on 64bit and -march=i686 on 32bit.
While I'd love to switch to x86_64-v2, that would cut off a few
processors that Win7 can be installed on.
Thanks for the tips. Will do
Achim Gratz writes:
> The Cygwin gcc is configured to use -mtune=generic,
…and -march=x86_64 on 64bit and -march=i686 on 32bit.
While I'd love to switch to x86_64-v2, that would cut off a few
processors that Win7 can be installed on.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQ
Mark Geisert writes:
> I compiled the package with gcc 10.2.0 using the default options. Let
> me investigate further to find some kind of solution for the AVX
> usage, likely by using more/different gcc options.
The Cygwin gcc is configured to use -mtune=generic, so if you're ending
up with AVX
On Fri, 13 Aug 2021 20:17:58 -0700
Mark Geisert wrote:
> Brian Inglis wrote:
> > On 2021-08-13 19:54, Takashi Yano via Cygwin wrote:
> >> On Fri, 13 Aug 2021 15:20:40 -0700, Mark Geisert wrote:
> >>> Jay Abel via Cygwin wrote:
> On Fri, Aug 13, 2021 at 10:27 AM Jay Abel wrote:
> >
> Sor
Hi Takashi,
Thanks for that lead. It appears the Makefile.am change didn't make it into the
commit for the getclip update. I'll remedy this shortly.
I compiled the package with gcc 10.2.0 using the default options. Let me
investigate further to find some kind of solution for the AVX usage,
Brian Inglis wrote:
On 2021-08-13 19:54, Takashi Yano via Cygwin wrote:
On Fri, 13 Aug 2021 15:20:40 -0700, Mark Geisert wrote:
Jay Abel via Cygwin wrote:
On Fri, Aug 13, 2021 at 10:27 AM Jay Abel wrote:
Sorry, more information. I'm running Windows 10, 64-bit, AMD.
I've reverted cygutils
On 2021-08-13 19:54, Takashi Yano via Cygwin wrote:
On Fri, 13 Aug 2021 15:20:40 -0700, Mark Geisert wrote:
Jay Abel via Cygwin wrote:
On Fri, Aug 13, 2021 at 10:27 AM Jay Abel wrote:
Sorry, more information. I'm running Windows 10, 64-bit, AMD.
I've reverted cygutils back to 1.4.16-2 and
Hi Mark,
On Fri, 13 Aug 2021 15:20:40 -0700
Mark Geisert wrote:
> Hello Jay,
>
> Jay Abel via Cygwin wrote:
> > Sorry, more information. I'm running Windows 10, 64-bit, AMD.
> >
> > I've reverted cygutils back to 1.4.16-2 and the problem is resolved.
> >
> > Jay
> >
> > On Fri, Aug 13, 2021 a
Hello Jay,
Jay Abel via Cygwin wrote:
Sorry, more information. I'm running Windows 10, 64-bit, AMD.
I've reverted cygutils back to 1.4.16-2 and the problem is resolved.
Jay
On Fri, Aug 13, 2021 at 10:27 AM Jay Abel wrote:
Run cygstart with anything and no window opens. I've tried URLS cy
Sorry, more information. I'm running Windows 10, 64-bit, AMD.
I've reverted cygutils back to 1.4.16-2 and the problem is resolved.
Jay
On Fri, Aug 13, 2021 at 10:27 AM Jay Abel wrote:
> Run cygstart with anything and no window opens. I've tried URLS cygstart
> http://www.cygwin.com, director
Run cygstart with anything and no window opens. I've tried URLS cygstart
http://www.cygwin.com, directories cygstart . and cygstart ./ as well as
pdf files cygstart example.pdf.
None of these seems to do anything anymore.
--
Problem reports: https://cygwin.com/problems.html
FAQ:
Greetings, Kostya Altukhov!
> On Fri, Mar 13, 2020 at 9:14 PM Takashi Yano wrote:
>> Why do you use rlwrap for cmd.exe? History and command line
>> edit are working in cmd without rlwrap in new cygwin.
>>
> cmd.exe is just an example. I use rlwrap for other Windows command line
> tools like Orac
On Fri, Mar 13, 2020 at 9:14 PM Takashi Yano wrote:
> Why do you use rlwrap for cmd.exe? History and command line
> edit are working in cmd without rlwrap in new cygwin.
>
cmd.exe is just an example. I use rlwrap for other Windows command line
tools like Oracle's sqlplus and others. But even in s
On Fri, 13 Mar 2020 19:34:18 +0300
Kostya Altukhov wrote:
> Just try e.g. "rlwrap cmd" from bash and attempt to work in it ->
> completely broken.
> Is this related to the recent pty changes?
> It worked fine earlier.
Why do you use rlwrap for cmd.exe? History and command line
edit are working in
On Fri, Mar 13, 2020 at 8:37 PM Marco Atzeri wrote:
>
> What are you doing ?
> What is the result you are seeing?
> What is the result you were expecting ?
>
Oh, sorry. Here are some cases:
1. Run 'rlwrap cmd'.
Expected result: a prompt with a current directory name and a cursor for
inputting c
Am 13.03.2020 um 17:34 schrieb Kostya Altukhov via Cygwin:
Just try e.g. "rlwrap cmd" from bash and attempt to work in it ->
completely broken.
Is this related to the recent pty changes?
It worked fine earlier.
--
Problem reports: http://cygwin.com/problems.html
Please define what do you
Just try e.g. "rlwrap cmd" from bash and attempt to work in it ->
completely broken.
Is this related to the recent pty changes?
It worked fine earlier.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/do
On 2/28/20 8:21 AM, Brian Inglis wrote:
> Hi folks,
>
> After the recent upgrades to cygwin 3.1.4, perl, etc. I have found that the
> Cygwin-X Startup, Start Menu, and Task Bar shortcuts no longer work, although
> I
> can start Cygwin-X by running startxwin from a mintty window.
>
>>From the sho
Jon Turney writes:
> On 28/02/2020 07:21, Brian Inglis wrote:
>> Hi folks,
>>
>> After the recent upgrades to cygwin 3.1.4, perl, etc. I have found that the
>> Cygwin-X Startup, Start Menu, and Task Bar shortcuts no longer work,
>> although I
>> can start Cygwin-X by running startxwin from a mint
On 28/02/2020 07:21, Brian Inglis wrote:
Hi folks,
After the recent upgrades to cygwin 3.1.4, perl, etc. I have found that the
Cygwin-X Startup, Start Menu, and Task Bar shortcuts no longer work, although I
can start Cygwin-X by running startxwin from a mintty window.
From the shortcut, the sh
Hi folks,
After the recent upgrades to cygwin 3.1.4, perl, etc. I have found that the
Cygwin-X Startup, Start Menu, and Task Bar shortcuts no longer work, although I
can start Cygwin-X by running startxwin from a mintty window.
>From the shortcut, the shell is invoked to run startxwin normally, t
On 2015-07-11 23:13, Thomas Wolff wrote:
> If I only patch the apparently non-working version of mintty to report
> version 1.2 and change nothing else,
> it works! This is obviously a bug in vim, not mintty, and a very silly
> one, because if must be checking the terminal version and enable the
>
Am 11.07.2015 um 23:07 schrieb James Darnley:
On 2015-07-11 22:44, Thomas Wolff wrote:
Am 11.07.2015 um 20:11 schrieb James Darnley:
On 2015-07-11 13:59, Thomas Wolff wrote:
Am 11.07.2015 um 02:52 schrieb James Darnley:
Hi Thomas
Unfortunately I have a complaint to make.
When using the late
On 2015-07-11 22:44, Thomas Wolff wrote:
> Am 11.07.2015 um 20:11 schrieb James Darnley:
>> On 2015-07-11 13:59, Thomas Wolff wrote:
>>> Am 11.07.2015 um 02:52 schrieb James Darnley:
Hi Thomas
Unfortunately I have a complaint to make.
When using the latest Mintty release I
Am 11.07.2015 um 20:11 schrieb James Darnley:
On 2015-07-11 13:59, Thomas Wolff wrote:
Am 11.07.2015 um 02:52 schrieb James Darnley:
Hi Thomas
Unfortunately I have a complaint to make.
When using the latest Mintty release I can no longer use the mouse to
resize split windows in Vim. In 1.1.3
On 2015-07-11 13:59, Thomas Wolff wrote:
> Am 11.07.2015 um 02:52 schrieb James Darnley:
>> Hi Thomas
>>
>> Unfortunately I have a complaint to make.
>>
>> When using the latest Mintty release I can no longer use the mouse to
>> resize split windows in Vim. In 1.1.3, I can drag any window separato
Am 11.07.2015 um 02:52 schrieb James Darnley:
Hi Thomas
Unfortunately I have a complaint to make.
When using the latest Mintty release I can no longer use the mouse to
resize split windows in Vim. In 1.1.3, I can drag any window separator
around to change the size of them. In 2.0.2 Aim appear
Hi Thomas
Unfortunately I have a complaint to make.
When using the latest Mintty release I can no longer use the mouse to
resize split windows in Vim. In 1.1.3, I can drag any window separator
around to change the size of them. In 2.0.2 Aim appears to interpret
the mouse as trying to make a vis
On Thu, 2015-05-07 at 08:16 +0200, Joakim Karlsson wrote:
> After upgrading to Python 3.4.3, some features in Vim stopped working.
> I believe this is because Vim is built against a specific version of
> python3, namely python 3.2.
>
> Vim needs to be rebuilt agains python 3.4.3 for this to work a
Hi,
After upgrading to Python 3.4.3, some features in Vim stopped working.
I believe this is because Vim is built against a specific version of
python3, namely python 3.2.
Vim needs to be rebuilt agains python 3.4.3 for this to work as well.
Vim version information:
:version
VIM - Vi IMproved 7.
Great, thanks!
On Fri, Sep 12, 2014 at 4:14 PM, Matthew Cummings
wrote:
> Hi,
> I'm running 64bit Windows 7, a relatively new OS install. I've been
> using the 64bit version of Cygwin for about a month now on this
> machine, including the emacs that ships with it.
>
> I haven't changed any part
On 9/12/2014 5:53 PM, David Rothenberger wrote:
Ken Brown wrote:
Maybe I should make that the current release; it does seem to be pretty
stable.
I've been running it ever since it came out on x86_64 and have seen a
lot less crashes than with the "official" release. I'd love if this
became curr
Ken Brown wrote:
> Maybe I should make that the current release; it does seem to be pretty
> stable.
I've been running it ever since it came out on x86_64 and have seen a
lot less crashes than with the "official" release. I'd love if this
became curr.
--
David Rothenberger daver...@acm.or
On 9/12/2014 5:14 PM, Matthew Cummings wrote:
Hi,
I'm running 64bit Windows 7, a relatively new OS install. I've been
using the 64bit version of Cygwin for about a month now on this
machine, including the emacs that ships with it.
I haven't changed any part of my cygwin/emacs configuration in t
Hi,
I'm running 64bit Windows 7, a relatively new OS install. I've been
using the 64bit version of Cygwin for about a month now on this
machine, including the emacs that ships with it.
I haven't changed any part of my cygwin/emacs configuration in the
past few weeks but starting today, emacs has
As the subject states, the pidof application no longer works (just hangs).
I have attached the results of cygcheck pidof
P.S.
As a workaround, I have to use the following:
ps -ef | grep -i "${1}" | grep -v "grep" | awk {'print $2'} | head -1
cygcheck_pido
On 10/11/2012 4:34 AM, Josef Wolf wrote:
On Wed, Oct 10, 2012 at 09:02:57AM -0600, Warren Young wrote:
You can probably simplify your fstab like so:
D:/cygwin/bin /usr/bin ntfs binary 0 0
D:/cygwin/lib /usr/lib ntfs binary 0 0
none / cygdrive binary,posix=0,user 0 0
The last lin
On Thu, Oct 11, 2012 at 10:51:53AM -0400, Christopher Faylor wrote:
>On Thu, Oct 11, 2012 at 02:05:31PM +0200, Corinna Vinschen wrote:
>>On Oct 11 07:43, Earnie Boyd wrote:
>>> On Thu, Oct 11, 2012 at 6:34 AM, Josef Wolf wrote:
>>> >>
>>> >> The last line automatically gets rid of the "/cygdrive" p
On Thu, Oct 11, 2012 at 02:05:31PM +0200, Corinna Vinschen wrote:
>On Oct 11 07:43, Earnie Boyd wrote:
>> On Thu, Oct 11, 2012 at 6:34 AM, Josef Wolf wrote:
>> >>
>> >> The last line automatically gets rid of the "/cygdrive" path part,
>> >> so all drive letters appear at the root of the Cygwin pat
On Oct 11 07:43, Earnie Boyd wrote:
> On Thu, Oct 11, 2012 at 6:34 AM, Josef Wolf wrote:
> >>
> >> The last line automatically gets rid of the "/cygdrive" path part,
> >> so all drive letters appear at the root of the Cygwin path tree.
> >
> > I'm not sure I understand this. Should I remove all my
On 10/11/2012 5:07 AM, Josef Wolf wrote:
On Wed, Oct 10, 2012 at 04:55:14PM +0200, marco atzeri wrote:
in this case
cygwin 1.7.16-1 OK
[ ... ]
DLL version: 1.7.15
so if reboot does not work, than Josef you need to re-install the
cygwin-
On Thu, Oct 11, 2012 at 6:34 AM, Josef Wolf wrote:
>>
>> The last line automatically gets rid of the "/cygdrive" path part,
>> so all drive letters appear at the root of the Cygwin path tree.
>
> I'm not sure I understand this. Should I remove all my fstab entries and
> replace with the three lines
On Wed, Oct 10, 2012 at 09:02:57AM -0600, Warren Young wrote:
> What does "which latex" say?
/usr/bin/latex
> Other curious things in your cygcheck output:
>
> >Warning: Mount entries should not have a trailing (back)slash
OK
> You might want to fix that. But also:
>
> >c:\ /c
On Wed, Oct 10, 2012 at 04:55:14PM +0200, marco atzeri wrote:
> in this case
>
> cygwin 1.7.16-1 OK
[ ... ]
> DLL version: 1.7.15
>
> so if reboot does not work, than Josef you need to re-install the
> cygwin- 1.7.16-1 package
Yeah, the ve
On 10/10/2012 8:20 AM, Josef Wolf wrote:
Any hints what might be screwed up here?
What does "which latex" say?
I ask because of:
Warning: D:\cygwin\bin\tar.exe hides C:\Program
Files\CatPC\Windows\System32\tar.ex
That leads me to believe you might have some rogue *ix like programs
runni
On 10/10/2012 4:47 PM, Larry Hall (Cygwin) wrote:
On 10/10/2012 10:20 AM, Josef Wolf wrote:
Hello,
yesterday, I did an update of cygwin with setup.exe and now latex stopped
working at all. It just silently doesn't do anything at all, no matter
what
type of input or options I give it. Not even "
On 10/10/2012 10:20 AM, Josef Wolf wrote:
Hello,
yesterday, I did an update of cygwin with setup.exe and now latex stopped
working at all. It just silently doesn't do anything at all, no matter what
type of input or options I give it. Not even "latex --version" gives me any
output anymore.
I fo
I don't think cygcheck can resolve a symlink.
(I'm not near a Windows machine to test right now)
For the archives, yes, it can.
I don't have emacs on my machine (vi is the one true editor) but the
only difference between the two invocation methods is that if you pass a
symlink, cygcheck emit
On 4/19/2011 6:57 AM, Ken Brown said this:
> On 4/18/2011 5:44 PM, Tim Daneliuk wrote:
>> On 4/18/2011 3:27 PM, Ken Brown wrote:
>>> On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
> This has happened the last few times I did an upgrade with
On 4/18/2011 5:44 PM, Tim Daneliuk wrote:
On 4/18/2011 3:27 PM, Ken Brown wrote:
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start
On 4/18/2011 3:27 PM, Ken Brown wrote:
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
fine.
Previously, I w
On Mon, Apr 18, 2011 at 04:36:09PM -0400, Ken Brown wrote:
>On 4/18/2011 4:30 PM, Christopher Faylor wrote:
>> On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
>>> On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
> This has happened
On 4/18/2011 4:30 PM, Christopher Faylor wrote:
On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, an
On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
>On 4/18/2011 4:02 PM, marco atzeri wrote:
>> On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
>>> This has happened the last few times I did an upgrade with setup.exe.
>>> emacs, emacs-nox, and emacs -nw will not start at all. Xemac
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
fine.
Previously, I was able to work around this by falling
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
> This has happened the last few times I did an upgrade with setup.exe.
> emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
> fine.
>
> Previously, I was able to work around this by falling back to a
> previous version of ema
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
fine.
Previously, I was able to work around this by falling back to a
previous version of emacs, but this too seems broken now.
Ideas?
--
--
On Thu, Feb 25, 2010 at 09:14:15AM +0100, Matthias Andree wrote:
> Jason, would you include this EXITCODE/HOST stuff and other hints into
> your Cygwin README file? I don't think the upstream version will ever
> change again, procmail is apparently dead for nearly a decade. For
> debugging, I'd als
On Wed, Feb 24, 2010 at 06:04:05PM -0500, Thomas Baker wrote:
> >> Are you configured for case sensitive filenames? What does the
> >> following indicate?
> >>
> >> $ regtool get '\HKLM\SYSTEM\CurrentControlSet\Control\Session
> >> Manager\kernel\obcaseinsensitive'
> >
> > I am on the road tod
Am 25.02.2010 00:04, schrieb Thomas Baker:
>>> Are you configured for case sensitive filenames? What does the
>>> following indicate?
>>>
>>>$ regtool get '\HKLM\SYSTEM\CurrentControlSet\Control\Session
>>> Manager\kernel\obcaseinsensitive'
>>
>> I am on the road today with the netbook, and o
>> Are you configured for case sensitive filenames? What does the
>> following indicate?
>>
>> $ regtool get '\HKLM\SYSTEM\CurrentControlSet\Control\Session
>> Manager\kernel\obcaseinsensitive'
>
> I am on the road today with the netbook, and on the netbook the command
> above yields a respons
>> $ cd /home
>> $ ls
>> Administrator TBaker tbaker
>
> How did you manage to create two subdirectories (i.e., TBaker and
> tbaker) in the same parent directory that only differ by case?
>
> Are you configured for case sensitive filenames? What does the
> following indicate?
>
>
Tom,
I know your problem was resolved later in the thread, but I'm curious...
On Tue, Feb 23, 2010 at 03:20:46PM -0500, Thomas Baker wrote:
> This is what I find...:
>
> $ cd /home
> $ ls
> Administrator TBaker tbaker
How did you manage to create two subdirectories (i.e., TBak
On Tue, Feb 23, 2010 at 4:44 PM, Larry Hall (Cygwin)
wrote:
>>> Evidently if it does not find /home/TBaker/.procmailrc, it does
>>> not go looking for /home/tbaker/.procmailrc. Since my entire
>>> file system is based on tbaker, I'd love to find a way to eradicate
>>> the "TBaker" from my system
On 02/23/2010 03:37 PM, Thomas Baker wrote:
Evidently if it does not find /home/TBaker/.procmailrc, it does
not go looking for /home/tbaker/.procmailrc. Since my entire
file system is based on tbaker, I'd love to find a way to eradicate
the "TBaker" from my system entirely. The guy who set up m
> Evidently if it does not find /home/TBaker/.procmailrc, it does
> not go looking for /home/tbaker/.procmailrc. Since my entire
> file system is based on tbaker, I'd love to find a way to eradicate
> the "TBaker" from my system entirely. The guy who set up my XP
> installation many years ago set
On Tue, Feb 23, 2010 at 2:35 PM, Jason Tishler wrote:
>> > What does the following indicate?
>> >
>> > ?? ??$ procmail VERBOSE=on >
>> procmail: [4092] Tue Feb 23 14:11:50 2010
>> procmail: Locking "/var/spool/mail/TBaker.lock"
>> [snip]
>
> You should have seen a line like the following:
>
> pr
Tom,
On Tue, Feb 23, 2010 at 02:14:00PM -0500, Thomas Baker wrote:
> On Tue, Feb 23, 2010 at 1:28 PM, Jason wrote:
> >> Can you be a bit more specific? Is anything added to the procmail
> >> log? You could also add VERBOSE=on on the command line for more
> >> info.
> >
> > What does the following
On Tue, Feb 23, 2010 at 1:28 PM, Jason wrote:
>> Can you be a bit more specific? Is anything added to the procmail log?
>> You could also add VERBOSE=on on the command line for more info.
>
> What does the following indicate?
>
> $ procmail VERBOSE=on http://cygwin.com/problems.html
FAQ:
>> And you're sure you are running the correct procmail, i.e. there is no
>> other procmail in your path before the one you are expecting to run?
>> $ type -a procmail
>> procmail is /usr/bin/procmail
>> procmail is /bin/procmail
Yes, though the result repeats itself as follows:
$ type -a
On Tue, Feb 23, 2010 at 11:49 AM, Gary wrote:
>> If I pipe one message into procmail with:
>>
>> procmail -v -d tbaker >
>> procmail reports:
>>
>> Locking strategies: dotlocking, fcntl()
>> Default rcfile: $HOME/.procmailrc
>> Your system mailbox: /var/spool/
Tom,
On Tue, Feb 23, 2010 at 05:49:27PM +0100, Gary wrote:
> On Tue, Feb 23, 2010 at 10:33:24AM -0500, Thomas Baker wrote:
> > This also does not work:
> >
> > procmail -d tbaker
> Can you be a bit more specific? Is anything added to the procmail log?
> You could also add VERBOSE=on on the
On Tue, Feb 23, 2010 at 11:25 AM, Eric wrote:
> According to Thomas Baker on 2/23/2010 9:06 AM:
>> On the netbook the permissions for /usr/bin/procmail start with:
>>
>> -rwxr-x---+
>
> The trailing + tells you that there are ACLs attached to the file that may
> further impact who can access
On Tue, Feb 23, 2010 at 10:33:24AM -0500, Thomas Baker wrote:
> If I pipe one message into procmail with:
>
> procmail -v -d tbaker
> procmail reports:
>
> Locking strategies: dotlocking, fcntl()
> Default rcfile: $HOME/.procmailrc
> Your system mailbox:
According to Thomas Baker on 2/23/2010 9:06 AM:
> On the netbook the permissions for /usr/bin/procmail start with:
>
> -rwxr-x---+
The trailing + tells you that there are ACLs attached to the file that may
further impact who can access the file. getfacl can show you those
additional
On Tue, Feb 23, 2010 at 10:33 AM, Thomas Baker wrote:
> This also does not work:
>
> procmail -d tbaker
> However, on the netbook
>
> procmail -d tbaker
> works fine, delivering the message where it is supposed to go.
On the netbook the permissions for /usr/bin/procmail start with
On Tue, Feb 23, 2010 at 8:13 AM, Jason wrote:
>> > http://cygwin.com/acronyms#PPIOSPE
>>
>> My apologies if I overlooked that - I'm temporarily working in
>> googlemail because of this procmail situation and feel out of my usual
>> element (mutt).
>
> Unfortunately, you are still overlooking th
Tom,
On Mon, Feb 22, 2010 at 10:48:14PM -0500, Thomas Baker wrote:
> Jason,
>
> On Mon, Feb 22, 2010 at 9:17 PM, Jason Tishler wrote:
> > Please note the following:
> >
> > http://cygwin.com/acronyms#PPIOSPE
>
> My apologies if I overlooked that - I'm temporarily working in
> googlemail bec
On Mon, Feb 22, 2010 at 10:34:42PM +0100, Matthias Andree wrote:
http://cygwin.com/acronyms/#PCYMTNQREAIYR
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwi
Jason,
On Mon, Feb 22, 2010 at 9:17 PM, Jason Tishler wrote:
> Please note the following:
>
> http://cygwin.com/acronyms#PPIOSPE
My apologies if I overlooked that - I'm temporarily working in googlemail
because of this procmail situation and feel out of my usual element (mutt).
>> Ah, how in
Tom,
Please note the following:
http://cygwin.com/acronyms#PPIOSPE
On Mon, Feb 22, 2010 at 05:52:34PM -0500, Thomas Baker wrote:
> On Mon, Feb 22, 2010 at 5:02 PM, Jason Tishler wrote:
> > On Mon, Feb 22, 2010 at 09:12:00AM -0500, Thomas Baker wrote:
> >> The problem is that since the upgrad
On Mon, Feb 22, 2010 at 5:02 PM, Jason Tishler wrote:
> On Mon, Feb 22, 2010 at 09:12:00AM -0500, Thomas Baker wrote:
>> The problem is that since the upgrade to Cygwin 1.7, the fetchmail
>> on my _desktop_ computer no longer passes the incoming messages to the
>> MDA procmail. Each incoming mess
Thomas,
On Mon, Feb 22, 2010 at 09:12:00AM -0500, Thomas Baker wrote:
> The problem is that since the upgrade to Cygwin 1.7, the fetchmail
> on my _desktop_ computer no longer passes the incoming messages to the
> MDA procmail. Each incoming message, retrieved with POP3, is saved
> undelivered as
Am 22.02.2010, 19:39 Uhr, schrieb Gary :
On Mon, Feb 22, 2010 at 06:53:46PM +0100, Matthias Andree wrote:
Am 22.02.2010 17:25, schrieb Thomas Baker:
and (b) you're either running an old fetchmail
version
No, the version numbers Tom provided are current (or thereabouts).
6.3.9 may be the
On Mon, Feb 22, 2010 at 06:53:46PM +0100, Matthias Andree wrote:
> Am 22.02.2010 17:25, schrieb Thomas Baker:
> and (b) you're either running an old fetchmail
> version
No, the version numbers Tom provided are current (or thereabouts).
--
Problem reports: http://cygwin.com/problems.html
FA
Am 22.02.2010 17:25, schrieb Thomas Baker:
> On Mon, Feb 22, 2010 at 11:41 PM, Gary wrote:
>> What does the fetchmail log say? "fetchmail: MDA open failed"?
>
> The fetchmail simply reports that each message is "flushed". The log
> entries in this regard are identical on both machines. The lo
Apologies for repeating my message - the Cygwin list would only let me sign
up using my googlemail account - then googlemail caught your response in a
delete filter :-(
On Mon, Feb 22, 2010 at 11:41 PM, Gary wrote:
> On Mon, Feb 22, 2010 at 09:12:00AM -0500, Thomas Baker wrote:
>
>> The problem i
On Mon, Feb 22, 2010 at 09:12:00AM -0500, Thomas Baker wrote:
> The problem is that since the upgrade to Cygwin 1.7, the fetchmail
> on my _desktop_ computer no longer passes the incoming messages to the
> MDA procmail. Each incoming message, retrieved with POP3, is saved
> undelivered as an indi
Dear all,
I recently upgraded to cygwin 1.7.1-1 on two computers:
-- an ASUS netbook running Windows XP (German edition)
-- a Fujitsu-Siemens desktop running Windows XP (English)
The software on the C: partitions of the two computers
has been installed separately (including c:/cygwin and c:/cygw
On Fri, 29 Oct 2004, Alex Vinokur wrote:
> "Igor Pechtchanski" wrote:
> > On Thu, 28 Oct 2004, Alex Vinokur wrote:
> [snip]
> > > It seems that I got rid of problem "bash: kpsexpand: command not found".
> >
> > Great. So it was simply a missing dependency problem.
>
> I don't understand how the p
"Igor Pechtchanski" wrote in message news:[EMAIL PROTECTED]
> On Thu, 28 Oct 2004, Alex Vinokur wrote:
[snip]
> > It seems that I got rid of problem "bash: kpsexpand: command not found".
>
> Great. So it was simply a missing dependency problem.
I don't understand how the problem has been resolve
On Thu, 28 Oct 2004, Alex Vinokur wrote:
> "Igor Pechtchanski" wrote:
> > On Tue, 26 Oct 2004, Alex Vinokur wrote:
> >
> > > "Igor Pechtchanski" wrote:
> > >
> > > > I have a feeling your postinstall scripts didn't run properly because
> > > > of the screwed-up mounts. In fact, run
> > > >
> > > >
I nuked and restored the Windows disk from partimage saves (attempting to
correct a problem unrelated to Cygwin). Partimage is a bit too finicky about
the size of the destination partition, test full size and aborts even if the
"used data" fill fit! As I was unable to recreate the partition I ha
"Igor Pechtchanski" wrote in message news:[EMAIL PROTECTED]
> On Tue, 26 Oct 2004, Alex Vinokur wrote:
>
> > "Igor Pechtchanski" wrote:
> >
> > > I have a feeling your postinstall scripts didn't run properly because
> > > of the screwed-up mounts. In fact, run
> > >
> > > find /etc/postinstall -na
On Tue, 26 Oct 2004, Alex Vinokur wrote:
> "Igor Pechtchanski" wrote:
> [snip]
> > Please select "Reinstall" for all of the packages in your zzz3.txt file.
> [snip]
>
> "Select Packages" has the following actions:
> * Keep
> * Retrieve
> * Source
> * Uninstall
>
> I didn't find "Reinstall".
Dave
"Igor Pechtchanski" wrote in message news:[EMAIL PROTECTED]
[snip]
> Please select "Reinstall" for all of the packages in your zzz3.txt file.
[snip]
"Select Packages" has the following actions:
* Keep
* Retrieve
* Source
* Uninstall
I didn't find "Reinstall".
--
Alex Vinokur
email: alex
On Tue, 26 Oct 2004, Alex Vinokur wrote:
> "Igor Pechtchanski" wrote:
>
> > I have a feeling your postinstall scripts didn't run properly because
> > of the screwed-up mounts. In fact, run
> >
> > find /etc/postinstall -name \*.done | sed 's/\.done$//' | xargs cygcheck -f | uniq
>
> $ find /etc/po
1 - 100 of 122 matches
Mail list logo
