From: covici@ccs.covici.com
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 17059@debbugs.gnu.org
Subject: bug#17059: 24.3; cannot view extracted text for a pdf
Date: Sat, 31 May 2014 03:17:41 -0400 [thread overview]
Message-ID: <6988.1401520661@ccs.covici.com> (raw)
In-Reply-To: <jwv4n06d7ya.fsf-monnier+bug#17059@gnu.org>
I am not in an X terminal when I do this, I am in an actual virtual
console. I also tried this under Ubuntu 14.04 and got the same results.
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > go into emacs. I will enclose my .emacs or attach.
> [...]
> > Then find a pdf with text.
>
> What does "with text" mean, here?
>
> > In emacs23 you immediately get the unable to render file prompt.
>
> Hmm... no I get to see the PDF rendered by ghostscript.
>
> > In 24, you get the pdf raw.
>
> Hmm... no I get to see the PDF rendered by ghostscript.
>
> > By the way, this is done from a text console.
>
> Ah, now you tell us. OK, starting over:
>
> > In emacs23 you immediately get the unable to render file prompt.
>
> Indeed, and it prompts me if I want to see the extracted text (I said
> yes, and it did show me the text).
>
> > In 24, you get the pdf raw.
>
> Indeed. I can't remember this being a conscious change, so it looks
> like a bug.
>
> > Now do escape-x and type docview-mode.
> > Now you get the unable to render file prompt.
>
> Yup, I get that too.
>
> > When you hit y to the view extracted text instead, you get the
> > following: DocView: process pdf->txt changed status to killed.
>
> Hmmm... I don't see that here (with Debian's "emacs24 -nw -Q foo.pdf"),
> it shows me the extracted text just fine.
>
>
> Stefan
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
prev parent reply other threads:[~2014-05-31 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 15:46 bug#17059: 24.3; cannot view extracted text for a pdf John Covici
2014-05-31 2:06 ` Stefan Monnier
2014-05-31 7:17 ` covici [this message]
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=6988.1401520661@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=17059@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.