Hello All, I have been used to invoking Ghostscript to display my postscript efforts on this Thinkpad running Ubuntu, but it did not do so with the "fresh" desktop install of Debian. I have looked at the default output device on this Thinkpad, and it is x11alpha, but that appears to not be available with the Debian installed version of Ghostscript. I would appreciate pointers as to enabling that, even if I have to grab the source via this computer, then transfer via CDR and compile. The desktop will be on the net in due course, but it is dial up access, and I am still looking closely at being able to disable Gnome Netmanager in such a way that I can still learn about it for when I install for novices. It does not appear cleanly in Synaptic, but I can see parts of it. I have been scratching my ead as to what is the "head" of the app, where I should start, rather than a piecemeal approach. I also need to have the head space to sort out setting up pon and poff, rather than using wvdial as I have been. Meatspace has been of higher priority at this time. Regards, Mark Trickett
Mark Trickett <marktrickett@bigpond.com> wrote:
I have been used to invoking Ghostscript to display my postscript efforts on this Thinkpad running Ubuntu, but it did not do so with the "fresh" desktop install of Debian. I have looked at the default output device on this Thinkpad, and it is x11alpha, but that appears to not be available with the Debian installed version of Ghostscript.
Is the ghostscript-x package installed? Does it help? See below. Package: ghostscript-x New: yes State: installed Automatically installed: yes Version: 9.05~dfsg-6 Priority: optional Section: text Maintainer: Debian Printing Team <debian-printing@lists.debian.org> Architecture: amd64 Uncompressed Size: 198 k Depends: libc6 (>= 2.7), libice6 (>= 1:1.0.0), libsm6, libx11-6, libxext6, libxt6, ghostscript (= 9.05~dfsg-6) Description: interpreter for the PostScript language and for PDF - X11 support GPL Ghostscript is used for PostScript/PDF preview and printing. Usually as a back-end to a program such as ghostview, it can display PostScript and PDF documents in an X11 environment. This package contains the GPL Ghostscript output device for X11. Homepage: http://www.ghostscript.com/
Jason White wrote:
Mark Trickett <marktrickett@bigpond.com> wrote:
I have been used to invoking Ghostscript to display my postscript efforts on this Thinkpad running Ubuntu, but it did not do so with the "fresh" desktop install of Debian. I have looked at the default output device on this Thinkpad, and it is x11alpha, but that appears to not be available with the Debian installed version of Ghostscript.
Is the ghostscript-x package installed?
As the more general heuristic, what I would be doing in such a scenario is looking at aptitude search ?source-package(foo) when foo isn't working, and looking at unmet Recommends dependencies of installed packages. $ aptitude search '?source-package(ghostscript)' i A ghostscript - interpreter for the PostScript language an p ghostscript-cups - interpreter for the PostScript language an p ghostscript-dbg - interpreter for the PostScript language an p ghostscript-doc - interpreter for the PostScript language an p ghostscript-x - interpreter for the PostScript language an p libgs-dev - interpreter for the PostScript language an i A libgs9 - interpreter for the PostScript language an i A libgs9-common - interpreter for the PostScript language an
Hello Trent and Jason, On Mon, 2012-09-10 at 12:29 +1000, Trent W. Buck wrote:
Jason White wrote:
Mark Trickett <marktrickett@bigpond.com> wrote:
I have been used to invoking Ghostscript to display my postscript efforts on this Thinkpad running Ubuntu, but it did not do so with the "fresh" desktop install of Debian. I have looked at the default output device on this Thinkpad, and it is x11alpha, but that appears to not be available with the Debian installed version of Ghostscript.
Is the ghostscript-x package installed?
I still need to set up net access, it was only the defaults from the DVD that were installed at this point. That is why I made comments about setting up dial up and ppp via pon and poff. I repeat that other meat space commitments are keeping me from an adequate examination of getting that right. I need to refresh my shell scripting, and to learn sed and the like.
As the more general heuristic, what I would be doing in such a scenario is looking at aptitude search ?source-package(foo) when foo isn't working, and looking at unmet Recommends dependencies of installed packages.
$ aptitude search '?source-package(ghostscript)' i A ghostscript - interpreter for the PostScript language an p ghostscript-cups - interpreter for the PostScript language an p ghostscript-dbg - interpreter for the PostScript language an p ghostscript-doc - interpreter for the PostScript language an p ghostscript-x - interpreter for the PostScript language an p libgs-dev - interpreter for the PostScript language an i A libgs9 - interpreter for the PostScript language an i A libgs9-common - interpreter for the PostScript language an
That too is interesting, while I was scratching around, some of the documentation files were mentioned, but not present. One trouble is that unless I use the commands and options reasonably regularly, I will forget them. I know quite a lot of looking things up, but sometimes I still need prompting, including the appropriate technical terms. Regards, Mark Trickett
Mark Trickett <marktrickett@bigpond.com> wrote:
On Mon, 2012-09-10 at 12:29 +1000, Trent W. Buck wrote:
As the more general heuristic, what I would be doing in such a scenario is looking at aptitude search ?source-package(foo) when foo isn't working, and looking at unmet Recommends dependencies of installed packages.
That's excellent advice.
That too is interesting, while I was scratching around, some of the documentation files were mentioned, but not present. One trouble is that unless I use the commands and options reasonably regularly, I will forget them. I know quite a lot of looking things up, but sometimes I still need prompting, including the appropriate technical terms.
Aliases and shell scripts can help you to automate and simplify complex commands, or complex sequences of commands. Also remember man -k, and maybe it would be a good idea to install the debian-handbook package (a very recent addition to the distribution) and then refer your Web browser to file://localhost/usr/share/doc/debian-handbook/html/index.html Often, reading a coherent discussion in a book makes it easier to remember commands and technical terms, while providing a better technical foundation of knowledge in the subject.
Jason White wrote:
Also remember man -k
a.k.a. "apropos"; probably because GNU stole the idiom from Lisp.
file://localhost/usr/share/doc/debian-handbook/html/index.html
Probably available online as well, for the lazy. Of course, that won't necessarily reflect the release you're using...
On Tue, 11 Sep 2012, Trent W. Buck wrote:
Probably available online as well, for the lazy. Of course, that won't necessarily reflect the release you're using...
http://www.freebsd.org/cgi/man.cgi Has *BSDs, CentOS and SuSE Linux, plus HP/UX and Solaris. Just Debian/Ubuntu missing: http://manpages.debian.net/ http://manpages.ubuntu.com/ Of course, there are always others but it may fit 95% of the Linux users. Regards Peter
Peter Ross wrote:
On Tue, 11 Sep 2012, Trent W. Buck wrote:
Probably available online as well, for the lazy. Of course, that won't necessarily reflect the release you're using...
http://www.freebsd.org/cgi/man.cgi [et cetera]
I was actually referring to the Debian Handbook.
Trent W. Buck <trentbuck@gmail.com> wrote:
I was actually referring to the Debian Handbook.
Plainly so. http://debian-handbook.info/
participants (4)
-
Jason White -
Mark Trickett -
Peter Ross -
Trent W. Buck