* Pavel Roskin [EMAIL PROTECTED] [Mon, 09 Dec 2002]:
Here is the new patch. It allows the user to set the
HISTCONTROL environment variable to a value of ignoredups
if he wants to have only unique entries in history widgets.
Maybe duplicates should be always ignored?
Maybe. The
Adam Byrtek 'alpha' wrote:
On Fri, Dec 13, 2002 at 07:09:27PM +0200, Andrew V. Samoilov wrote:
Perfect and very impressive! Power perl skills!
Thank you very much :)
I do not enforce you to implement context format.
But it will be some regressive and on other hand some projects (Samba as
On Wed, Dec 18, 2002 at 07:45:29PM +0200, Andrew V. Samoilov wrote:
Well, but some quoting (and security) issues fixed in the CVS just now.
Patch attached.
Looks good, thanks.
I need to be more careful when it comes to quoting... looks like I
forget about this too often.
BTW, new incarnation
Hello!
Well, but some quoting (and security) issues fixed in the CVS just now.
Patch attached. BTW, new incarnation reports wrong patch sizes for
gzipped patches.
Just for your information.
Size is not very critical after I disabled fast loading on non-local VFS
in the editor. You can open
BTW, new incarnation reports wrong patch sizes for gzipped patches.
I'll examine this when I have more time.
Regards
You can use ideas from attached file. I eliminated all tell() call and
calculate position itself by adding current line length to some
variable. Patched patchfs list
On Wed, Dec 18, 2002 at 09:26:05PM +0200, Andrew V. Samoilov wrote:
You can use ideas from attached file. I eliminated all tell() call and
calculate position itself by adding current line length to some
This wasn't necessary at all.
The problem was somewhere else: patchfs treated empty
Hello!
This wasn't necessary at all.
The problem was somewhere else: patchfs treated empty line as the diff
boundary, so the size was broken. The fix was really simple.
Sorry, I don't understand why an empty line is not a diff boundary. It's
not valid in diff, as far as I know.
Pavel,
On Wed, Dec 18, 2002 at 06:45:42PM -0500, Pavel Roskin wrote:
Sorry, I don't understand why an empty line is not a diff boundary. It's
not valid in diff, as far as I know.
Yes, it is not a valid diff.
Valid diff puts:
' \n' (space and a newline)
But Andrew gave me a link to a www mailing list
