-
The same problem occurs with 2.8 Beta 5 Net Installer.
2009-08-08 01:59:37 UTC in MiKTeX
-
2.8 Beta 4 Net Installer, while downloading local repository for MikTeX Basic, aborts after a minute or so with error message: "The operation could not be completed because a required file does not exist". Rerunning Net Installer gives the same result. See attached log file.
2009-08-06 20:38:34 UTC in MiKTeX
-
An isolated Carriage Return (without following Line Feed) in the clipboard is changed to CRLF when pasted into Notepad++.
Likewise, an isolated LF (without preceeding CR) in the clipboard is changed to CRLF when pasted into Notepad++.
To reproduce bug, enter e.g. eeee LF eeee into Notepad++ with "Show End of Line" selected. Then copy this text and paste it elsewhere in the same file. The...
2008-12-18 08:37:30 UTC in Notepad++
-
Hi,
WindowManager v1.2 UNI crashes Notepad++ v5.1.1 Unicode when opening any file without a file extension. (E.g. rename any textfile foo.txt to foo and try to open it with Notepad++.)
CPU: Athlon 2000+
OS: Windows 2003 Server sp2 32bit
Thanks very much for WindowManager.
Friendly Greetings,
Larry.
2008-11-22 07:14:11 UTC in Notepad++
-
Documentation update
Updates to Inno Setup 5.1.14 (2007-08-07) our documentation at
http://gnuwin32.sourceforge.net/setup.html.
2007-08-31 01:09:41 UTC in GnuWin
-
Updates http://unattended.sourceforge.net/InnoSetup_Switches_ExitCodes.html to Inno Setup 5.1.14 (2007-08-07)
2007-08-30 23:45:43 UTC in Unattended, A Windows deployment system
-
Configuration: tac 5.3.0.1936 (from GnuWin32 Coreutils 5.3.0.1936) on Windows Server 2003 sp2 x86
Bug: tac 5.3.0.1936 breaks when input file > ~4K piped into standard input
Examples:
1. cat foo | tac > bar
Completely broken regardless of foo's size. Nothing written to bar. Exits with "cat: write error: Invalid argument"
2. cat foo | tac - > bar
a. If foo < ~4K, works fine
b. If...
2007-08-01 18:05:54 UTC in GnuWin
-
Bug: \w (word character) and \W (nonword character) don't function as escapes inside character classes. Inside character classes, sed treats \w as literal `\' followed by literal `w'. Likewise for \W
Example: `echo file~1.txt|sed -r s/[\w~.]+/foo/' returns `filefoo1.txt', not `foo' as expected
Workaround: Inside character classes, replace \w with A-Za-z0-9_ ; e.g. `echo file~1.txt|sed -r...
2007-07-06 05:27:51 UTC in GnuWin
-
Bug: sed-4.1.5 doesn't handle \x5c and \x26 literally. Rather, sed handles these objects the same as the special regex symbols they stand for. Therefore, there is no point in using \x5c or \x26.
1. Sed-4.1.5 treats \x5c as an escape, not a literal `\' as expected
a. Example (matching): `echo path\.ext|sed s/\x5c./#/' returns `path\#ext', not `path#ext' as expected
b. Example (replacement):
2007-07-06 05:25:30 UTC in GnuWin
-
Bug: regex . doesn't match ascii null (\x0) but matches all other extended ascii characters \x1 - \xff.
Consequence: .* (or .+) doesn't match entire line which contains an ascii null.
Example: `echo bar|sed "s/a/\x0/;s/.*/foo/"' returns `foor', not `foo' as expected
Workarounds
1. (exact): replace . with (.|\x0); e.g. `echo bar|sed -r "s/a/\x0/;s/(.|\x0)*/foo/"' returns `foo'
2.
2007-07-06 05:22:37 UTC in GnuWin
