Numerous linux hangovers?

[Snowhog]

If you want to see what kernels are install, use dpkg -l and grep to see what's installed. Something like:

dpkg -l |grep -E "^[^rc]" | awk '{print $2}'

I use:

dpkg --list | awk '/linux-image/ {print $2}'

[chimak111]

I have "apt list --installed | grep -i" aliased to "apli" and so

apli linux-image

works for me.

[chimak111]

@kubicle, I have yet another question about your script!

Since I don't have any "rc" files left, I'm using

PCKGS=$(COLUMNS=200 dpkg -l | grep breeze | tr -s ' ' | cut -d ' ' -f 2)

instead of

PCKGS=$(COLUMNS=200 dpkg -l | grep "^rc" | tr -s ' ' | cut -d ' ' -f 2)

to ask my question.

First, I run

COLUMNS=200 dpkg -l | grep breeze | tr -s ' ' | cut -d ' ' -f 2 > ~/Desktop/breeze.txt

I open ~/Desktop/breeze.txt in vim. Each line ends with a pilcrow (?) and there's no space immediately before the pilcrow as seen in the image:



Now, I run

PCKGS=$(COLUMNS=200 dpkg -l | grep "^rc" | tr -s ' ' | cut -d ' ' -f 2)

and follow that with

echo ${PCKGS}

which gives me:

breeze breeze-cursor-theme breeze-gtk-theme breeze-icon-theme kde-style-breeze kwin-style-breeze libreoffice-style-breeze sddm-theme-breeze

The question: how do spaces appear between the package names? What does "echo ${PCKGS}" do to convert the "one package name per line" (as seen in the image) to the single line output with package names separated by spaces?

[kubicle]

The question: how do spaces appear between the package names? What does "echo ${PCKGS}" do to convert the "one package name per line" (as seen in the image) to the single line output with package names separated by spaces?

If you wish to preserve control chars, you'd put the variable in double quotes, otherwise they are replaced by spaces.
echo "${PCKGS}" vs. echo ${PCKGS}

[chimak111]

If you wish to preserve control chars, you'd put the variable in double quotes, otherwise they are replaced by spaces.
echo "${PCKGS}" vs. echo ${PCKGS}

Okay, thanks! So many intricacies

[jlittle]

Each line ends with a pilcrow (?) ...

Taking that question mark as implying a question, your .vimrc (or some other rc file) includes something like

set nu list lcs=eol:?

to make visible the line numbers and the ends of lines.

[chimak111]

Taking that question mark as implying a question, your .vimrc (or some other rc file) includes something like

set nu list lcs=eol:?

to make visible the line numbers and the ends of lines.

Thanks!

I have

set list listchars=tab:→\ ,nbsp:␣,eol:?

in my .vimrc. My sticking the "?" in the earlier post was because I wasn't sure whether the ? was an end-of-line or carriage return or "\n". I'm don't know how/whether those differ and are to be termed.