gmane.comp.version-control.darcs.user

Display correctly utf-8 in commit info

xancorreu — 2013-05-08T18:14:33

Hi,

I use utf-8 intensively: in console and in files it's my default encoding.
With export DARCS_DONT_ESCAPE_EXTRA="áàéèíïóúüñÁÀÉÈÍÏÓÒÚÚÑ", export 
DARCS_DONT_ESCAPE_ISPRINT=1
or export DARCS_DONT_ESCAPE_8BIT=1 there is no problem for displaying 
files and diff changes when I run "darcs log --verbose", but the commit 
messages *don't* appear in UTF-8:

$ darcs log --verbose
Sun May 5 22:10:18 CEST 2013 xan< at >localhost
* O no <U+00E9>s aix<U+00ED>
hunk ./holamón.txt 1
-Hola què tal
+Hola què tal. O no és així

Sun May 5 22:05:19 CEST 2013 xan< at >localhost
* Hola m<U+00F3>n
addfile ./holamón.txt
hunk ./holamón.txt 1
+Hola què tal


How can I do for displaying the commit message in UTF-8? With 8BIT=1, I get:

$ darcs log --verbose
Sun May 5 22:10:18 CEST 2013 xan< at >localhost
* O no �s aix
hunk ./holamón.txt 1
-Hola què tal
+Hola què tal. O no és així

Sun May 5 22:05:19 CEST 2013 xan< at >localhost
* Hola m�n
addfile ./holamón.txt
hunk ./holamón.txt 1
+Hola què tal

My darcs versio

Re: Best place for Darcs Hub questions

Simon Michael — 2013-05-02T15:18:29

Hi Ash,

yes, this is the best place for such discussion. Thanks for recording 
the feature on trello also. This is probably the most often requested 
feature at the moment, so I've moved it to the top of the backlog. For 
now deleting the account is your best option (see FAQ). Hopefully 
someone will implement this, or offer a bounty, or figure a procedure I 
can follow as admin, soon.

Best - Simon

GSoC 2013 Darcsden

Joe Nash — 2013-05-01T16:44:53

Hi there,
This project sounds quite interesting and I'd like to write a proposal for
it. Unfortunately I've only just seen the email about the darcs projects
and the deadline is drawing close, and being unfamiliar with the code or
the issue I have no idea where to start!

I'd greatly appreciate more information on this project if any of the
proposers or anyone in the know is reading!

For some background, I'm a second year Computer science student at the
University of Nottingham, and have used Haskell quite extensively in my
degree thus far, with only more to come. Additionally I have a fair bit of
experience with web applications.

Cheers,
Joe Nash
_______________________________________________
darcs-users mailing list
darcs-users< at >darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users

Re: hunk move as primitive change

Ganesh Sittampalam — 2013-05-01T17:27:53

Hi Ben,

On 01/05/2013 00:51, Ben Franksen wrote:


I've wanted this feature for a long time too! I've actually spent some
time thinking about it already - see below.


I agree in principle it's not too hard, but I think there are quite a
few details to get right. One technical issue with commuting hunks in
general is whether to do when two hunks are touching - you want to make
commute succeed in as many situations as possible but not make it ambiguous.

I started working out the rules for commuting hunk move a while ago, and
concluded that there are quite a lot of rules needed for the different
cases - if commuting two hunk move patches on the same file then you
need to worry about the ordering of four different positions in the file
(source and target of each move).

My working view right now is that it's probably best to treat hunk move
as a "cut" and a "paste" operation, internally. [They shouldn't be
exposed to users, otherwise we end up having to manage a clipboard!]

However the rules will still be qu

Re: GSoC 2013 Darcsden

Owen Stephens — 2013-05-01T17:38:18

Hi Joe,

On 1 May 2013 18:25, Joe Nash <joenash< at >blackvine.co.uk> wrote:

First question: are you famililar with darcs? It's not a necessary requirement I
suppose, but it'll certainly be a good start!


Do you use irc? The best thing to do at the moment is probably to hop onto
#darcs on freenode, and say hello! I'm "owst", Simon Michael who's done a lot
of work on darcsden is "sm", come and chat about GSoC, darcs and darcsden. If
not, we can go via email...


Ah cool, did you get taught by Graham Hutton?

Cheers,

Owen.

GSoC 2013 Darcsden

Joe Nash — 2013-05-01T17:25:17

Hi there,
This project sounds quite interesting and I'd like to write a proposal for
it. Unfortunately I've only just seen the email about the darcs projects
and the deadline is drawing close, and being unfamiliar with the code or
the issue I have no idea where to start!

I'd greatly appreciate more information on this project if any of the
proposers or anyone in the know is reading!

For some background, I'm a second year Computer science student at the
University of Nottingham, and have used Haskell quite extensively in my
degree thus far, with only more to come. Additionally I have a fair bit of
experience with web applications.

Cheers,
Joe Nash
_______________________________________________
darcs-users mailing list
darcs-users< at >darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users

Re: hunk move as primitive change

Petr Pudlák — 2013-05-01T07:04:45

Hi,

an excellent idea. It has troubled me for a long time that when someone
moves a piece of code to another file, it's basically impossible to see if
there were any changes in the block or not without a very thorough
examination.

  Best regards,
  Petr


2013/5/1 Ben Franksen <benjamin.franksen< at >bessy.de>

_______________________________________________
darcs-users mailing list
darcs-users< at >darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users

hunk move as primitive change

Ben Franksen — 2013-04-30T23:51:42

Hi Everyone

This is something I have on my wish-list for longer than I can think. The 
idea is quite simple: a primitive change type that says "this sequence of 
lines moved from file X line N to file Y line M". Here, X and Y need not be 
different, i.e. a hunk move need not be between different files.

To my knowledge no existing VCS has such a feature. There are two advantages 
I expect:

(1) Moving code around is something I do regularly in the process of 
cleaning up my (or other's) code. Currently such changes are represented 
(e.g. when using record or whatsnew) as "remove these lines from file X line 
N (long block of code follows), add these lines to file Y line M (another 
long block of code follows)". The remove and insert changes need not even be 
adjacent to one another (they typically are not) and even if they are it is 
very hard for the human eye to spot small differences in a long stretch of 
text. So if the tool told me I have a move (or I could tell it that this is 
the case) then I could

darcs weekly news #103

Guillaume Hoffmann — 2013-04-30T19:26:19

# News and discussions

1.  Darcs will be participating to this year's Google Summer of Code under
    the umbrella of Haskell.org! If you are interested please consult the ideas
    page and contact us:

    -   <http://darcs.net/GSoC>

2.  Sebastian Fischer implemented `darcs-history`, a program to be used as
    darcs posthook and that tracks patch movements inside of a repository:

    -   <http://lists.osuosl.org/pipermail/darcs-devel/2013-February/014754.html>
    -   <http://lists.osuosl.org/pipermail/darcs-devel/2013-February/014898.html>
    -   <http://www.informatik.uni-kiel.de/~sebf/darcs/darcs-history/README.html>

3.  Sebastian also suggested the possibility for darcs to easily split and
    merge patches that are depended upon:

    -   <http://lists.osuosl.org/pipermail/darcs-devel/2013-March/014965.html>

4.  Piyush P Kurur was also interested in some special kinds of deep
    `amend-record`:

    -   <http://lists.osuosl.org/pipermail/darcs-users/2013-March/026838.html>

# Issues resolved i

Re: GSoC Proposal - Better record command

Guillaume Hoffmann — 2013-04-30T15:27:16

Hi everyone,

Marcio told me that he finally will not be able to apply to GSoC this year :-(

The good news is that we have an application that has already received
a good amount of feedback (from Owen but also from me offline), and
that can be reused by anyone who is interested. So please go ahead if
you find the project "better record" interesting!

Guillaume

Re: GSoC Proposal - Better record command

Marcio Díaz — 2013-04-29T17:12:05

Thanks Owen, this was a very good review :)

On Mon, Apr 29, 2013 at 9:45 AM, Owen Stephens <darcs< at >owenstephens.co.uk>wrote:

_______________________________________________
darcs-users mailing list
darcs-users< at >darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users

Re: GSoC Proposal - Better record command

Owen Stephens — 2013-04-29T12:45:21

Hi Marcio,

On 29 April 2013 05:26, Marcio Díaz <marcio.diaz< at >gmail.com> wrote:

Cool! I've added a bunch of comments here:
    https://docs.google.com/document/d/1j3QHm5OdZ_FEgvwdF5cU6WE_bKnHlO4g-HjZJUxchpQ/edit?usp=sharing

Cheers,

Owen.

GSoC Proposal - Better record command

Marcio Díaz — 2013-04-29T04:26:07

Hi everyone, I've uploaded my proposal for the GSoC, you can see it here:

http://darcs.net/GSoC/2013-BetterRecord

I would like to hear your comments.

Marcio.
_______________________________________________
darcs-users mailing list
darcs-users< at >darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users

Best place for Darcs Hub questions

Ash Moran — 2013-04-28T20:03:56

Hi

I've added a card[1] to the Darcs Hub wishlist on Trello (reset password feature). It contains a non-urgent implicit support request (it would be nice if the person I was trying to show a file to could log in before this feature is added). Is darcs-users the best place to raise feature requests etc for Darcs Hub, or should I be sending them somewhere else?

Thanks
Ash

[1] https://trello.com/c/kew04adB

Google Summer of Code

Ganesh Sittampalam — 2013-04-25T06:00:25

Hi,

darcs.net will participating in Google Summer of Code this year, under
the umbrella of haskell.org - Google will be allocating 1 or 2 extra
slots specifically for Darcs.

Time is a little short, as we'd originally thought this arrangement was
coming to an end: the student application deadline is 1900UTC on next
Friday (May 3rd).

Please see http://darcs.net/GSoC for ideas and what to do next if you
are interested in participating. The most important thing is to get in
touch with us informally asap.

Many thanks to Guillaume Hoffmann both for making our initial
application to be a separate organisation (which was unfortunately
rejected), and then for talking to Google and establishing that our
existing arrangement of having a dedicated slot under the haskell.org
umbrella could continue.

Cheers,

Ganesh

Re: some special amend-records

Ganesh Sittampalam — 2013-04-19T22:09:26

Hi Sebastian,

On 19/04/2013 11:07, Sebastian Fischer wrote:


I've removed most of the presumablys to confirm I agree with your
reasoning. I left the one about the usability of darcs changes which is
just a matter of opinion about the UI that I'm not sure about either way.

As I understand the proposal, you plan to split textually independent
changes into separate named patches and then use explicit dependencies
to group those named patches together into the same unit that would
previously have been a single patch.

I think it would be technically feasible as described. The downside
would be that there would be no record at all of any logical
dependencies - so in the example of a new member being added to an
interface along with implementations of that new member, people could
end up with one but not the other.

That lack of dependencies is always a problem with darcs - for example
if in the normal mode of recording, the user first records the addition
of a new function and then in a new patch a use of that

Re: packs

Simon Michael — 2013-04-19T18:16:17

Another interesting data point will be what kind of resources does generating and keeping packs cost in medium/large repos ? In particular, RAM and disk space.

I hope you'll understand and not mind that I push back a little. I am excited about this, it's exactly the sort of hacking darcs hub hopes to encourage (says so right on the front page).

Best
-Simon

packs

Simon Michael — 2013-04-19T18:08:40

Hi BSRK,

On Apr 19, 2013, at 2:38 AM, Aditya wrote:

I think both. With -fdarcs28, darcsden builds (or used to) with released darcs, otherwise it builds with latest darcs-screened. IIRC darcs hub's darcsden is built darcs-screened, to get the latest fixes.


I have been building it with 7.4.2 till now. I'd love to have someone update it for 7.6 so I don't have to.


You don't need to deploy it to hub to test this, but I guess you feel it's ready for wider use. I'm keen to encourage hacking and to deploy things on hub quickly, as long as they don't disrupt ordinary users.


Great, all help is welcome. I'm much more likely to act on a clear list of steps than to do exploratory hacking right now, as I'm about to go on a family trip till the end of the month.


Best - Simon



_______________________________________________
darcs-users mailing list
darcs-users< at >darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users

Re: some special amend-records

Sebastian Fischer — 2013-04-19T10:07:49

Hi Ganesh and David,

I'll restrict my response to a subset of what we discussed because I
have a simpler change in mind that might be sufficient for factis, at
least initially.


I notice that Darcs distinguishes "implicit" and "explicit"
dependencies. However, implicit dependencies are not (always) what I
meant by system dependencies. I have made a wiki page on "essential"
dependencies that (hopefully) clarifies the difference:

    http://darcs.net/Ideas/EssentialDependencies

As far as I can tell, implicit and explicit dependencies have the same
effect in Darcs. Originally, I envisioned system and user dependencies
to have different effects but my new proposal just uses implicit and
explicit dependencies to achieve a similar goal.


The new wiki page proposes a new flag for darcs record that allows to
automatically split recorded patches into unrelated sets of changes
and grouping them using empty patches. I think this reduces the need
to retroactively splitting patches (it would still be impossible - bu

Patch groups - does this makes sense

Piyush P Kurur — 2013-04-18T07:24:53

Here is my impression of patch groups after reading through some of
the mails in this list.

A patch group of order (or type) n, abbreviated as PG(n), is
inductively defined as

1. patch group of order 0 is the actual patches (hunks, addfile etc)

2. A patch group of order n+1 is a collection of patches of order n

What about patch groups of higher order.

PG(1): is a record (collection of PG(0)s or actual patches)

PG(2): is a branch (a collection of PG(1)s or records).

PG(3): is a repository (a collection of PG(2)s or branches).

PG(4): is a team of repository, a group of people who work on a
project.
   
PG(n>4): is something that gives me a headache.


For all PG(n>=0), one should be able to attach meta information.

Operations 
----------

Operations are restricted to certain level of the patch group.  We
have record level operations, branch level operations and may be
repository level operations.

PG(0):

  1. Editing the working copy creates/deletes/modifies them
  2. reverting deletes some of them

Re: some special amend-records

Ganesh Sittampalam — 2013-04-18T06:45:13

Hi Sebastian,

Sorry for the delay replying.

I've snipped quite a bit of the conversation where it's not directly
relevant to my replies, hopefully the discussion still makes sense.

On 09/04/2013 11:57, Sebastian Fischer wrote:

Sure.


Yep - in Darcs as it is now, system dependencies indeed about
automatically and user dependencies can be added with the --ask-deps
flag to record/amend-record.


I'm not sure I see this - in current darcs any user dependency on
"feature and mistake" is permanent in the sense that you can't retract a
published patch; all you can do is submit a new patch that undoes the
mistake. The dependencies will still be there, although perhaps they
won't matter.

If there's a system dependency on the mistake itself then undoing the
mistake becomes a little harder because by definition there's some kind
of conflict - e.g. the mistake added a line of text and the system
dependency is because a further patch edits that line. Undoing the
mistake now requires judgement as to what to do with