Search Results

You can configure vim to not add the newline at the end. Unless your vim is already quite old, try to put into .vimrc a


set nofixendofline

Whether this is a wise choice, I'm not sure. In...

I am not a vim developer so i can only speculate: vim - like vi - is not a hex-editor, but a text-editor. As such it (tries to) create(s) "well-formed" text files. A text file in UNIX has to have a...

Did you consider using the iconv tool to convert the files between all the encodings?
And, provided a program was compiled "locale-aware", you can force it to work e.g. in the C locale by setting...

man regex:
Above means: a line feed at the begin-of-line or at end-of-line will be removed. You have to know that in sed, the line end is implicitly known, no <LF> in pattern space. Thus a really...

sed '/^ *:47A/s/$/\/9201/' infile

RavinderSingh13's response works for me (tested in bash and zsh):


-0-1- ~/tmp > echo xx >'ab '
-0-1- ~/tmp > find . -name '* ' -exec echo '({})' \;
(./ab )


As you can see, I can clearly...

If there is no sub directory, and not too many files, then you can simply print them
printf "(%s)\n" Test.dat*

Hello API,

I don't think there is a need of a loop and then putting find command's value to it, you could only use find command to print the file names.

Thanks,
R. Singh

The problem is that the for loop is parsing the arguments it gets, based on the space.

If you let find control the loop, it should work:-
find . -name "Test.*" -exec echo "({})" \;

I get this...

Hello API,

Could you please try following and let me know if this helps you(haven't tested it though).

find -type f -name "* "
Thanks,
R. Singh

Hi,
Your problem is not spaces but the not eval of '*'...
Try:
#!/bin/bash
str="/home/hte4993/tmp/Porg Dir/t_"*.txt
chmod 775 "$str"But you must have just only one file either you must use a...

#!/bin/bash

IFS="+" i_string="TABLE|T_TS+AUSDRUCK|'hans.meier%'+SHIP|'Herr Kanns%'"

for key_value_item in $i_string
do
echo "key_value_item: $key_value_item"
done

Hello API,

Could you please try following and let us know if this helps you.

echo "key_value_item: TABLE|T_TS+AUSDRUCK|'hans.meier%'+SHIP|'Herr Kanns%'" | awk '{Q=$1;$1="";num=split($0,...

First off, using pipes creates temporary files - just so you know. gzip renames the output file, so no extra files when you are done.

Start with this:

gunzip tarfile.tar.gz
tar -rf...

Hello API,

Could you please try following steps(not tested though) and let me know if this helps you.
1st: Extract .tar file from .tar.gz file:
gunzip filename.tar.gz
2nd: Update uncompressed...

This works fine for ls as long as the number of digits in the part being sorted is always 2 digits, but it won't give you what you want for ls -l output. (Unless all of the files have the same...

Well, then, try to extend RavinderSingh13's proposal:ls *.txt | sort -t_ -k3,3 -k1,1

Unfortunately, your request is not clear. What exactly is "the element between the first word and the prefix"? Your two samples are somewhat contradictory as well, so your correct request can't be...

Hello API,

Could you please try following and let me know if this helps, I have checked this on bash.

ls *.txt | sort -t_ -k2,2
Output for above command was as follows.

exec_aabs291_71.txt...

something along these lines:

awk -F'[][,]' '{printf("Filename=%s%s%s\nFromLine=%s%s%s\nToLine=%s%s%s\n", qq,$2,qq,qq,$(NF-2),qq,qq,$(NF-1),qq)}' qq='"' myFile

Hello API,

I am sorry for using the same variable in both the places, following may help you in same.

cat test34.ksh
awk '{
A=B=$0;
match($0,/file\[.*\] +/);
...

You need to send the output of gzip to stdout, using the -c option. If your files end with .tar.gz try:
for file in *.tar.gz ; do gzip -cd "$file" | tar xf -; done

Some tar implementations...

You could test if you are on a terminal or pseudo terminal which would indicate a command line user. Having neither would suggest a scheduler.

The output from ps -otty= -p $$ will give you this....

The standard way of doing this (when exactly one of two possible options or operands are required) is to use a two line synopsis:
Usage: create_sql -f <filename> -a <add client> --pto <filename>...

The square brackets are what I see used to denote a choice usually.

usage: ./command --arg1 --arg2 [--arg3 | --arg4]

Don't think there's really a standard for that though.