[sf-lug] NEED INFO ABOUT BOOT SECTOR, SPACE LIMITS

Alex Kleider akleider at sonic.net
Wed Aug 2 09:58:47 PDT 2017


On 2017-08-01 10:51, Rick Moen wrote:
> Quoting Daniel Gimpelevich (daniel at gimpelevich.san-francisco.ca.us):
> 
>> In the steps I gave, I piped dpkg -l through cat because it apparently
>> detects the number of columns from the tty that is stdout, and not 
>> from
>> a pipe, e.g. to less or cat.
> 
> Well, OK, but in my experience, 'dpkg -l | less' works just great
> provided you run it in a terminal 80 columns (or more) wide, so my 
> point
> to Alex is that I'm puzzled he perceives a problem he needs scripting 
> to
> solve.

The problem I was trying to solve is that the long lines get carried 
over to the next line so the ability to scan down columns is disrupted 
by 'spilled' lines.  Your
COLUMNS=$COLUMNS dpkg -l | less
command fixes that (by making the columns narrower with the result that 
lines don't spill past 150 chars per line) but I don't understand how- 
the question asked in another email.)


> 
> No special steps should be required at all, is my point.  Just have an
> adequately wide terminal, nothing more.  If there's a problem you see,
> then maybe your terminal is screwed up and you should be fixing _that_
> instead.
> 
> 
> 
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/<br>
> Related Information <br>
> http://www.shallowsky.com/blog/<br>
> http://explainshell.com/ <br>



More information about the sf-lug mailing list