If the hunk is so large that it scrolls off my screen then I don't know what
file (or line number) it is from.  Perhaps darcs ought to print the hunk
contents and *then* the hunk meta-data.

On Jan 5, 2006, at 7:41 AM, Zooko wrote:

>
> New submission from Zooko <zooko@zooko.com>:
>
> If the hunk is so large that it scrolls off my screen then I don't  
> know what
> file (or line number) it is from.  Perhaps darcs ought to print the  
> hunk
> contents and *then* the hunk meta-data.

I second this change,  but there are a few problems:

1) Tools which parse the output of darcs (including darcs own  
testsuite) need to be updated.

2) Currently what you see on the screen is also what darcs puts into  
the patch files.  This is a pretty minor problem I think...I think we  
could just need a new show function for printing to the screen and  
continue to use the existing stuff when writing the patch files.

Jason

I think if we fix issue610, making appropriate use of a $PAGER, then I don't
think this change will be necessary.

I nominate this issue for "wont-fix", feeling like the change seems somewhat
arbitrary, and may confuse or break users who expect the current behavior.

On Wed, Feb 06, 2008 at 04:29:39 -0000, Mark Stosberg wrote:
> I think if we fix issue610, making appropriate use of a $PAGER, then I don't
> think this change will be necessary.

Note that interactive mode now has a 'p' command to pass patches through
$PAGER

After reviewing the new "p for pager" functionality, I nominate this request for
being considered resolved-in-unstable, since it addresses the underlying
interest in being able to find the file-name that goes with a hunk.

Okay, thanks for granting my wish!