how to transform a column list into usable command line?

[_______0]

hi,

I want to generate a list of of packages (or any files for that matter) with eix. Currently is possible but if I want to use that list in command line is not possible because it's a column and command line can't process columns.

What I am trying to do is with eix to list packages from a certain category that are NOT installed, but shockingly has options for everything except for 'NOT installed' :/

This list is needed because some packages I want to discard but most not, so eix alone can't do it. I was passing eix to emerge like this emerge `eix fumanchu`.

Anyone know how to transform a list like this:

[kimmie]

When you use bash command substitution $(..) (or even the old shell backticks `..`), all whitespace is coalesced to single spaces. Newlines are treated as whitespace, so they disappear.

So:

[_______0]

amazing it works!!

thanks a lot.

just one more thing. Why can't command line process columns? Is more natural than serialized items. For example I do ls on a directory with ogg files, then I highlight the list and it becomes a column:

[kimmie]

I see the argument pasting issue as the terminal, the shell and the user all having different views of a stream of text, more than as a flaw in the shell. The terminal is 2D, the shell is 1D, and only you can say whether the end of your selection should terminate the command when pasted....

I think some xterm variants may translate newlines into spaces (I'm not sure which ones, and it probably depends on a using ctrl or alt-paste). Or, app-misc/screen will virtualise your terminal session, and has a vi-like copy mode where you can scroll and search terminal output and also copy and paste. It will do that sort of translation. screen is really handy if you do lots of terminal work, especially if your session is on a remote system. Bit of a learning curve though.

From the shell end, I find myself using cat or xargs fairly often. xargs takes arguments from stdin, and builds a command, so:

[mv]

You should really get used to read manuals. Of course, eix is able to print uninstalled packages (e.g. ... --and --not --installed), and it can produce it in almost any format you want; it could even print you uninstalled slots if you dive into details of the documentation, although this would be a bit more tricky and require to build your custom FORMAT string.

[_______0]

it was tricky though, looks like the option order matters here, by crazy recombination of option I discovered something that appears to yield the proper results:

[mv]

[py-ro]

If you use bash, try CTRL-X CTRL-E, your favorite editor will open and you can paste your arguments easily.

[EDIT]Swapped keys[/EDIT]

[_______0]

[John R. Graham]

TIMTOWTDI. Here're just a few:

From the command line:

[papu]

hi, i like pass to file a list of filter atoms bases/atoms versions , with all dependencies of a previous just installed package.

something like this:

[mv]

The eix --pipe parsing algorithm is quite smart, so you can simply use eix:

[papu]

[mv]

[papu]

[mv]

In general, you can use any of sed, awk, perl (or even python or ruby) for simple modifications of such a type. However, dedicated tools like eix are preferrable if they are suited to your task, because you can expect that they will be adopted to changes of portage. For instance, although it is unfortunate, that just now it turned out that eix has problems with the new portage output, this will be fixed in the next eix release (>=0.28.1 which will be soon in the tree - the fix is already in git): For your own scripts you cannot expect that they will fix themselves automatically when portage changes its output format in a new version...

Edit: Until the new version is available to you, you can use something like

[papu]

[paulj]