How can I separate information into fields in both input and output?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












$ stat -c "%Y#%n#%y" * | awk -F'#' "BEGIN OFS=" NR==1,NR==3 print $2 $3"
directory1/Blum2017-12-22 22:33:38.644178442 -0500
dir2/Ciolli2017-12-22 21:53:51.769368496 -0500
Dar2017-12-06 13:29:37.698296879 -0500


I try to set up input and output field separators.



  • I use # as input separator, but a filename can contains #. Is there a better choice? I don't know if stat can separate the output pathnames by /null as find does and if awk can accept input field separator null.


  • why does my setup of OFS to | not work?


Thanks.




bash awk stat




share|improve this question

















  • 1




    (1) it depends - what are you trying to do, exactly? (2) because $2 $3 is a string concatenation: try $2,$3
    – steeldriver
    Jun 13 at 22:56










  • Thanks. (1) I want to make sure the three pieces of information provided by stat are recognzed by awk as separate fields.
    – Tim
    Jun 13 at 23:27










  • It seems the use of null is problematic: see this insightful answer.
    – simlev
    Jun 14 at 15:47















up vote
0
down vote

favorite












$ stat -c "%Y#%n#%y" * | awk -F'#' "BEGIN OFS=" NR==1,NR==3 print $2 $3"
directory1/Blum2017-12-22 22:33:38.644178442 -0500
dir2/Ciolli2017-12-22 21:53:51.769368496 -0500
Dar2017-12-06 13:29:37.698296879 -0500


I try to set up input and output field separators.



  • I use # as input separator, but a filename can contains #. Is there a better choice? I don't know if stat can separate the output pathnames by /null as find does and if awk can accept input field separator null.


  • why does my setup of OFS to | not work?


Thanks.




bash awk stat




share|improve this question

















  • 1




    (1) it depends - what are you trying to do, exactly? (2) because $2 $3 is a string concatenation: try $2,$3
    – steeldriver
    Jun 13 at 22:56










  • Thanks. (1) I want to make sure the three pieces of information provided by stat are recognzed by awk as separate fields.
    – Tim
    Jun 13 at 23:27










  • It seems the use of null is problematic: see this insightful answer.
    – simlev
    Jun 14 at 15:47













up vote
0
down vote

favorite









up vote
0
down vote

favorite











$ stat -c "%Y#%n#%y" * | awk -F'#' "BEGIN OFS=" NR==1,NR==3 print $2 $3"
directory1/Blum2017-12-22 22:33:38.644178442 -0500
dir2/Ciolli2017-12-22 21:53:51.769368496 -0500
Dar2017-12-06 13:29:37.698296879 -0500


I try to set up input and output field separators.



  • I use # as input separator, but a filename can contains #. Is there a better choice? I don't know if stat can separate the output pathnames by /null as find does and if awk can accept input field separator null.


  • why does my setup of OFS to | not work?


Thanks.




bash awk stat




share|improve this question













$ stat -c "%Y#%n#%y" * | awk -F'#' "BEGIN OFS=" NR==1,NR==3 print $2 $3"
directory1/Blum2017-12-22 22:33:38.644178442 -0500
dir2/Ciolli2017-12-22 21:53:51.769368496 -0500
Dar2017-12-06 13:29:37.698296879 -0500


I try to set up input and output field separators.



  • I use # as input separator, but a filename can contains #. Is there a better choice? I don't know if stat can separate the output pathnames by /null as find does and if awk can accept input field separator null.


  • why does my setup of OFS to | not work?


Thanks.





bash awk stat





share|improve this question












share|improve this question




share|improve this question








edited Jun 14 at 15:26
























asked Jun 13 at 22:13









Tim

22.5k61222401




22.5k61222401







  • 1




    (1) it depends - what are you trying to do, exactly? (2) because $2 $3 is a string concatenation: try $2,$3
    – steeldriver
    Jun 13 at 22:56










  • Thanks. (1) I want to make sure the three pieces of information provided by stat are recognzed by awk as separate fields.
    – Tim
    Jun 13 at 23:27










  • It seems the use of null is problematic: see this insightful answer.
    – simlev
    Jun 14 at 15:47













  • 1




    (1) it depends - what are you trying to do, exactly? (2) because $2 $3 is a string concatenation: try $2,$3
    – steeldriver
    Jun 13 at 22:56










  • Thanks. (1) I want to make sure the three pieces of information provided by stat are recognzed by awk as separate fields.
    – Tim
    Jun 13 at 23:27










  • It seems the use of null is problematic: see this insightful answer.
    – simlev
    Jun 14 at 15:47








1




1




(1) it depends - what are you trying to do, exactly? (2) because $2 $3 is a string concatenation: try $2,$3
– steeldriver
Jun 13 at 22:56




(1) it depends - what are you trying to do, exactly? (2) because $2 $3 is a string concatenation: try $2,$3
– steeldriver
Jun 13 at 22:56












Thanks. (1) I want to make sure the three pieces of information provided by stat are recognzed by awk as separate fields.
– Tim
Jun 13 at 23:27




Thanks. (1) I want to make sure the three pieces of information provided by stat are recognzed by awk as separate fields.
– Tim
Jun 13 at 23:27












It seems the use of null is problematic: see this insightful answer.
– simlev
Jun 14 at 15:47





It seems the use of null is problematic: see this insightful answer.
– simlev
Jun 14 at 15:47











1 Answer
1






active

oldest

votes

















up vote
1
down vote













stat -c "%Y/%n/%y" * | awk -F'/' 'NR==1,NR==3 "$3'


Or:



stat -c "%Y/%n/%y" * | awk -F'/' 'BEGIN OFS=" NR==1,NR==3 print $2,$3'


Explanation:



Instead of #, you might want to use / (the directory separator), since it can not be part of a filename.



The input awk field separator needs to be set accordingly: -F'/'.



As already pointed out in a comment by @steeldriver, you have two ways of choosing an output field separator.



  1. Use string concatenation: print $2"|"$3.

  2. Define OFS="|" and then print $2,$3.

I chose single quotes ' over double quotes " which reduces the need of escaping in this case.



Update:



Since the question now specifies that the stat output may contain the directory separator, / would not be a wise choice for the record separator. The only other character that I know of which is not allowed in filenames is NUL, but its use is problematic at least in this case. My suggestion would be to make up an awkward string that is very unlikely (although allowed) to be found as part of a filename. Accidentally, x0 (which is a representation of NUL) could be a good choice:



stat -c "%Yx0%nx0%y" * | awk -Fx0 'BEGIN OFS=" NR==1,NR==3 "$3'





share|improve this answer























  • Thanks. The output of stat can be pathnames containing /, because there can be subdirectories in the expansion of *.
    – Tim
    Jun 14 at 15:24











  • @Tim Your best bet is to use the NUL character then!
    – simlev
    Jun 14 at 15:27










  • How shall I specify NUL to stat and awk?
    – Tim
    Jun 14 at 15:28










  • I don't think it will work. You can specify a very awkward string that is unlikely to be found in filenames, such as #°°#.
    – simlev
    Jun 14 at 15:40










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f449680%2fhow-can-i-separate-information-into-fields-in-both-input-and-output%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













stat -c "%Y/%n/%y" * | awk -F'/' 'NR==1,NR==3 "$3'


Or:



stat -c "%Y/%n/%y" * | awk -F'/' 'BEGIN OFS=" NR==1,NR==3 print $2,$3'


Explanation:



Instead of #, you might want to use / (the directory separator), since it can not be part of a filename.



The input awk field separator needs to be set accordingly: -F'/'.



As already pointed out in a comment by @steeldriver, you have two ways of choosing an output field separator.



  1. Use string concatenation: print $2"|"$3.

  2. Define OFS="|" and then print $2,$3.

I chose single quotes ' over double quotes " which reduces the need of escaping in this case.



Update:



Since the question now specifies that the stat output may contain the directory separator, / would not be a wise choice for the record separator. The only other character that I know of which is not allowed in filenames is NUL, but its use is problematic at least in this case. My suggestion would be to make up an awkward string that is very unlikely (although allowed) to be found as part of a filename. Accidentally, x0 (which is a representation of NUL) could be a good choice:



stat -c "%Yx0%nx0%y" * | awk -Fx0 'BEGIN OFS=" NR==1,NR==3 "$3'





share|improve this answer























  • Thanks. The output of stat can be pathnames containing /, because there can be subdirectories in the expansion of *.
    – Tim
    Jun 14 at 15:24











  • @Tim Your best bet is to use the NUL character then!
    – simlev
    Jun 14 at 15:27










  • How shall I specify NUL to stat and awk?
    – Tim
    Jun 14 at 15:28










  • I don't think it will work. You can specify a very awkward string that is unlikely to be found in filenames, such as #°°#.
    – simlev
    Jun 14 at 15:40














up vote
1
down vote













stat -c "%Y/%n/%y" * | awk -F'/' 'NR==1,NR==3 "$3'


Or:



stat -c "%Y/%n/%y" * | awk -F'/' 'BEGIN OFS=" NR==1,NR==3 print $2,$3'


Explanation:



Instead of #, you might want to use / (the directory separator), since it can not be part of a filename.



The input awk field separator needs to be set accordingly: -F'/'.



As already pointed out in a comment by @steeldriver, you have two ways of choosing an output field separator.



  1. Use string concatenation: print $2"|"$3.

  2. Define OFS="|" and then print $2,$3.

I chose single quotes ' over double quotes " which reduces the need of escaping in this case.



Update:



Since the question now specifies that the stat output may contain the directory separator, / would not be a wise choice for the record separator. The only other character that I know of which is not allowed in filenames is NUL, but its use is problematic at least in this case. My suggestion would be to make up an awkward string that is very unlikely (although allowed) to be found as part of a filename. Accidentally, x0 (which is a representation of NUL) could be a good choice:



stat -c "%Yx0%nx0%y" * | awk -Fx0 'BEGIN OFS=" NR==1,NR==3 "$3'





share|improve this answer























  • Thanks. The output of stat can be pathnames containing /, because there can be subdirectories in the expansion of *.
    – Tim
    Jun 14 at 15:24











  • @Tim Your best bet is to use the NUL character then!
    – simlev
    Jun 14 at 15:27










  • How shall I specify NUL to stat and awk?
    – Tim
    Jun 14 at 15:28










  • I don't think it will work. You can specify a very awkward string that is unlikely to be found in filenames, such as #°°#.
    – simlev
    Jun 14 at 15:40












up vote
1
down vote










up vote
1
down vote









stat -c "%Y/%n/%y" * | awk -F'/' 'NR==1,NR==3 "$3'


Or:



stat -c "%Y/%n/%y" * | awk -F'/' 'BEGIN OFS=" NR==1,NR==3 print $2,$3'


Explanation:



Instead of #, you might want to use / (the directory separator), since it can not be part of a filename.



The input awk field separator needs to be set accordingly: -F'/'.



As already pointed out in a comment by @steeldriver, you have two ways of choosing an output field separator.



  1. Use string concatenation: print $2"|"$3.

  2. Define OFS="|" and then print $2,$3.

I chose single quotes ' over double quotes " which reduces the need of escaping in this case.



Update:



Since the question now specifies that the stat output may contain the directory separator, / would not be a wise choice for the record separator. The only other character that I know of which is not allowed in filenames is NUL, but its use is problematic at least in this case. My suggestion would be to make up an awkward string that is very unlikely (although allowed) to be found as part of a filename. Accidentally, x0 (which is a representation of NUL) could be a good choice:



stat -c "%Yx0%nx0%y" * | awk -Fx0 'BEGIN OFS=" NR==1,NR==3 "$3'





share|improve this answer















stat -c "%Y/%n/%y" * | awk -F'/' 'NR==1,NR==3 "$3'


Or:



stat -c "%Y/%n/%y" * | awk -F'/' 'BEGIN OFS=" NR==1,NR==3 print $2,$3'


Explanation:



Instead of #, you might want to use / (the directory separator), since it can not be part of a filename.



The input awk field separator needs to be set accordingly: -F'/'.



As already pointed out in a comment by @steeldriver, you have two ways of choosing an output field separator.



  1. Use string concatenation: print $2"|"$3.

  2. Define OFS="|" and then print $2,$3.

I chose single quotes ' over double quotes " which reduces the need of escaping in this case.



Update:



Since the question now specifies that the stat output may contain the directory separator, / would not be a wise choice for the record separator. The only other character that I know of which is not allowed in filenames is NUL, but its use is problematic at least in this case. My suggestion would be to make up an awkward string that is very unlikely (although allowed) to be found as part of a filename. Accidentally, x0 (which is a representation of NUL) could be a good choice:



stat -c "%Yx0%nx0%y" * | awk -Fx0 'BEGIN OFS=" NR==1,NR==3 "$3'






share|improve this answer















share|improve this answer



share|improve this answer








edited Jun 14 at 16:34


























answered Jun 14 at 15:19









simlev

47019




47019











  • Thanks. The output of stat can be pathnames containing /, because there can be subdirectories in the expansion of *.
    – Tim
    Jun 14 at 15:24











  • @Tim Your best bet is to use the NUL character then!
    – simlev
    Jun 14 at 15:27










  • How shall I specify NUL to stat and awk?
    – Tim
    Jun 14 at 15:28










  • I don't think it will work. You can specify a very awkward string that is unlikely to be found in filenames, such as #°°#.
    – simlev
    Jun 14 at 15:40
















  • Thanks. The output of stat can be pathnames containing /, because there can be subdirectories in the expansion of *.
    – Tim
    Jun 14 at 15:24











  • @Tim Your best bet is to use the NUL character then!
    – simlev
    Jun 14 at 15:27










  • How shall I specify NUL to stat and awk?
    – Tim
    Jun 14 at 15:28










  • I don't think it will work. You can specify a very awkward string that is unlikely to be found in filenames, such as #°°#.
    – simlev
    Jun 14 at 15:40















Thanks. The output of stat can be pathnames containing /, because there can be subdirectories in the expansion of *.
– Tim
Jun 14 at 15:24





Thanks. The output of stat can be pathnames containing /, because there can be subdirectories in the expansion of *.
– Tim
Jun 14 at 15:24













@Tim Your best bet is to use the NUL character then!
– simlev
Jun 14 at 15:27




@Tim Your best bet is to use the NUL character then!
– simlev
Jun 14 at 15:27












How shall I specify NUL to stat and awk?
– Tim
Jun 14 at 15:28




How shall I specify NUL to stat and awk?
– Tim
Jun 14 at 15:28












I don't think it will work. You can specify a very awkward string that is unlikely to be found in filenames, such as #°°#.
– simlev
Jun 14 at 15:40




I don't think it will work. You can specify a very awkward string that is unlikely to be found in filenames, such as #°°#.
– simlev
Jun 14 at 15:40












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f449680%2fhow-can-i-separate-information-into-fields-in-both-input-and-output%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more