lpq should separate its columns #117

Closed
michaelrsweet opened this Issue May 21, 2003 · 4 comments

Comments

Projects
None yet
1 participant
Collaborator

michaelrsweet commented May 21, 2003

Version: 1.1.18
CUPS.org User: litauer.uni-koblenz

Environment: Suse 8.2, samba 2.2.8a

lpq doesn't separate the output columns if username is longer or equal 8 characters or if the printed files exceeds 30 characters. This causes samba to ignore these lines while sumbitting the printers queue to a windows client.

It would be nice if:
1.) lpq outputs the complete username, not just 8 characters as a maximum.
2.) lpq separates its columns by a space or a tab-character.

Example output:
f112 is ready and printing
Rank Owner Job File(s) Total Size
active yvonnel 14190 http://www.uni-koblenz.de/~kgt/.308224 bytes
1st zillge 14191 Microsoft Word - Dokument1 495616 bytes
2nd waldfee 14195 http://www.uni-koblenz.de/~gpste562176 bytes
3rd susiweb 14200 http://www.paritaet.org/asbh/bri220160 bytes
4th ohamann 14203 Microsoft PowerPoint - Präsentat1256448 bytes
5th natiklei14206 Microsoft Word - Referat Schunte337920 bytes
6th natiklei14207 Microsoft Word - Referat Schunte225280 bytes

Collaborator

michaelrsweet commented May 21, 2003

CUPS.org User: mike

Unfortunately, the current ("standard") lpq output format is used by several applications, so it is not possible to change it without causing serious compatibility problems.

Collaborator

michaelrsweet commented May 21, 2003

CUPS.org User: litauer.uni-koblenz

Causes it compatibility problems if the columns still have fixed widths, but you decrement the number of characters per column with one and insert a blank instead?

Collaborator

michaelrsweet commented May 21, 2003

CUPS.org User: mike

No, that would probably work; the current behavior duplicates the problem that occurs with the standard Berkeley lpq command...

Collaborator

michaelrsweet commented May 22, 2003

CUPS.org User: mike

Fixed in CVS for 1.1.19.

michaelrsweet added this to the Stable milestone Mar 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment