pgmtolispm(1) General Commands Manual pgmtolispm(1)NAME
pgmtolispm - convert a portable graymap into Lisp Machine format
SYNOPSIS
pgmtolispm [pgmfile]
DESCRIPTION
Reads a portable graymap as input. Produces a Lisp Machine bitmap as output.
This is the file format read by the tv:read-bit-array-file function on TI Explorer and Symbolics lisp machines.
Given a pgm (instead of a pbm) a multi-plane image will be output. This is probably not useful unless you have a color lisp machine.
Multi-plane bitmaps on lisp machines are color; but the lispm image file format does not include a color map, so we must treat it as a
graymap instead. This is unfortunate.
SEE ALSO lispmtopgm(1), pgm(5)BUGS
Output width is always rounded up to the nearest multiple of 32; this might not always be what you want, but it probably is (arrays which
are not modulo 32 cannot be passed to the Lispm BITBLT function, and thus cannot easily be displayed on the screen).
No color.
AUTHOR
Copyright (C) 1991 by Jamie Zawinski and Jef Poskanzer.
06 March 1990 pgmtolispm(1)
Check Out this Related Man Page
lispmtopgm(1) General Commands Manual lispmtopgm(1)NAME
lispmtopgm - convert a Lisp Machine bitmap file into pgm format
SYNOPSIS
lispmtopgm [lispmfile]
DESCRIPTION
Reads a Lisp Machine bitmap as input. Produces a portable graymap as output.
This is the file format written by the tv:write-bit-array-file function on TI Explorer and Symbolics lisp machines.
Multi-plane bitmaps on lisp machines are color; but the lispm image file format does not include a color map, so we must treat it as a
graymap instead. This is unfortunate.
SEE ALSO pgmtolispm(1), pgm(5)BUGS
The Lispm bitmap file format is a bit quirky; Usually the image in the file has its width rounded up to the next higher multiple of 32,
but not always. If the width is not a multiple of 32, we don't deal with it properly, but because of the Lispm microcode, such arrays are
probably not image data anyway.
Also, the lispm code for saving bitmaps has a bug, in that if you are writing a bitmap which is not mod32 across, the file may be up to 7
bits too short! They round down instead of up, and we don't handle this bug gracefully.
No color.
AUTHOR
Copyright (C) 1991 by Jamie Zawinski and Jef Poskanzer.
06 March 1990 lispmtopgm(1)
There is no xorg.conf file and no XF86Config file on a certain FreeBSD machine:
# locate xorg.conf
/usr/local/man/man5/xorg.conf.5.gz
# locate XF86Config
#
Can someone let me know if that means that there is a bare bones set up possible only? xrandr works fine, but I am looking for ways to... (6 Replies)
I'm looking for finer granularity than the 20 ANSI escape sequence screen modes. What I'd like to do is have the terminal increase it's own height when I have to show the user a long menu.
Platform is Cygwin 64 running over Win 7 Pro.
Mike (4 Replies)
What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file.
# When the shell exits, append to the history file instead of overwriting it
shopt -s histappend (3 Replies)
Look this very good rendering on Slackware 14.2
in my opinion is near perfect.
https://i.stack.imgur.com/q5trL.png
Now look the same page on Fedora 30
https://i.stack.imgur.com/FBQv7.png
In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of... (20 Replies)