Hi,
Bernd Warken wrote:
> I did not have any trouble with my Debian version. This bug is not
> part of groffer. A bug report to evince telling them the erroneous
> version of evince would make more sense.
It is not a bug. It is the normal behaviour on some very popular
systems. evince is not
> Von: "Blake McBride"
> Having less control over evince and all the other programs that have this
> (very sensible) behaviour, I think groffer should have an option to not
> delete the temporary files. Perhaps possible future evocations of groffer
> by the same user could delete old temp files.
Having less control over evince and all the other programs that have this
(very sensible) behaviour, I think groffer should have an option to not
delete the temporary files. Perhaps possible future evocations of groffer
by the same user could delete old temp files.
Blake McBride
On Mon, Aug 3, 2
Hi,
> OK, Kal is back from lunch on #evince. There isn't a command-line
> option to make #2 not exit. #2 hands the work over to #1 using D-Bus.
>
> http://en.wikipedia.org/wiki/D-Bus
>
> If evince is compiled without D-Bus support, each evince will act
> independently. I'd guess that wou
Hi,
> Whatever the reason for the differences we're seeing, it seems clear
> that this is what's making evince unsuitable for use with groffer for
> Blake unless he stops groff deleting the temporary file. Perhaps
> there's some option to evince that'll make #2 do the work itself, as
> if it cou
Hi,
Bernd Warken wrote:
> I tried that with groff 1.18.1 of Debian testing and the actual
> CVS-code of 1.20.1. In both variations, xour groffer command worked
> without problems. The temporary file was not deleted. even wtih
> several evince programs running.
>
> Maybe your evince version is b
On 02-Aug-09 23:32:27, Blake McBride wrote:
> On Sun, Aug 2, 2009 at 2:34 PM, Ted Harding
> wrote:
>
>> On 02-Aug-09 19:20:39, Bernd Warken wrote:
>> >> Von: "Blake McBride"
>> > T> groffer --ps --ps-viewer evince groff
>> >> It doesn't display the pages (although "evince file.ps" works
>> >
On Sun, Aug 2, 2009 at 2:34 PM, Ted Harding wrote:
> On 02-Aug-09 19:20:39, Bernd Warken wrote:
> >> Von: "Blake McBride"
> > T> groffer --ps --ps-viewer evince groff
> >> It doesn't display the pages (although "evince file.ps" works fine).
> >
> > I tried that with groff 1.18.1 of Debian te
When I look at Help / About I get (after typing 'evince'):
Document Viewer 2.26.1
Using poppler 0.15.5 (cairo)
The evince authors
I am using the latest version of Ubuntu Linux (9.04).
Just, FYI.
Blake McBride
On 02-Aug-09 19:20:39, Bernd Warken wrote:
>> Von: "Blake McBride"
> T> groffer --ps --ps-viewer evince groff
>> It doesn't display the pages (although "evince file.ps" works fine).
>
> I tried that with groff 1.18.1 of Debian testing and the actual
> CVS-code of 1.20.1.
> In both variations
> Von: "Blake McBride"
T> groffer --ps --ps-viewer evince groff
>
> It doesn't display the pages (although "evince file.ps" works fine).
I tried that with groff 1.18.1 of Debian testing and the actual CVS-code of
1.20.1.
In both variations, xour groffer command worked without problems. Th
Hi Blake,
> Digging in a little it seems that evince is passed a postscript file
> made in a temporary directory created in /tmp. The problem is that
> that directory seems to have been removed, thus evince couldn't
> display anything. Interestingly, if I do:
>
> groffer --ps --ps-viewer
Greetings,
I am having some trouble with groffer that I haven't been able to figure our
too easily. If I do:
groffer --ps --ps-viewer gv groff
everything works fine. But if I do:
groffer --ps --ps-viewer evince groff
It doesn't display the pages (although "evince file.ps" works fine
13 matches
Mail list logo
