Re: [darcs-users] new release

Hi all, I may have been a little too optimistic when I said "in the coming days" in that last message :-) I can say now with more confidence that in the coming days, I am actually going to create the 2.14 branch and start the release process. Thanks for your patience. Guillaume 2018-02-07 20:2

Re: [darcs-users] String encoding issue

On Thu, Mar 22, 2018 at 11:29:54AM +, Eric Kow wrote a message of 157 lines which said: > Does setting DARCS_DONT_ESCAPE_8BIT to 1 help? Ah yes, thanks. I then discovered (at the end). Now, everything is fine. IMHO, it could be in the FAQ.

Re: [darcs-users] String encoding issue

Does setting DARCS_DONT_ESCAPE_8BIT to 1 help? On Thu, 22 Mar 2018 at 18:43, Stephane Bortzmeyer wrote: > In the FAQ, I read: > > > http://darcs.net/FAQ#can-i-write-patch-comments-or-have-an-author-name-with-characters-in-the-full-unicode-spectrum > > Can I write patch comments, or have an auth

[darcs-users] String encoding issue

In the FAQ, I read: http://darcs.net/FAQ#can-i-write-patch-comments-or-have-an-author-name-with-characters-in-the-full-unicode-spectrum Can I write patch comments, or have an author name, with characters in the full Unicode spectrum? Darcs agnosticism w/r/t character encodings can be a problem

[darcs-users] Resurrecting a file?

I am wondering if there is a simply way to ressurect a file which has been deleted some times ago. Today, I do a darcs changes (if I remember the file name) or a darcs test (if I don't), find the last patch where the file existed, then do a darcs clone, copy the file to my working copy and darcs ad

Re: [darcs-users] so long and thanks for all the darcs

Am Donnerstag, den 22.03.2018, 09:12 +0900 schrieb Stephen J. Turnbull: > Wolfgang Jeltsch writes: > > > What about double-clicks, which mark the word (in this case, the > > SHA1 hash) under the cursor? > > The discoverability problem (git repositories normally will have > several dangling heads