From: Vibhav Pant <vibhavp@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 26600@debbugs.gnu.org
Subject: bug#26600: 26.0.50; Compiled ps-print.el is non-functional
Date: Sat, 22 Apr 2017 13:42:27 +0530 [thread overview]
Message-ID: <CA+T2Sh0fxYYi8fVaMFUDpeq0AO7nUFO1953E-DaKyLvYAgcVEw@mail.gmail.com> (raw)
In-Reply-To: <83h91gri2i.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
A certain bytecode bug which might have caused this was fixed just
recently. Could you try `make bootstrap` and see whether the issue still
persists?
On 22-Apr-2017 1:26 PM, "Eli Zaretskii" <eliz@gnu.org> wrote:
> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Date: Sat, 22 Apr 2017 05:41:22 +0200
> >
> > ps-print.el has become non-functional for me in compiled form since some
> > time (days? weeks? ... not much longer). It produces only empty .ps
> > documents.
> >
> > Here is a very simple recipe for emacs -Q (from *scratch*):
> >
> > M-: (require 'ps-print) RET
> >
> > M-: (ps-spool-buffer-with-faces) RET
> >
> > Switch to the buffer *Post Script*. The created document ends with
> >
> >
> > | BeginDoc
> > | %%EndSetup
> > |
> > | %%Trailer
> > | %%Pages: 0
> > |
> > | EndDoc
> > |
> > | %%EOF
> >
> > If I save the buffer to a .ps file and open it with a viewer, I get a
> > blank page.
> >
> > Now I repeat the recipe with the source file ps-print.el loaded. I get
> > the expected result this time. Hmm.
>
> Does the problem go away if you byte-compile ps-print.el with Emacs
> 25?
>
[-- Attachment #2: Type: text/html, Size: 1646 bytes --]
next prev parent reply other threads:[~2017-04-22 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 3:41 bug#26600: 26.0.50; Compiled ps-print.el is non-functional Michael Heerdegen
2017-04-22 7:56 ` Eli Zaretskii
2017-04-22 8:12 ` Vibhav Pant [this message]
2017-04-22 16:40 ` Vibhav Pant
2017-04-22 19:29 ` Eli Zaretskii
2017-04-23 2:24 ` Michael Heerdegen
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=CA+T2Sh0fxYYi8fVaMFUDpeq0AO7nUFO1953E-DaKyLvYAgcVEw@mail.gmail.com \
--to=vibhavp@gmail.com \
--cc=26600@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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.