unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Anand Tamariya <atamariya@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [Patch] Basic WYSIWYG printing in GNU Emacs
Date: Thu, 12 Aug 2021 11:08:22 +0300	[thread overview]
Message-ID: <835ywbdr0p.fsf@gnu.org> (raw)
In-Reply-To: <CADm7Y4moLSHg5nUwd_nYHYmnz_1ofQTUVAniTk7QJ4yKB2BcWw@mail.gmail.com> (message from Anand Tamariya on Thu, 12 Aug 2021 12:15:53 +0530)

> From: Anand Tamariya <atamariya@gmail.com>
> Date: Thu, 12 Aug 2021 12:15:53 +0530
> Cc: emacs-devel@gnu.org
> 
>  But the original question still stands: where do you make use of
>  Ghostscript in your code which generates the PS file?
> 
> I don't. 
> 
>    Or maybe you
>  don't use Ghostscript for that (which would be good news), and I just
>  misunderstood you did?  IOW, is Ghostscript a prerequisite for using
>  your WYSIWYG printing code to produce the PS stuff (as opposed to
>  sending the PS to the printer)?
> 
> It's not. It is only required if one wants to visualize (print preview) it within Emacs. Of course, for
> development and testing, it's irreplaceable unless you want to waste reams of paper. Hence, I count it as a
> dependency.

Thanks, and sorry for my confusion about this aspect.



      reply	other threads:[~2021-08-12  8:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10  9:29 [Patch] Basic WYSIWYG printing in GNU Emacs Anand Tamariya
2021-08-10 12:31 ` Eli Zaretskii
2021-08-10 18:12   ` Pankaj Jangid
2021-08-11  3:39     ` Anand Tamariya
2021-08-11  4:32   ` Anand Tamariya
2021-08-11 11:41     ` Eli Zaretskii
2021-08-11 15:49       ` Anand Tamariya
2021-08-11 16:51         ` Eli Zaretskii
2021-08-11 16:58           ` Eli Zaretskii
2021-08-12  5:34           ` Anand Tamariya
2021-08-12  6:11             ` Eli Zaretskii
2021-08-12  6:45               ` Anand Tamariya
2021-08-12  8:08                 ` Eli Zaretskii [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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=835ywbdr0p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=atamariya@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).