From: Tomas Nordin <tomasn@posteo.net>
To: help-gnu-emacs@gnu.org
Subject: Re: I want to contribute and chose right project for graduate thesis
Date: Sat, 22 Jul 2017 22:55:32 +0200 [thread overview]
Message-ID: <87pocs2nuj.fsf@fliptop> (raw)
In-Reply-To: <86o9sd77mr.fsf@zoho.com>
Emanuel Berg <moasen@zoho.com> writes:
> Despite using cut 27 times in my zsh source,
> I have never experienced any problems and
> I don't understand what is lacking.
> Perhaps because I have used it to parse command
> outputs, not file contents ... tho my intuition
> tells me, that shouldn't matter! Care to share
> an example where cut as it presently
> stands fails?
I hope I have not made the impression that I think it fails somehow, I
was merely trying to give a tip on something to possibly hack on for a
thesis. Maybe participate in the thread on the coreutils list if
feelings against the suggestion are strong? :)
But since I cannot resist, here is my rewrite of the suggestion:
$ cat feb17.csv | head -n 1
Datum,Transaktion,Kategori,Belopp,Saldo
$ cut -d, -f 1,3 feb17.csv | head -n 1
Datum,Kategori
# can we ask cut to reorder the fields by requesting them in other order?
$ cut -d, -f 3,1 feb17.csv | head -n 1
Datum,Kategori
# seems not
So the suggestion is about outputting the fields as requested on the
command line.
next prev parent reply other threads:[~2017-07-22 20:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 8:46 I want to contribute and chose right project for graduate thesis Mario Krajačić
2017-07-21 16:01 ` Emanuel Berg
2017-07-21 18:40 ` Marcin Borkowski
2017-07-21 20:01 ` Emanuel Berg
2017-07-22 4:10 ` Marcin Borkowski
2017-07-22 16:19 ` Emanuel Berg
2017-07-27 23:15 ` Ken Goldman
2017-07-27 23:27 ` Emanuel Berg
2017-07-28 18:55 ` Marcin Borkowski
2017-07-28 19:50 ` Drew Adams
2017-07-29 2:30 ` Emanuel Berg
2017-08-03 17:39 ` Marcin Borkowski
2017-07-29 2:22 ` Emanuel Berg
2017-07-21 18:30 ` Kevin Buchs
2017-07-21 19:58 ` Emanuel Berg
2017-07-21 21:16 ` Tomas Nordin
2017-07-21 22:17 ` Emanuel Berg
2017-07-21 22:22 ` Emanuel Berg
2017-07-22 20:55 ` Tomas Nordin [this message]
2017-07-22 21:37 ` Emanuel Berg
2017-07-25 17:39 ` Mario Krajačić
2017-07-25 18:30 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2017-07-22 13:33 Richard Melville
2017-07-22 16:25 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pocs2nuj.fsf@fliptop \
--to=tomasn@posteo.net \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).