caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] llpp
Date: Sun, 13 Jun 2010 00:54:36 +0400 (MSD)	[thread overview]
Message-ID: <alpine.LNX.2.00.1006130053120.11824@linmac> (raw)
In-Reply-To: <4C13F2F1.9070508@gmail.com>

On Sat, 12 Jun 2010, T?r?k Edwin wrote:

> On 06/12/2010 09:36 PM, malc wrote:
> > Hello,
> > 
> > Long story cut short: the PDF viewers that are available for my machine
> > leave a lot to be desired for my usage pattern, so i had to write yet
> > another, the code is at:
> > 
> > http://repo.or.cz/w/llpp.git
> > 
> > http://repo.or.cz/w/llpp.git/blob_plain/master:/BUILDING explains how to
> > build it.
> > 
> 
> Appears to be working fine so far, and much faster than okular.
> 
> Two minor issues:
> 1. The mupdf from sumatrapdf installs fitz.h and mupdf.h directly into
> /usr/local/include, and not under fitz/, or mupdf/, so llpp failed to
> compile. I fixed by copying the headers to where llpp expected them to be.

I was a nanometer away from typing: please edit build.sh to match your
mupdf installation(or lack there of) into BUILDING, but then didn't,
sigh...

> 2. It segfaults if the file is not found, fix below:
> diff --git a/link.c b/link.c
> index 7ca7684..7dab233 100644
> --- a/link.c
> +++ b/link.c
> @@ -177,7 +177,8 @@ static void __attribute__ ((format (printf, 2, 3)))
>  static void die (fz_error error)
>  {
>      fz_catch (error, "aborting");
> -    pdf_closexref (state.xref);
> +    if (state.xref)
> +       pdf_closexref (state.xref);
>      exit (1);
>  }
> 

Thank you.

-- 
mailto:av1474@comtv.ru


  reply	other threads:[~2010-06-12 20:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12 18:36 malc
2010-06-12 20:49 ` [Caml-list] " Török Edwin
2010-06-12 20:54   ` malc [this message]
2010-06-12 21:00     ` bluestorm
2010-06-12 21:07       ` malc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.00.1006130053120.11824@linmac \
    --to=av1474@comtv.ru \
    --cc=caml-list@yquem.inria.fr \
    --cc=edwintorok@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).