[RFU] libogg-1.1.4-1
Please leave 1.1.3-1 and remove all previous versions. Thanks! wget -x -nH --cut-dirs=2 \ http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg-1.1.4-1-src.tar.bz2 \ http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg-1.1.4-1.tar.bz2 \ http://mysite.verizon.net/res00a7j/cygwin/libogg/setup.hint \ http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg-devel/libogg-devel-1.1.4-1.tar.bz2 \ http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg-devel/setup.hint \ http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg0/libogg0-1.1.4-1.tar.bz2 \ http://mysite.verizon.net/res00a7j/cygwin/libogg/libogg0/setup.hint \ -- David Rothenberger daver...@acm.org Cutler Webster's Law: There are two sides to every argument, unless a person is personally involved, in which case there is only one.
Re: [RFU] libogg-1.1.4-1
On 12/01/2010 13:23, David Rothenberger wrote: Please leave 1.1.3-1 and remove all previous versions. Thanks! Uploaded; there were no pre-1.1.3 versions to remove. Thanks, Yaakov
moving cogito to obsolete?
Any objections to me moving cogito to obsolete, as it has been several years since upstream declared it unmaintained, and since it no longer works well with modern git? Or should we quit providing it altogether? -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net signature.asc Description: OpenPGP digital signature
Re: moving cogito to obsolete?
On 12/01/2010 21:58, Eric Blake wrote: Any objections to me moving cogito to obsolete, as it has been several years since upstream declared it unmaintained, and since it no longer works well with modern git? Or should we quit providing it altogether? As a program, nothing requires: it, so if it's dead, I say just remove it and send a cygwin-announce to that effect. My 0.02 CAD, Yaakov
Re: moving cogito to obsolete?
According to Yaakov (Cygwin/X) on 1/12/2010 9:12 PM: On 12/01/2010 21:58, Eric Blake wrote: Any objections to me moving cogito to obsolete, as it has been several years since upstream declared it unmaintained, and since it no longer works well with modern git? Or should we quit providing it altogether? As a program, nothing requires: it, so if it's dead, I say just remove it and send a cygwin-announce to that effect. Done. Should I update the package-maintainer mapping list? (If so, where is it stored?) -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net signature.asc Description: OpenPGP digital signature
[ANNOUNCEMENT] New: libgsf-1.14.16-1
The following packages have been added to the Cygwin distribution: * libgsf-1.14.16-1 * libgsf1-devel-1.14.16-1 * libgsf1_114-1.14.16-1 * python-gsf-1.14.16-1 libgsf is a GNOME library which provides I/O abstraction for a variety of structured file formats, such as compressed archives and office document formats. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO == If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
[ANNOUNCEMENT] New: librsvg2-2.26.0-2
The following packages have been added to the Cygwin distribution: * gdk-pixbuf2.0-svg-2.26.0-2 * gtk2.0-engines-svg-2.26.0-2 * librsvg2-devel-2.26.0-2 * librsvg2_2-2.26.0-2 * rsvg-2.26.0-2 libRSVG is a very fast SVG rendering engine written in C. It currently support most of the SVG 1.2 specification, except the animation part. libRSVG is used in many projects for SVG rendering, most notably GNOME. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO == If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Questions regarding windows 7 installation
thanks Jason, I have already done that, but even after commenting out the exec xterm and running the xterm process from the drop down menu I get two X windows. One that starts and stays blank and then the actual Xterm window which has a white background. I don't mind running the Xterm automatically, it's the spurious cygwin windows that start and stay up. Just clutters up the desktop and you can't tell which is the usable Xterm. DePriest, Jason R. wrote: On Mon, Jan 11, 2010 at 6:32 PM, Jerry Lowry wrote: I have installed Cygwin 1.7 twice on my windows 7 laptop. Each time it installs fine but when I try to run the X server it leaves three different X windows open as well as an Xterm itself. Is this the default behavior on 1.7? I really would like to get just the X icon in the task bar and nothing else until I start an Xterm. But even the Xterm opens two windows. Anyone have any ideas as to the problem I am seeing? -- Try modifying your /etc/X11/xinit/xinitrc file I commented out the last line which had an 'exec xterm' in it and the xterm no longer runs automatically. -Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
bug report/suggested temp. patch: handling bursts of sent keys
Background:
I use Nuance's Dragon NaturallySpeaking voice recognition software
to control remote Linux systems from a Windows box. I open up xterms
and emacs windows on a local Cygwin X server. Occasionally the voice
recognizer makes a mistake, which has to be corrected. The mechanics of
how this is done are unimportant; what matters is how Dragon applies the
correction. It does this by sending a large burst of keystrokes via
something like SendKeys. (E.g., many (shift) arrow keys to select the
text to be changed, a backspace to delete it, then the replacement
text.)
Unfortunately, there is a bug in the current released Cygwin X
server that causes it to drop sent keystrokes when the burst exceeds a
given size (roughly 64 or 128 keys depending on the version). This
breaks correction, and forces painful manual fix up of the text. Note
that what is really dropped are key events so the system can get into
the state where the shift key remains pressed or a key starts repeating
forever because the key up event was dropped.
Problem/temporary patch:
I investigated and found that the problem appears to be that the X
event queue (miEventQueue) in hw/mi/mieq.c is statically allocated with
a ridiculously small value (512). When keyboard bursts come in, this
queue overflows, causing the problem. If I set this queue to a more
reasonable value of 5120:
mieq.c:62:#define QUEUE_SIZE 5120/* was 512 */
then 10 times larger key bursts can be accommodated without problem.
This value is probably still too small in practice so it would be safer
to go with a larger value like 25000.
I characterize this as a temporary patch because ideally either the
queue would be made dynamic with no upper bound in size, or some kind of
flow control would be implemented so the code that receives Windows key
events does not overflow the event queue.
Reproducing the problem:
Dragon NaturallySpeaking costs money, so I will instead describe how
to demonstrate the problem using AutoHotkey, which is a free download
from http://www.autohotkey.com/. Download that program then create and
run the following script, burst.ahk:
cut here for burst.ahk
#space::
Send ** ** ** **
**{enter}** ** ** **
**{enter}** ** ** **
**{enter}** ** ** **
**{enter}** ** ** ** **{enter}
=
Finally, type the Windows key and space together while focus is on an X
application. The bug is not present, the following will be typed:
** ** ** ** **
** ** ** ** **
** ** ** ** **
** ** ** ** **
** ** ** ** **
On the other hand, if the bug is present you'll get something more like:
** ** ** ** **
** ** ** ** **
***
- Mark
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: XWin Server Not Starting
I too had the same problem and I looked through some of the other posts. Simon Jean-Francois posted the solution and Andy Koppe posted a followup. Just as Andy has suggested, I got a in-use message box because I had a bash shell running. http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00098.html http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00099.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
try to startx
Dear cygwin x programer: I try the suggestion of mailing list to fix startx problem, - /bin/sh disappeared: this was fixed with ln -s /bin/bash /bin/sh Another problem related to fonts was fixed by mkfontdir --- but it still not work, and I try to reinstall bash at base category then retry above my startx still not work please help, Eric -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: XWin Server Not Starting
Well I figured that I would start over. So, I downloaded the cygwin files again to a local disk. Installed everything from the local disk. I found that this time the install did not put any programs in the Cyginw-X folder at all. So I deleted the cygwin download and picked a different mirror site. I found that the number of folders got bigger and this time when I installed, the Cygwin-X folder is populated. ( The first site I used was OSU, anyway to ping them to have them upgrade the mirror with all of the folders?) After the install I started the X server. Worked okay, except that when the xterm started it still leaves a blank X windows hanging around. Have yet to investigate this, just finished the install. I then started the cygwin dos window and it returned this error: 1 [main] bash 3660 C:\Xwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x85, top 0x8B, reserve_size 389120, allocsize 393216, page_const 4096 2 [main] bash 2848 child_info::sync: wait failed, pid 3660, Win32 error 1812 1861 [main] bash 2848 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 2 [main] bash 2584 C:\Xwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x85, top 0x8B, reserve_size 389120, allocsize 393216, page_const 4096 301671318 [main] bash 2848 child_info::sync: wait failed, pid 2584, Win32 error 1812 301672949 [main] bash 2848 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 I killed the windows after these errors. I was hoping to check see if 'sh' was installed, but will look at the xterm instead. Started the Xterm and got the following error: /usr/bin/xterm: Could not exec /bin/bash: Bad address looks like bash needs to be reinstalled or fixed. Will do the reinstall and report back. thanks Bob Whitehurst wrote: I too had the same problem and I looked through some of the other posts. Simon Jean-Francois posted the solution and Andy Koppe posted a followup. Just as Andy has suggested, I got a in-use message box because I had a bash shell running. http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00098.html http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00099.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: try to startx
On 12/01/2010 15:53, eric lin wrote: Dear cygwin x programer: I try the suggestion of mailing list to fix startx problem, For the *third* time, when you provide us with ALL of the information EXACTLY as detailed here, then we may be able to help you: Problem reports: http://cygwin.com/problems.html Until then, please stop wasting both your time and ours. Yaakov Cygwin/X -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
BitDefender prevents installation and execution of Cygwin and Cygwin-x
After upgrading to WinXP last month (I don't like to rush in to things) cygwin, cygwin-x, and NX-Client ceased to function. (To make a long story short, I had changed to BitDefender at the same time, but had forgotten that). I blamed the problem on the OS upgrade, not realizing that the problem was with the AV software. I tried everything I could think of, to the point where I deleted all files associated with both cygwin and NX, then searched the registry and deleted all references to Cygnus, cygwin and nx-client, all to no avail. I then re-installed only cygwin (the default minimum) but got the same symptoms: Error messages in the /etc/postinstall script processes which translated to 0xC00D (access violation) occurred on each an every entry in the script. I finally found a web entry that suggested that this error could be caused by AV software (although it did not mention BitDefender by name). In desperation, I erased all cygwin files yet again, put BD in GAME mode, and re-installed the default cygwin. The install was successful so I added cygwin-x which also installed and ran successfully. I thought I'd push my luck so I also installed NX-client. It worked as well! Since I didn't like to leave my systems in Game (very permissive) mode, I switched BD back to its normal operating mode. All the cygwin stuff stopped working. Back to Game mode. Everything works. Sent nasty-gram to BitDefender (not really nasty, but let them know of the problem and asked for solution). I had the same problem on machines running Vista and Win7 (which also recovered in BD Game mode) so I think the problem is wide-spread. I'm posting this in the hope that it helps others who may be beating their heads against the wall. Don Ziesig -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Can't start xterm from Cygwin/X icon in system tray
After re-installing Cygwin from scratch, I have determined that this environment variable is/was causing the problem: CYGWIN=tty Once I removed it, I was able to create an X term from the icon in the system tray. - Jim On Wed, Dec 30, 2009 at 10:07 AM, I wrote: I have a very strange situation. At work, I am running Win XP SP3. I installed all the latest Cygwin (1.7.1) + Xorg updates, including startxwin.exe. Everything works perfectly. At home, I am running Windows 7 Professional, 64-bit. I am unable to start an xterm from the Cygwin/X icon in the system tray (right-click, select xterm). Both setups have the same line in .XWinrc: xterm EXEC xterm I am starting the X server the same way: D:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe I do not have a ~/.startxwinrc file. The xterm that is supposed to be created when the server starts doesn't start either. The symptom is that xterm.exe is shown running in the task manager, but there is no Xterm window on the desktop. As a work-around, I created a shortcut on my desktop to start an xterm: D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0 That works perfectly, but is not an optimum solution (I try to have as few desktop icons as possible). There is nothing in the /var/log/Xwin log that indicates why an xterm would start but not open a window. Any ideas? -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
src/winsup/cygwin ChangeLog dir.cc dtable.cc d ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-01-12 10:15:00 Modified files: winsup/cygwin : ChangeLog dir.cc dtable.cc dtable.h ntea.cc path.cc path.h sec_acl.cc syscalls.cc times.cc Log message: * dtable.cc (build_fh_name_worker): Remove. Move all functionality back into build_fh_name. (build_fh_name): Drop unused HANDLE parameter. Drop call to pc.fillin. Remove disabled build_fh_name with UNICODE_STRING name parameter. * dtable.h (build_fh_name): Drop HANDLE parameter from declaration. Remove declaration for build_fh_name with UNICODE_STRING name parameter. * path.cc (path_conv::fillin): Remove. (symlink_info::check): Fix comment. * path.h (path_conv::fillin): Remove declaration. * dir.cc: Accommodate change in build_fh_name parameters throughout. * sec_acl.cc: Ditto. * syscalls.cc: Ditto. * ntea.cc (getxattr_worker): Fix debug output. (setxattr_worker): Ditto. * times.cc (utimens_worker): Ditto. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4761r2=1.4762 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dir.cc.diff?cvsroot=srcr1=1.124r2=1.125 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dtable.cc.diff?cvsroot=srcr1=1.210r2=1.211 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dtable.h.diff?cvsroot=srcr1=1.50r2=1.51 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ntea.cc.diff?cvsroot=srcr1=1.22r2=1.23 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.cc.diff?cvsroot=srcr1=1.575r2=1.576 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.h.diff?cvsroot=srcr1=1.136r2=1.137 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/sec_acl.cc.diff?cvsroot=srcr1=1.57r2=1.58 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/syscalls.cc.diff?cvsroot=srcr1=1.549r2=1.550 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/times.cc.diff?cvsroot=srcr1=1.99r2=1.100
src/winsup/cygwin ChangeLog fhandler_disk_file ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-01-12 14:47:46 Modified files: winsup/cygwin : ChangeLog fhandler_disk_file.cc globals.cc mount.cc mount.h path.cc path.h Log message: * globals.cc (ro_u_nwfs): New R/O unicode string. * mount.cc (fs_info::update): Check for NWFS filesystem. Set has_buggy_basic_info, if so. Add comment to explain why. (fillout_mntent): Add nwfs string to fs_names array. * mount.h (enum fs_info_type): Add nwfs. (class fs_info): Add has_buggy_basic_info status flag. Add accessors for has_buggy_basic_info and is_nwfs. * fhandler_disk_file.cc (fhandler_base::fstat_by_handle): Accommodate filesystems with broken FileBasicInformation handling. * path.cc (symlink_info::check): Ditto. * path.h (path_conv::has_buggy_basic_info): Add method. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4762r2=1.4763 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_disk_file.cc.diff?cvsroot=srcr1=1.319r2=1.320 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/globals.cc.diff?cvsroot=srcr1=1.15r2=1.16 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/mount.cc.diff?cvsroot=srcr1=1.52r2=1.53 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/mount.h.diff?cvsroot=srcr1=1.10r2=1.11 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.cc.diff?cvsroot=srcr1=1.576r2=1.577 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.h.diff?cvsroot=srcr1=1.137r2=1.138
Re: Redirecting $TEMP or a certain directory to /tmp
* Thomas Wiedmann (Tue, 12 Jan 2010 08:24:57 +0100) how can in Cygwin the directory, which is in Windows configured as $TEMP, or a certain other directory, be redirected to /tmp? man mount -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
cppunit: rebuild for gcc4
Ross, Could you please build the lateset cppunit with gcc4? The last release was built with gcc3 and does not work with a gcc4-compiled package. Thanks, Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
units: update, FHS compliance
Jari, Could you please update your units package, at the same time fixing the location of the data file to be FHS compliant by passing --datadir=/usr/share/units/ (including the trailing slash) to configure? Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
ACEs for system - sysprep
Hello, there are no ACEs for SYSTEM in / and below. This causes that during the cloning process (using Sysprep) after minisetup changes computer SID and corrects the old one in NTFS ACLs this correction is not performed in cygwin directories. Is my reasoning correct and if so should't cygwin Setup add rights for SYSTEM? With greetings Pavel Kudrna -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Redirecting $TEMP or a certain directory to /tmp
Thorsten Kampe wrote:
Thomas Wiedmann (Tue, 12 Jan 2010 08:24:57 +0100) wrote
how can in Cygwin the directory, which is in Windows configured as
$TEMP, or
a certain other directory, be redirected to /tmp?
man mount
My approach is different, I solve the problem on the Windows side for all
apps, Cygwin, or Windows.
My system is Visa 64b; others use a slightly different menu
sequence, but:
Control Panel - System - Advanced system settings -
Environment Variables - System Variables -
TEMP == %TMPDIR%
and ...-
TMPDIR == c:\_0\tmp
and (because some pseudo *nix apps for Windows use $TMP, instead of $TMPDIR:
...-
TMP == %TMPDIR%
(since Cygwin root on my system is at 'c:\_0')
My approach means that both Windows and Cygwin apps use the same
directory for temporary files. This means I only have to clean up
or search in one temporary directory.
I also use the attached script, 'tmpdir', when I'm using the temporary
directory with unknown *NIX configs.
It has it's own help (-h|--help).
As always, YMMV.
#!/bin/bash
# tmpdir: resilient TeMPorary Directory Inquisition Reporter
# 'tmpdir' finds a master temporary directory (MTD) -- the directory in
# which temporary files and directories of an appication's session are
# stored. With certain options, it will create the directory.
# By Lee Rothstein, 2009-02-07 11:56
ProgName=tmpdir
Version=0.4.0
UpDate=2009-05-10
HelpEm () {
less !!!EOF!!!
NAME
tmpdir - *resilient* TeMPorary Directory Intantiator/Reporter
DESCRIPTION
'tmpdir' finds a master temporary directory (MTD) -- the
directory in which temporary files and directories of an
application's session are stored. With certain options it will
create (recursively, i.e., 'mkdir - p') the directory.
In most GNU, UNIX, BSD, Linux, Cygwin and Posix systems, the
MTD is either /tmp, or the directory referenced by $TMPDIR. In
Cygwin, a likely additional possibility is the directory
referenced by $TEMP.
Normally, 'tmpdir' will be used by another script. Practical
uses for this utility include:
* If you're writing scripts for unknown users and are unsure of
their environment, 'tmpdir' might be one element of a
foolproof approach. Alas, however, fools are such clever
creatures; witness, George W. Bush (or, at least, George W.
Bush with Karl Rove's help).
* Creating a more private MTD for a specific application or
session.
SYNOPSIS
tmpdir -h
tmpdir [ [-c] [-f TEMPDIRECTORY] [-l TEMPDIRECTORY] ]
OPTIONS
Each option is mutually exclusive of the others. (That is,
only one can be used per invocation of 'tmpdir'.) Every option
besides '-h' requires TEMPDIRECTORY. Any option must be
specified before a TEMPDIRECTORY is provided.
-h | --help -- Help -- Provide this help. Take no other
actions. Exit code = '99'. 'tmpdir' does not use nor
check for any other arguments, when '-h', or '--help' is
specified.
Note: no other long option names are supported.
-c -- Create a specified temporary directory. Abort if
directory already exists.
-f -- Force -- Force the use of the specified directory
whether or not it pre-exists. (This option will not
delete a file that prevents the creation of a directory
by the same name. Ergo, even The Force is limited in
its power ;-) )
-l -- Last resort -- Go through the normal sequence of
temporary directory investigation. If none is found,
try TEMPDIRECTORY, if it doesn't exist create it
(recursively, i.e., 'mkdir -p').
With the exception of help, long option syntax is not
supported!
USAGE
Rules:
* Almost any name acceptable to the file system is acceptable
as TEMPDIRECTORY, except one beginning with a dash. This is
done for four reasons:
It makes option sanity checking easier.
The user is very likely making a mistake about options
usage.
It's very bad form. MTDs beginning with '-' would likely
cause problems later when 'tmpdir' was used in a script.
If you don't like it, you can always change it, it's just
a script.
* Success is finding or creating an MTD -- return value == 0.
* Whenever it succeeds, and returns '0', it 'stdouts' the name
of that directory.
* Failure for any operational reason returns '1'. 'stdout' is
null. Failure means there is not a temporary directory, of
any kind, to be found.
The help option exits with a return code of '99'. Errors
in command line specification also return 90 series numbers.
Help is directed to 'stdout' piped through 'less'.
* Error messages are limited in size and always directed to
'stderr'.
* Directories are only created if one of the options is used.
* '-c' will create a directory (recursively, i.e., 'mkdir -p')
if one
Re: Cygwin upgrade
On 1/11/2010 3:58 PM, Larry Hall (Cygwin) wrote: On 01/11/2010 03:46 PM, Tod wrote: I'm upgrading to 1.7.1 from the previous version which I was pretty good at keeping up to date. I ran into a problem installing openssh which locked the install forcing me to cancel. I stopped the openssh service and cygwin service and tried again. It completed with me ok'ing past pointer errors on certain packages from the previous install attempt. I restarted and now get the message: The procedure entry point __ctype_ptr__ could not be located in the dynamic link library cygwin1.dll. I'm running XP service pack 2. I haven't rebooted the box yet so maybe that has something to do with it? The thought was that reboot in Cygwin terms was restarting Cygwin. I'll try the box now and report back tomorrow. Not when you're dealing with an in-use version of cygwin1.dll during an installation it's not. Clearly what you're running into is postinstall scripts that are running with updated tools accessing the older version of cygwin1.dll you have. The solution? Reboot and run 'setup.exe' again. The postinstall scripts that didn't already run will be run in the process. You don't need to reinstall any packages unless you ignored any of the error messages you got and allowed the postinstall scripts to continue running. Speaking of reinstall, if I did ignore those pesky error messages, is there a way to mark all my existing packages for update so I can rereun the setup again? Kind of like an upgrade do over? Thanks - Tod -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin upgrade
On 01/12/2010 07:16 AM, Tod wrote: On 1/11/2010 3:58 PM, Larry Hall (Cygwin) wrote: On 01/11/2010 03:46 PM, Tod wrote: I'm upgrading to 1.7.1 from the previous version which I was pretty good at keeping up to date. I ran into a problem installing openssh which locked the install forcing me to cancel. I stopped the openssh service and cygwin service and tried again. It completed with me ok'ing past pointer errors on certain packages from the previous install attempt. I restarted and now get the message: The procedure entry point __ctype_ptr__ could not be located in the dynamic link library cygwin1.dll. I'm running XP service pack 2. I haven't rebooted the box yet so maybe that has something to do with it? The thought was that reboot in Cygwin terms was restarting Cygwin. I'll try the box now and report back tomorrow. Not when you're dealing with an in-use version of cygwin1.dll during an installation it's not. Clearly what you're running into is postinstall scripts that are running with updated tools accessing the older version of cygwin1.dll you have. The solution? Reboot and run 'setup.exe' again. The postinstall scripts that didn't already run will be run in the process. You don't need to reinstall any packages unless you ignored any of the error messages you got and allowed the postinstall scripts to continue running. Speaking of reinstall, if I did ignore those pesky error messages, is there a way to mark all my existing packages for update so I can rereun the setup again? Kind of like an upgrade do over? Rerun 'setup.exe' and click the symbol next to All until Reinstall shows up. Continue with 'setup.exe' as usual. This will reinstall all the packages you have installed. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
On Jan 12 15:59, Niklaus Kuehnis wrote: Hi, I've upgraded to Cygwin 1.7 (release version, clean install) and now am unable to print text files with non-ascii characters (i.e. German umlauts) from commandline. Did you read the User's Guide, especially http://cygwin.com/cygwin-ug-net/setup-locale.html ? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 'as it was replaced while being copied'
On Jan 12 10:04, Charles Wilson wrote: $ cp ../*cpp . cp: skipping file `../tactical_transmit_msg.cpp', as it was replaced while being copied cp: skipping file `../test.cpp', as it was replaced while being copied cp: skipping file `../test2.cpp', as it was replaced while being copied cp: skipping file `../xml_message_types.cpp', as it was replaced while being copied This is on a SMB share (actually, it's a distributed file system exposed to windows via SMB). I've attached the output of cygcheck and getvolinfo. This is the first time I've tried to do anything on this share since upgrading to 1.7.1-official, but before the holidays I was using 1.7.0-nn, on a 32bit machine. For Christmas IT gave me a brand new 64 bit machine, and they may (or may not) have changed something with regards to this filesystem over the holidays -- so the culprit is not necessarily something that changed *in cygwin*. But I'd still like cp to work... Any ideas? Debugging might help. Is that SMB as in Samba or as in real remote NTFS? The error message points to an unreliable inode handling. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Question about yacc linking on new mingw-w64 cygwin patch.
Dear all, I am trying to build gcc using cygwin on my new win64 machine. I have downloaded the latest mingw code (mingw-w64-trunk-snapshot-20091222.tar.bz2) and followed the instruction in mingw-w64-howto-build.txt. However I have the following error: gengtype-parse.c:952: undefined reference to `_yyend' I have installed bison and flex on my machine. Would you be able to help. Thank you very much. Renaud. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Perl, abs_path from Version 5.10.1-1 to 5.10.1-2 changed behaviour (no longer uses fast_path?)
Hi *,
I have a perl script, which stopped working, when I recently updated cygwin
to 1.7.
Here is a small demo script which shows the problem. It just calls abs_path()
with different values and prints the output. It would be great if anyone
could confirm that they also see this behaviour.
#!/bin/env perl
use strict;
use Cwd 'abs_path';
abs_path_WITHDEBUG(.);
abs_path_WITHDEBUG(C:\\);
abs_path_WITHDEBUG(C:\\Program Files\\);
abs_path_WITHDEBUG(C:\\Does Not Exist\\);
exit;
sub abs_path_WITHDEBUG
{
my $pPath = shift;
my $result_path=abs_path($pPath);
print Test: \n PrePath={.$pPath.}\nPostPath={.$result_path.}\n\n;
return $result_path;
}
When called with current Perl Version 5.10.1-2 it shows this output:
Test:
PrePath={.}
PostPath={/tmp}
Test:
PrePath={C:\}
PostPath={/tmp/C:\} --- broken
Test:
PrePath={C:\Program Files\}
PostPath={/tmp/C:\Program Files\} --- broken
Test:
PrePath={C:\Does Not Exist\}
PostPath={/tmp/C:\Does Not Exist\} --- broken
Please notice, that the Windows path is justed added to the current
Unix path (which results in a broken path)
When I manually downgrade Perl to Version 5.10.1-1 it shows this output:
Test:
PrePath={.}
PostPath={/tmp}
Test:
PrePath={C:\}
PostPath={/cygdrive/c}
Test:
PrePath={C:\Program Files\}
PostPath={/cygdrive/c/Program Files}
C:\Does Not Exist\: No such file or directory at ./demo.pl line 20
Here I get the correct Unix path in all cases.
The difference seems to be in Cwd.pm:
diff -u -U5 Cwd.pm*
--- Cwd.pm_old 2010-01-12 15:37:19.718007800 +0100
+++ Cwd.pm_new 2010-01-12 15:46:32.159043400 +0100
@@ -303,11 +303,11 @@
cygwin =
{
getcwd = 'cwd',
fastgetcwd = 'cwd',
fastcwd= 'cwd',
-abs_path = 'fast_abs_path',
+# abs_path = 'fast_abs_path',
realpath = 'fast_abs_path',
},
epoc =
{
@@ -817,8 +817,8 @@
*abs_path = \_perl_abs_path unless defined abs_path;
*getcwd = \_perl_getcwd unless defined getcwd;
# added function alias for those of us more
# used to the libc function. --tchrist 27-Jan-00
-*realpath = \abs_path;
+*realpath = \abs_path unless defined realpath;
1;
So abs_path used to point to fast_abs_path, but does not longer for Cygwin?
When I use fast_abs_path instead of abs_path in my test script it works for
both perl versions 5.10.1-1 and 5.10.1-2. What was wrong with fast_abs_path?
Should I just replace abs_path to fast_abs_path?
regards
Thorsten
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Question about yacc linking on new mingw-w64 cygwin patch.
On Tue, Jan 12, 2010 at 03:22:24PM -, Renaud Meunier wrote: I am trying to build gcc using cygwin on my new win64 machine. I have downloaded the latest mingw code (mingw-w64-trunk-snapshot-20091222.tar.bz2) and followed the instruction in mingw-w64-howto-build.txt. However I have the following error: gengtype-parse.c:952: undefined reference to `_yyend' I have installed bison and flex on my machine. Would you be able to help. Doesn't the word mingw give you a strong clue that this is not something that would be handled in the cygwin mailing list? Please contact the authors of the package that you've installed for help. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Running Cygwin from an NFS drive (symlinks with system attribute)
On Jan 11 14:14, Larry Hall (Cygwin) wrote: On 01/11/2010 05:22 AM, Corinna Vinschen wrote: Is my description under using-cygwinenv.html unclear? I only compared the old and the new format. The new format using UTF-16 is used by both styles of symlinks, the SYSTEM and the .lnk style. OK, I didn't get that from my reading of the description. I'd recommend adding that path names of either style now use UTF-16, just to be clear. I doubt this is a critical issue of course but it's worthwhile to make this distinction to avoid confusion. I tried to make it clearer. Is that better? http://cygwin.com/cygwin-ug-net/using-cygwinenv.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Tried out cygwin-inst-20100111.tar.bz2
On Jan 11 22:39, Karl M wrote: Hi All... I just tried out the latest snapshot and had two problems on a Vista Business SP2 machine. The first problem was that in bash shell launched from the cygwin.bat file in a console window, the backspace did nothing. I also received the following error from find: $ find / -name '*code.exe' /lib/code.exe /lib/frcode.exe find: `/tmp/ssh-OksMRN4552': Permission denied /usr/lib/code.exe /usr/lib/frcode.exe assertion ent-fts_info == FTS_NSOK || state.type != 0 failed: file /usr/src/findutils-4.5.5-1/src/findutils-4.5.5/find/ftsfind.c, line 477, function: consider_visiting 3 [main] find 2160 sig_send: wait for sig_complete event failed, signal 6, rc 258, Win32 error 0 I can reproduce find(1) failing, but it's not clear to me where and why this happens. Apparently there's a point where internally allocated space gets overwritten while recursively calling readdir. Due to the huge number of files it's not easy to catch the place where this happens. OTOH this does not occur when recursively calling readdir using ls(1) which allows the assumption that it's find, not Cygwin, which overwrites the memory. Where's the difference between find and ls when recursing through directories? Eric, do you see a chance to find time to debug this? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Perl, abs_path from Version 5.10.1-1 to 5.10.1-2 changed behaviour (no longer uses fast_path?)
Thorsten Gunkel schrieb:
Hi *,
I have a perl script, which stopped working, when I recently updated cygwin
to 1.7.
Here is a small demo script which shows the problem. It just calls abs_path()
with different values and prints the output. It would be great if anyone
could confirm that they also see this behaviour.
#!/bin/env perl
use strict;
use Cwd 'abs_path';
abs_path_WITHDEBUG(.);
abs_path_WITHDEBUG(C:\\);
abs_path_WITHDEBUG(C:\\Program Files\\);
abs_path_WITHDEBUG(C:\\Does Not Exist\\);
exit;
sub abs_path_WITHDEBUG
{
my $pPath = shift;
my $result_path=abs_path($pPath);
print Test: \n PrePath={.$pPath.}\nPostPath={.$result_path.}\n\n;
return $result_path;
}
When called with current Perl Version 5.10.1-2 it shows this output:
Test:
PrePath={.}
PostPath={/tmp}
Test:
PrePath={C:\}
PostPath={/tmp/C:\}--- broken
Test:
PrePath={C:\Program Files\}
PostPath={/tmp/C:\Program Files\}--- broken
Test:
PrePath={C:\Does Not Exist\}
PostPath={/tmp/C:\Does Not Exist\}--- broken
Please notice, that the Windows path is justed added to the current
Unix path (which results in a broken path)
When I manually downgrade Perl to Version 5.10.1-1 it shows this output:
Test:
PrePath={.}
PostPath={/tmp}
Test:
PrePath={C:\}
PostPath={/cygdrive/c}
Test:
PrePath={C:\Program Files\}
PostPath={/cygdrive/c/Program Files}
C:\Does Not Exist\: No such file or directory at ./demo.pl line 20
Here I get the correct Unix path in all cases.
The difference seems to be in Cwd.pm:
diff -u -U5 Cwd.pm*
--- Cwd.pm_old 2010-01-12 15:37:19.718007800 +0100
+++ Cwd.pm_new 2010-01-12 15:46:32.159043400 +0100
@@ -303,11 +303,11 @@
cygwin =
{
getcwd = 'cwd',
fastgetcwd = 'cwd',
fastcwd= 'cwd',
-abs_path = 'fast_abs_path',
+# abs_path = 'fast_abs_path',
realpath = 'fast_abs_path',
},
epoc =
{
@@ -817,8 +817,8 @@
*abs_path = \_perl_abs_path unless definedabs_path;
*getcwd = \_perl_getcwd unless definedgetcwd;
# added function alias for those of us more
# used to the libc function. --tchrist 27-Jan-00
-*realpath = \abs_path;
+*realpath = \abs_path unless definedrealpath;
1;
So abs_path used to point to fast_abs_path, but does not longer for Cygwin?
When I use fast_abs_path instead of abs_path in my test script it works for
both perl versions 5.10.1-1 and 5.10.1-2. What was wrong with fast_abs_path?
Should I just replace abs_path to fast_abs_path?
Yes please, until we come up with a satisfactory solution for all problems.
It was caused by a patch request from Eliott Moss
http://sourceware.org/ml/cygwin/2009-12/msg00506.html for svk,
which caused no regressions in the tests.
I'll talk to Stefan Müller to add such tests to the PathTools package.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
various problems resulting from version 1.7.1
After installing Cygwin 1.7.1, I noticed ugly man pages because LANG=UTF-8 causes man pages to be formatted with U+2010 hyphens, which aren't supported by Windows, so I took another's advice and installed mintty, which seemed to work just fine until I tried to use FTP or Telnet (the Windows versions). The mintty man page pro- vides a reason why it might not work with certain interactive pro- grams (see LIMITATIONS), which I presume includes these two programs. In lieu of going back to LANG=C and cygwin.bat, wondering if there is a recommended configuration that doesn't have these problems. --Ken Nellis
Re: Running Cygwin from an NFS drive (symlinks with system attribute)
On 01/12/2010 11:44 AM, Corinna Vinschen wrote: On Jan 11 14:14, Larry Hall (Cygwin) wrote: On 01/11/2010 05:22 AM, Corinna Vinschen wrote: Is my description under using-cygwinenv.html unclear? I only compared the old and the new format. The new format using UTF-16 is used by both styles of symlinks, the SYSTEM and the .lnk style. OK, I didn't get that from my reading of the description. I'd recommend adding that path names of either style now use UTF-16, just to be clear. I doubt this is a critical issue of course but it's worthwhile to make this distinction to avoid confusion. I tried to make it clearer. Is that better? http://cygwin.com/cygwin-ug-net/using-cygwinenv.html Perfect. :-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: various problems resulting from version 1.7.1
On 1/12/2010 12:08 PM, Nellis, Kenneth wrote: After installing Cygwin 1.7.1, I noticed ugly man pages because LANG=UTF-8 causes man pages to be formatted with U+2010 hyphens, which aren't supported by Windows, so I took another's advice and installed mintty, which seemed to work just fine until I tried to use FTP or Telnet (the Windows versions). The mintty man page pro- vides a reason why it might not work with certain interactive pro- grams (see LIMITATIONS), which I presume includes these two programs. In lieu of going back to LANG=C and cygwin.bat, wondering if there is a recommended configuration that doesn't have these problems. You could use Cygwin-based Telnet and FTP programs under Mintty. I'm personally fond of ncftp for FTP, and while I prefer to use SSH these days, the telnet program included in the inetutils package always worked for me back in the day. In general I try to avoid using Windows-native software under Cygwin whenever a Cygwin-based alternative is available. It's just easier that way for me. :-) -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Tried out cygwin-inst-20100111.tar.bz2
Date: Tue, 12 Jan 2010 17:48:34 +0100 From: corinna Subject: Re: Tried out cygwin-inst-20100111.tar.bz2 On Jan 11 22:39, Karl M wrote: Hi All... I just tried out the latest snapshot and had two problems on a Vista Business SP2 machine. The first problem was that in bash shell launched from the cygwin.bat file in a console window, the backspace did nothing. Do the changes from 1.7.1 to the latest snapshot require me to do something with LANG settings for a US English Southern California Vista Business SP2 machine? Pressing the backspace key did nothing, no cursor motion or deletion. Reverting to 1.7.1 restored the backspace key functionality. Thanks, ...Karl _ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/196390707/direct/01/ -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Running Cygwin from an NFS drive (symlinks with system attribute)
Hi, I am afraid the winsymlinks option is an installation time setting, is it? : --- sbre...@katz /usr/bin $ set | grep CYGWIN CYGWIN=winsymlinks CYGWIN_PATH='H:\Bazsi\cygwin\' sbre...@katz /usr/bin $ which awk /usr/bin/awk sbre...@katz /usr/bin $ awk /usr/bin/awk: /usr/bin/awk: cannot execute binary file --- Shall I set the environment variable: CYGWIN=winsymlinks and install Cygwin from scratch? Would the reexecution of the post-installation scripts be enough? Thanks for the help! /Balazs Date: Tue, 12 Jan 2010 14:11:04 -0500 From: reply-to-list-only...@cygwin.com To: cygwin@cygwin.com Subject: Re: Running Cygwin from an NFS drive (symlinks with system attribute) On 01/12/2010 11:44 AM, Corinna Vinschen wrote: On Jan 11 14:14, Larry Hall (Cygwin) wrote: On 01/11/2010 05:22 AM, Corinna Vinschen wrote: Is my description under using-cygwinenv.html unclear? I only compared the old and the new format. The new format using UTF-16 is used by both styles of symlinks, the SYSTEM and the .lnk style. OK, I didn't get that from my reading of the description. I'd recommend adding that path names of either style now use UTF-16, just to be clear. I doubt this is a critical issue of course but it's worthwhile to make this distinction to avoid confusion. I tried to make it clearer. Is that better? http://cygwin.com/cygwin-ug-net/using-cygwinenv.html Perfect. :-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple _ Keep your friends updated—even when you’re not signed in. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Running Cygwin from an NFS drive (symlinks with system attribute)
2010/1/12 sbremal I am afraid the winsymlinks option is an installation time setting, is it? : No, but it only affects newly created symlinks. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Running Cygwin from an NFS drive (symlinks with system attribute)
Thanks! What way do you guys suggest to convert all existing symlinks to the
.lnk style? Complete reinstall with setup.exe? Hope there is a second option...
;-)
There are quite some hits for: find / -exec grep '!symlink' {} \;
/Balazs
Date: Tue, 12 Jan 2010 21:40:52 +
Subject: Re: Running Cygwin from an NFS drive (symlinks with system attribute)
From: andy.ko...@gmail.com
To: cygwin@cygwin.com
2010/1/12 sbremal
I am afraid the winsymlinks option is an installation time setting, is it? :
No, but it only affects newly created symlinks.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
_
Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail
you.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Running Cygwin from an NFS drive (symlinks with system attribute)
On 01/12/2010 04:52 PM, sbre...@hotmail.com wrote:
Thanks! What way do you guys suggest to convert all existing symlinks to
the .lnk style? Complete reinstall with setup.exe? Hope there is a second
option... ;-)
There are quite some hits for: find / -exec grep '!symlink' {} \;
Right. And 'find' would be the way to do it. But if you're going to change
them, you're better off changing them to the Linux/Unix symlink from that
end (same procedure though). Then the symlinks should be understood as
simlinks on the server and the clients (uses MS's client).
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_
A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: various problems resulting from version 1.7.1
Thank you, Jeremy. BTW, I deal with legacy machines that don't know from SSH. :-( Well this gets more interesting, at least to me... With LANG=UTF-8, man uses the Unicode HYPHEN character (U+2010) to break long words at the right margin, and uses the Unicode MINUS character (U+2212) to prefix command line options (e.g., ls -l). The Windows Command Prompt window, used by Cygwin.bat, doesn't display U+2010 correctly with the Lucida Console font, but it works correctly with the default FixedSys font. Mintty, OTOH, doesn't display U+2212 correctly with the default FixedSys font, but does with the Lucida Console font. So, if I can tolerate the ugly FixedSys font, then I can use Cygwin.bat and the Windows FTP and Telnet tools without (anticipated) problems. (I wonder if the Mintty developer would want to update Mintty to support U+2212.) --Ken Nellis -Original Message- From: Jeremy Bopp [mailto:jer...@bopp.net] Sent: Tuesday, January 12, 2010 14:49 To: cygwin@cygwin.com Subject: Re: various problems resulting from version 1.7.1 On 1/12/2010 12:08 PM, Nellis, Kenneth wrote: After installing Cygwin 1.7.1, I noticed ugly man pages because LANG=UTF-8 causes man pages to be formatted with U+2010 hyphens, which aren't supported by Windows, so I took another's advice and installed mintty, which seemed to work just fine until I tried to use FTP or Telnet (the Windows versions). The mintty man page pro- vides a reason why it might not work with certain interactive pro- grams (see LIMITATIONS), which I presume includes these two programs. In lieu of going back to LANG=C and cygwin.bat, wondering if there is a recommended configuration that doesn't have these problems. You could use Cygwin-based Telnet and FTP programs under Mintty. I'm personally fond of ncftp for FTP, and while I prefer to use SSH these days, the telnet program included in the inetutils package always worked for me back in the day. In general I try to avoid using Windows-native software under Cygwin whenever a Cygwin-based alternative is available. It's just easier that way for me. :-) -Jeremy
Re: various problems resulting from version 1.7.1
2010/1/12 Nellis, Kenneth: Thank you, Jeremy. BTW, I deal with legacy machines that don't know from SSH. :-( Well this gets more interesting, at least to me... With LANG=UTF-8, man uses the Unicode HYPHEN character (U+2010) to break long words at the right margin, and uses the Unicode MINUS character (U+2212) to prefix command line options (e.g., ls -l). The Windows Command Prompt window, used by Cygwin.bat, doesn't display U+2010 correctly with the Lucida Console font, but it works correctly with the default FixedSys font. The FixedSys font is not a Unicode font, so what happens is that the console display switches into codepage mode and automatically maps all Unicode characters not in the font's codepage to some approximation of them, where possible. For hyphen and minus that works well, but for most characters it doesn't. You'll just get question marks instead. Mintty, OTOH, doesn't display U+2212 correctly with the default FixedSys font, but does with the Lucida Console font. So, if I can tolerate the ugly FixedSys font, then I can use Cygwin.bat and the Windows FTP and Telnet tools without (anticipated) problems. (I wonder if the Mintty developer would want to update Mintty to support U+2212.) It is supported just fine. Mintty does have a special hack to map U+2010 to plain '-', because most fixed-width Windows seem to be missing that for some reason, but U+2212 is present in all the fonts I've tried, except of course in non-Unicode fonts. For example, Consolas, Courier New, and DejaVu Sans Mono all have it. Bottom line: use a Unicode font for UTF-8. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problems running courierauth (UNIX-sockets) - more information
Hi There I have more information concerning my courierauth problem strace of authdaemon gives me: -- snip -- 254 158676 [main] authdaemond 38964 path_conv::check: this-path(C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp), has_acls(1) 691 159367 [main] authdaemond 38964 alloc_sd: uid -1, gid -1, attribute 81ED 98 159465 [main] authdaemond 38964 cygsid::debug_print: alloc_sd: owner SID = S-1-5-21-2662617662-1419630648-2448393657-1000 (+) 63 159528 [main] authdaemond 38964 cygsid::debug_print: alloc_sd: group SID = S-1-5-21-2662617662-1419630648-2448393657-512 (+) 77 159605 [main] authdaemond 38964 alloc_sd: ACL-Size: 100 163 159768 [main] authdaemond 38964 alloc_sd: Created SD-Size: 176 485 160253 [main] authdaemond 38964 set_file_attribute: 0 = set_file_attribute (\??\C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, -1, -1, 0x81ED) 133 160386 [main] authdaemond 38964 fhandler_base::set_flags: flags 0x1, supplied_bin 0x0 52 160438 [main] authdaemond 38964 fhandler_base::set_flags: O_TEXT/O_BINARY set in flags 0x1 46 160484 [main] authdaemond 38964 fhandler_base::set_flags: filemode set to binary 93163 253647 [main] authdaemond 38964 cygwin_bind: 0 = bind (5, 0x22CC70, 110) 111 253758 [main] authdaemond 38964 sig_send: sendsig 0x6F8, pid 38964, signal -34, its_me 1 68 253826 [main] authdaemond 38964 sig_send: wakeup 0x618 63 253889 [main] authdaemond 38964 sig_send: Waiting for pack.wakeup 0x618 64 253953 [sig] authdaemond 38964 wait_sig: signalling pack.wakeup 0x618 77 254030 [main] authdaemond 38964 sig_send: returning 0x0 from sending signal -34 6452 260482 [main] authdaemond 38964 cygwin_listen: 0 = listen (5, 2147483647) 106 260588 [main] authdaemond 38964 normalize_posix_path: src /usr/local/var/spool/authdaemon/socket.tmp 202 260790 [main] authdaemond 38964 normalize_posix_path: /usr/local/var/spool/authdaemon/socket.tmp = normalize_posix_path (/usr/local/var/spool/authdaemon/socket.tmp) 149 260939 [main] authdaemond 38964 mount_info::conv_to_win32_path: conv_to_win32_path (/usr/local/var/spool/authdaemon/socket.tmp) 69 261008 [main] authdaemond 38964 set_flags: flags: binary (0x2) 60 261068 [main] authdaemond 38964 mount_info::conv_to_win32_path: src_path /usr/local/var/spool/authdaemon/socket.tmp, dst C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, flags 0x3000A, rc 0 323 261391 [main] authdaemond 38964 symlink_info::check: not a symlink 99 261490 [main] authdaemond 38964 symlink_info::check: 0 = symlink.check (C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, 0x22B0D8) (0x4003000A) 83 261573 [main] authdaemond 38964 path_conv::check: this-path(C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp), has_acls(1) 57 261630 [main] authdaemond 38964 build_fh_pc: fh 0x6120ED9C 57 261687 [main] authdaemond 38964 fhandler_base::open: (\??\C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, 0x11) 118 261805 [main] authdaemond 38964 fhandler_base::set_flags: flags 0x11, supplied_bin 0x0 71 261876 [main] authdaemond 38964 fhandler_base::set_flags: O_TEXT/O_BINARY set in flags 0x1 54 261930 [main] authdaemond 38964 fhandler_base::set_flags: filemode set to binary 51 261981 [main] authdaemond 38964 fhandler_base::open: 0 = NtCreateFile (0x618, E0100, \??\C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, io, NULL, 0, 7, 1, 4000, NULL, 0) 56 262037 [main] authdaemond 38964 fhandler_base::open: 1 = fhandler_base::open (\??\C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, 0x11) 70 262107 [main] authdaemond 38964 fhandler_base::open_fs: 1 = fhandler_disk_file::open (\??\C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, 0x1) 113 262220 [main] authdaemond 38964 alloc_sd: uid -1, gid -1, attribute C1FF 64 262284 [main] authdaemond 38964 cygsid::debug_print: alloc_sd: owner SID = S-1-5-21-2662617662-1419630648-2448393657-1000 (+) 54 262338 [main] authdaemond 38964 cygsid::debug_print: alloc_sd: group SID = S-1-5-21-2662617662-1419630648-2448393657-512 (+) 58 262396 [main] authdaemond 38964 alloc_sd: ACL-Size: 100 102 262498 [main] authdaemond 38964 alloc_sd: Created SD-Size: 176 202 262700 [main] authdaemond 38964 set_file_attribute: 0 = set_file_attribute (\??\C:\cygwin\usr\local\var\spool\authdaemon\socket.tmp, -1, -1, 0xC1FF) 168 262868 [main] authdaemond 38964 fhandler_base::close: closing '/usr/local/var/spool/authdaemon/socket.tmp' handle 0x618 103 262971 [main] authdaemond 38964 chmod: 0 = chmod (/usr/local/var/spool/authdaemon/socket.tmp, 0x1FF) 67 263038 [main] authdaemond 38964 normalize_posix_path: src /usr/local/var/spool/authdaemon/socket.tmp 57 263095 [main] authdaemond 38964 normalize_posix_path: /usr/local/var/spool/authdaemon/socket.tmp = normalize_posix_path (/usr/local/var/spool/authdaemon/socket.tmp) 55 263150 [main] authdaemond 38964 mount_info::conv_to_win32_path:
Re: How to print textfiles in Cygwin 1.7?
try using pdf creator and make it shared, then you can use it have you tested printing a plain text from command shell eg my.txt lpt1 or the like Niklaus Kuehnis wrote: Hi, I've upgraded to Cygwin 1.7 (release version, clean install) and now am unable to print text files with non-ascii characters (i.e. German umlauts) from commandline. On Cygwin 1.5 printing used to work with a2ps but now all umlauts are replaced by strange characters (i.e. the u with diaeresis appears as a capital A with a tilde and '1/4'). The same happens with lpr. The files print fine using the Windows text editor. I'm using mintty on Windows Vista Business and nano to produce the files. Files with umlauts are recognized as UTF-8 by the file command. Is there an alternative to a2ps or a fix/workaround? Thanks in advance! Niklaus $ a2ps --version GNU a2ps 4.13 $ uname -a CYGWIN_NT-6.0 machinename 1.7.1(0.218/5/3) 2009-12-07 11:48 i686 Cygwin $ mintty --version mintty 0.5.6 $ nano --version GNU nano Version 2.0.9 (compiliert um 13:11:06, Oct 19 2008) -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- View this message in context: http://old.nabble.com/How-to-print-textfiles-in-Cygwin-1.7--tp27128849p27137998.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libogg-1.1.4-1/libogg-devel-1.1.4-1/libogg0-1.1.4-1
A new version the libogg, libogg-devel, and libogg0 packages are now available for download. NEWS: = This is a new upstream release, with upstream changes listed below. DESCRIPTION: Ogg project codecs use the Ogg bitstream format to arrange the raw, compressed bitstream into a more robust, useful form. For example, the Ogg bitstream makes seeking, time stamping and error recovery possible, as well as mixing several sepearate, concurrent media streams into a single physical bitstream. DOWNLOAD: = Note that downloads from sourceware.org (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- David Rothenberger daver...@acm.org The Abrams' Principle: The shortest distance between two points is off the wall. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: various problems resulting from version 1.7.1
Nellis, Kenneth a écrit : Thank you, Jeremy. BTW, I deal with legacy machines that don't know from SSH. :-( Hi, give a try to puttycyg which support both ssh, telnet as well cygwin. advantage over windows terminal, you may make it a full screen. you may also switch the font encoding to UTF-8 instead of the default iso8859-1 one. http://code.google.com/p/puttycyg/ however, w/ LANG=C.UTF-8, the minus is correct but not the hyphen in LucindaConsole font. Regards, Cyrille Lefevre -- mailto:cyrille.lefevre-li...@laposte.net -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: asciidoc-8.5.2-1
A new version of the asciidoc package, asciidoc 8.5.2-1, is now available
for download, leaving 8.4.5-1 as previous.
NEWS:
=
This is a new upstream release, with release notes listed below. See also
the package documentation in /usr/share/doc/asciidoc/.
DESCRIPTION:
AsciiDoc is a text document format for writing short documents, articles,
books and UNIX man pages. AsciiDoc files can be translated to HTML and
DocBook markups using the asciidoc(1) command. AsciiDoc is highly
configurable: both the AsciiDoc source file syntax and the backend output
markups (which can be almost any type of SGML/XML markup) can be
customized and extended by the user.
UPDATE:
===
To update your installation, click on the Install Cygwin now link on the
http://cygwin.com/ web page. This downloads setup.exe to your system.
Save it and run setup, answer the questions and pick up 'asciidoc' from
the 'Devel' category.
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations. This means that you will need to
find a mirror which has this update, please choose the one nearest to you:
http://cygwin.com/mirrors.html
QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.
--
Eric Blake
volunteer cygwin asciidoc maintainer
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO:
=
To unsubscribe to the cygwin-announce mailing list, look at the
List-Unsubscribe: tag in the email header of this message. Send email
to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
1. Version 8.5.2 (2009-12-09)
Additions and changes
* Added Italian language configuration file (contributed by Fabio
Inguaggiato).
* Added header table style. See:
[1]http://groups.google.com/group/asciidoc/browse_frm/thread/a23fea
28394c8ca9
* Pass icons, data-uri, imagesdir, iconsdir attributes to asciidoc
table style filter so that images are rendered in table cells.
* Pass trace and verbose attributes to asciidoc table style filter so
diagnostic information is printed from table cell source.
* The eval system attribute can be nested inside other system
attributes.
* HTML outputs: Table and figure caption punctuation set to more
usual syntax.
* docbook backend: footnotes can now contain embedded images. See
[2]http://groups.google.com/group/asciidoc/browse_frm/thread/50b28f
6941de111a
* CSS tweaks so that tables processed by DocBook XSL Stylesheets have
the default asciidoc xhtml11 backend styling. See
[3]http://groups.google.com/group/asciidoc/browse_frm/thread/dfe520
4d5b2c9685
* Block titles take precedence over section titles to avoid titled
delimited blocks being mistaken for two line section titles (see
[4]http://groups.google.com/group/asciidoc/browse_frm/thread/f0b6f9
989f828c3).
* Section title trace displays level and title text.
* FAQ additions.
* Added {zwsp} (zero width space) attribute.
* Undefined paragraph styles are reported (previously threw a runtime
error).
* Eliminated empty preamble generation.
* Floating titles now processed in all contexts.
* Implemented auto-lettered appendix names and updated example
documents.
* Section numbering can be disabled in HTML outputs with a
:numbered!: AttributeEntry.
* xhtml11: Nicer default quote block styling.
* Exclude floating titles from xhtml11 table of contents. Patch
submitted by Mark Burton (see
[5]http://groups.google.com/group/asciidoc/browse_frm/thread/14aefc
1cb6bd85f5).
* Enhanced doc/article-docinfo.xml example docinfo file.
* Vim syntax highlighter improvements.
Bug fixes
* FIXED: Absolute imagesdir and iconsdir attribute path names do not
work with the xhtml11 data-uri encoding. See
[6]http://groups.google.com/group/asciidoc/browse_frm/thread/cb8b76
94bbc82a6
* FIXED: Regression issue with inline data-uri images. See
[7]http://groups.google.com/group/asciidoc/browse_frm/thread/cb8b76
94bbc82a6
* FIXED: An unexpected error occurred when processing a table
containing CSV data if the cols attribute was not explicitly
specified. See
[8]http://groups.google.com/group/asciidoc/browse_frm/thread/4b0f36
4b477ec165
__
2. Version 8.5.1 (2009-10-31)
Additions and changes
* If an AsciiDoc document file begins with a UTF-8 BOM (byte order
mark) then it is
[ANNOUNCEMENT] Updated: sharutils-4.7-2
A new release of sharutils, 4.7-2, is available, leaving 4.6.3-1 as previous. NEWS: = This is an update to build against cygwin 1.7, using gcc 4, and to update the documentation layout to match recommended practice. Using shar on text mounts continues to have the possibility that line endings on text files might not be handled the way you want, but if it was truly a text file, that should not matter to you; the heuristic that shar uses to decide between text and binary files is whether it contains non-printing characters. It is safer to use shar/unshar on binary mounts (remembering that unshar is inherently unsafe). uuencode and uudecode, on the other hand, work reliably regardless of the underlying mount point. See also the package documentation found in /usr/share/doc/sharutils/. DESCRIPTION: The sharutils package contains the GNU shar utilities, a set of tools for encoding and decoding packages of files (in binary or text format) in a special plain text format called shell archives (shar). This format can be sent through e-mail (which can be problematic for regular binary files). The shar utility supports a wide range of capabilities (compressing, uuencoding, splitting long files for multi-part mailings, providing checksums), which make it very flexible at creating shar files. After the files have been sent, the unshar tool scans mail messages looking for shar files. Unshar automatically strips off mail headers and introductory text and then unpacks the shar files. Note that unshar is inherently unsafe by design, because it executes arbitrary shell scripts; therefore the creation of shar archives should be limited to situations where the receiver trusts the sender. However, uuencode and uudecode are useful in their own right, and are safe to use. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'sharutils' from the 'Archive' category. DOWNLOAD: = Note that downloads from cygwin.com aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- Eric Blake volunteer cygwin sharutils maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
[ANNOUNCEMENT] Removed: cogito-0.18.2-2
Now that cygwin 1.7 has been released, and upstream cogito 0.18.2 was marked deprecated several years ago, the cogito package is no longer part of the cygwin distribution. If you absolutely need cogito, you can download it from setup-legacy.exe for cygwin 1.5, or rebuild from upstream sources. However, it is recommended that you use git itself, or one of several actively maintained wrappers around git, rather than using the obsolete cogito wrapper. DESCRIPTION: Cogito was an interface to the Git version control system, back in the git 1.4.x days. It was designed to be comfortable, easy to use and present gentle learning curve for new users. QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- Eric Blake former volunteer cygwin cogito maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
[ANNOUNCEMENT] Updated: cvsps-2.2b1-1
A new release of cvsps, 2.2b1-1, is now available for download, leaving 2.1-1 as previous. NEWS: = This is a new upstream release. Upstream marks it as development rather than stable, but it has several bug fixes over the previous release that can aid in converting a CVS repository with branching into a more modern version control system. See also the package documentation in /usr/share/doc/cvsps/. Upstream changes include: 2.2b1 - add a new line item in the PatchSet output which indicates which branches fork off from after this PatchSet. This is actually the only way to correctly indicate the branching. The 'Ancestor Branch' thing is actually broken by design, and is now deprecated. - sometimes cvs log has a timezone in it (from Ludwig Nussel) - better buffer size handling DESCRIPTION: CVSps is a program for generating 'patchset' information from a CVS repository. A patchset in this case is defined as a set of changes made to a collection of files, and all committed at the same time (using a single 'cvs commit' command). This information is valuable to seeing the big picture of the evolution of a cvs project. While cvs tracks revision information, it is often difficult to see what changes were committed 'atomically' to the repository. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'cvsps' from the 'Devel' category. DOWNLOAD: = Note that downloads from cygwin.com aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- Eric Blake volunteer cygwin cvsps maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
Re: How to print textfiles in Cygwin 1.7?
2010/1/12 Niklaus Kuehnis: I've upgraded to Cygwin 1.7 (release version, clean install) and now am unable to print text files with non-ascii characters (i.e. German umlauts) from commandline. On Cygwin 1.5 printing used to work with a2ps but now all umlauts are replaced by strange characters (i.e. the u with diaeresis appears as a capital A with a tilde and '1/4'). The same happens with lpr. The files print fine using the Windows text editor. The problem is that both a2ps and lpr don't yet support UTF-8. Instead, they interpret the UTF-8 bytes as ISO-8859-1, which is why umlauts, which are represented as two bytes in UTF-8, appear as two funny characters. a2ps has the -X option to tell it explicitly what encoding to use, but unfortunately: $ a2ps -X UTF-8 a2ps: unknown encoding `utf-8' One workaround is to convert the file manually using iconv, e.g.: $ iconv -f utf-8 -t iso-8859-1 bla.txt | a2ps -o bla.ps (Of course this only works properly as long as your file doesn't have any characters outside iso-8859-1.) I'm using mintty on Windows Vista Business and nano to produce the files. Files with umlauts are recognized as UTF-8 by the file command. Please note that 'nano' also doesn't support UTF-8 yet. While entering characters looks like it works initially, nano will internally think that you've entered two characters when you enter an umlaut. Hence things get wonky when you try to edit them. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: various problems resulting from version 1.7.1
2010/1/13 Cyrille Lefevre: give a try to puttycyg which support both ssh, telnet as well cygwin. The OP is insisting on running the Windows versions of telnet and ftp, and those won't work in puttycyg either. Same in any other terminal based on 'pseudo terminal' (pty) devices. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Updated: libogg-1.1.4-1/libogg-devel-1.1.4-1/libogg0-1.1.4-1
A new version the libogg, libogg-devel, and libogg0 packages are now available for download. NEWS: = This is a new upstream release, with upstream changes listed below. DESCRIPTION: Ogg project codecs use the Ogg bitstream format to arrange the raw, compressed bitstream into a more robust, useful form. For example, the Ogg bitstream makes seeking, time stamping and error recovery possible, as well as mixing several sepearate, concurrent media streams into a single physical bitstream. DOWNLOAD: = Note that downloads from sourceware.org (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- David Rothenberger daver...@acm.org The Abrams' Principle: The shortest distance between two points is off the wall.
Updated: asciidoc-8.5.2-1
A new version of the asciidoc package, asciidoc 8.5.2-1, is now available
for download, leaving 8.4.5-1 as previous.
NEWS:
=
This is a new upstream release, with release notes listed below. See also
the package documentation in /usr/share/doc/asciidoc/.
DESCRIPTION:
AsciiDoc is a text document format for writing short documents, articles,
books and UNIX man pages. AsciiDoc files can be translated to HTML and
DocBook markups using the asciidoc(1) command. AsciiDoc is highly
configurable: both the AsciiDoc source file syntax and the backend output
markups (which can be almost any type of SGML/XML markup) can be
customized and extended by the user.
UPDATE:
===
To update your installation, click on the Install Cygwin now link on the
http://cygwin.com/ web page. This downloads setup.exe to your system.
Save it and run setup, answer the questions and pick up 'asciidoc' from
the 'Devel' category.
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations. This means that you will need to
find a mirror which has this update, please choose the one nearest to you:
http://cygwin.com/mirrors.html
QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.
--
Eric Blake
volunteer cygwin asciidoc maintainer
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO:
=
To unsubscribe to the cygwin-announce mailing list, look at the
List-Unsubscribe: tag in the email header of this message. Send email
to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
1. Version 8.5.2 (2009-12-09)
Additions and changes
* Added Italian language configuration file (contributed by Fabio
Inguaggiato).
* Added header table style. See:
[1]http://groups.google.com/group/asciidoc/browse_frm/thread/a23fea
28394c8ca9
* Pass icons, data-uri, imagesdir, iconsdir attributes to asciidoc
table style filter so that images are rendered in table cells.
* Pass trace and verbose attributes to asciidoc table style filter so
diagnostic information is printed from table cell source.
* The eval system attribute can be nested inside other system
attributes.
* HTML outputs: Table and figure caption punctuation set to more
usual syntax.
* docbook backend: footnotes can now contain embedded images. See
[2]http://groups.google.com/group/asciidoc/browse_frm/thread/50b28f
6941de111a
* CSS tweaks so that tables processed by DocBook XSL Stylesheets have
the default asciidoc xhtml11 backend styling. See
[3]http://groups.google.com/group/asciidoc/browse_frm/thread/dfe520
4d5b2c9685
* Block titles take precedence over section titles to avoid titled
delimited blocks being mistaken for two line section titles (see
[4]http://groups.google.com/group/asciidoc/browse_frm/thread/f0b6f9
989f828c3).
* Section title trace displays level and title text.
* FAQ additions.
* Added {zwsp} (zero width space) attribute.
* Undefined paragraph styles are reported (previously threw a runtime
error).
* Eliminated empty preamble generation.
* Floating titles now processed in all contexts.
* Implemented auto-lettered appendix names and updated example
documents.
* Section numbering can be disabled in HTML outputs with a
:numbered!: AttributeEntry.
* xhtml11: Nicer default quote block styling.
* Exclude floating titles from xhtml11 table of contents. Patch
submitted by Mark Burton (see
[5]http://groups.google.com/group/asciidoc/browse_frm/thread/14aefc
1cb6bd85f5).
* Enhanced doc/article-docinfo.xml example docinfo file.
* Vim syntax highlighter improvements.
Bug fixes
* FIXED: Absolute imagesdir and iconsdir attribute path names do not
work with the xhtml11 data-uri encoding. See
[6]http://groups.google.com/group/asciidoc/browse_frm/thread/cb8b76
94bbc82a6
* FIXED: Regression issue with inline data-uri images. See
[7]http://groups.google.com/group/asciidoc/browse_frm/thread/cb8b76
94bbc82a6
* FIXED: An unexpected error occurred when processing a table
containing CSV data if the cols attribute was not explicitly
specified. See
[8]http://groups.google.com/group/asciidoc/browse_frm/thread/4b0f36
4b477ec165
__
2. Version 8.5.1 (2009-10-31)
Additions and changes
* If an AsciiDoc document file begins with a UTF-8 BOM (byte order
mark) then it is
Updated: sharutils-4.7-2
A new release of sharutils, 4.7-2, is available, leaving 4.6.3-1 as previous. NEWS: = This is an update to build against cygwin 1.7, using gcc 4, and to update the documentation layout to match recommended practice. Using shar on text mounts continues to have the possibility that line endings on text files might not be handled the way you want, but if it was truly a text file, that should not matter to you; the heuristic that shar uses to decide between text and binary files is whether it contains non-printing characters. It is safer to use shar/unshar on binary mounts (remembering that unshar is inherently unsafe). uuencode and uudecode, on the other hand, work reliably regardless of the underlying mount point. See also the package documentation found in /usr/share/doc/sharutils/. DESCRIPTION: The sharutils package contains the GNU shar utilities, a set of tools for encoding and decoding packages of files (in binary or text format) in a special plain text format called shell archives (shar). This format can be sent through e-mail (which can be problematic for regular binary files). The shar utility supports a wide range of capabilities (compressing, uuencoding, splitting long files for multi-part mailings, providing checksums), which make it very flexible at creating shar files. After the files have been sent, the unshar tool scans mail messages looking for shar files. Unshar automatically strips off mail headers and introductory text and then unpacks the shar files. Note that unshar is inherently unsafe by design, because it executes arbitrary shell scripts; therefore the creation of shar archives should be limited to situations where the receiver trusts the sender. However, uuencode and uudecode are useful in their own right, and are safe to use. UPDATE: === To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'sharutils' from the 'Archive' category. DOWNLOAD: = Note that downloads from cygwin.com aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- Eric Blake volunteer cygwin sharutils maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
