On Wed, 02 Jul 2014 09:24:39 +, Duncan wrote:
> Duncan posted on Wed, 02 Jul 2014 04:45:39 + as excerpted:
>
>> Now to go create a patch to drop into /etc/portage/patches to
>> auto-apply on rebuild.
>
> Applied (on top of current git):
>
> --- pan/gui/header-pane.cc.old 2014-07-02 01:
Duncan posted on Wed, 02 Jul 2014 04:45:39 + as excerpted:
> Now to go create a patch to drop into /etc/portage/patches to auto-apply
> on rebuild.
Applied (on top of current git):
--- pan/gui/header-pane.cc.old 2014-07-02 01:44:25.0 -0700
+++ pan/gui/header-pane.cc 2014-07-02
walt posted on Tue, 01 Jul 2014 17:54:20 -0700 as excerpted:
> That number is specified in pan's source code, and for exactly the same
> reason I change it myself before I compile pan.
>
> Just in case you know how to build pan from code, the guilty number is
> here:
>
> ~/src/pan2 grep -r small
On 06/30/2014 11:58 AM, Bruce Bowler wrote:
> One group that I participate in has folks who, on occasion, post files
> that are 8000 lines or longer. Invariably, these are screenshots or other
> graphics. Rather than displaying them, pan asks me if I want to save
> them. I don't, I want to di
Bruce Bowler posted on Mon, 30 Jun 2014 18:58:43 + as excerpted:
> One group that I participate in has folks who, on occasion, post files
> that are 8000 lines or longer. Invariably, these are screenshots or
> other graphics. Rather than displaying them, pan asks me if I want to
> save them.
One group that I participate in has folks who, on occasion, post files
that are 8000 lines or longer. Invariably, these are screenshots or other
graphics. Rather than displaying them, pan asks me if I want to save
them. I don't, I want to display them in pan (shorter sceenshots do
display OK
