----- Original Message ----- From: "Randall R Schulz" To: Sent: Sunday, August 17, 2008 5:47 PM Subject: Re: [opensuse] OT: bash F1

On Sunday 17 August 2008 14:36, Nick Zeljkovic wrote:

...

Hi Listmates,

Current code: CURNUM=`ls /etc/apache2/sites-enabled|cut -d- -f1|tail -1` NEWNUM=`expr $CURNUM + 1` NUMLEN=`expr length $NEWNUM`

if [ -z $CURNUM ] then FID="001" elif [ $NUMLEN -eq "1" ] then FID="00$NEWNUM" elif [ $NUMLEN -eq "2" ] then FID="0$NEWNUM" elif [ $NUMLEN -eq "3" ] then FID=$NEWNUM Fi

Basically searches /etc/apache2/sites-enabled for filenames that are like: 001-site1 002-site2

And finds last value and then adds +1 to it. Let or expr doesn't want to work with numbers starting with 0,

Your cut command looks like it's going to give you "/etc/apache2/sites" every time. You should sort your result because ls garantees no particular order unless using ie -lt which is time anyways not numerical. You don't need expr as long as you are using bash or ksh or zsh or almost anything but stock sh on sco unix or solaris. #!/bin/bash unalias ls ## grr F*&^* distros... A=`cd /etc/apache2/sites-enabled ;ls |cut -d- -f1 |sort -n |tail -1` A=`printf "%03i\n" $((++A))` In ksh you don't need to spawn a sub shell just to use printf just to get it back to right-justifid, zero-padded, 3 digits. Nor do you need the subshell nor any of the processes in the backticks with ls either as long as we're making any assumptions about the filenames anyways. There is a quirk that you must start with 001 though. You can have a file 000-site0, and other files of other forms, just this script will never see those. #!/bin/ksh typeset -Z3 A=001 cd /etc/apache2/sites-enabled while [ -e ${A}-* ] ;do ((++A)) ;done In both cases $A holds the new/next value at the end echo Next site is $A -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "Randall R Schulz" To: Sent: Sunday, August 17, 2008 9:03 PM Subject: Re: [opensuse] OT: bash F1

On Sunday 17 August 2008 17:18, Brian K. White wrote:

...

----- Original Message ----- From: "Randall R Schulz" ...

Your cut command ...

You replied to my post but addressed only content from the post to which mine was a reply.

I replied to the thread. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "Randall R Schulz" To: Sent: Sunday, August 17, 2008 10:03 PM Subject: Re: [opensuse] OT: bash F1

On Sunday 17 August 2008 18:06, Brian K. White wrote:

...

----- Original Message ----- From: "Randall R Schulz" To: Sent: Sunday, August 17, 2008 9:03 PM Subject: Re: [opensuse] OT: bash F1

...

On Sunday 17 August 2008 17:18, Brian K. White wrote:

...

----- Original Message ----- From: "Randall R Schulz" ...

Your cut command ...

You replied to my post but addressed only content from the post to which mine was a reply.

I replied to the thread.

There is no such thing as replying to a thread. You reply to a

1) Of course there is.

particular post which is part of a thread. You should choose the post to which you reply based on the content you wish to address in that reply.

Otherwise phrases like "Your cut command" seem to refer to my (Randall R. Schulz's) "cut command" when in fact I neither suggested nor stated any such command.

2) I had already deleted the original post. Ergo: see 1). This argument is admittedly technically valid, and as such I am sorry I forgot to go up and clean off your attribution from the quoting, but then again, I didn't remove the OP's either or change the nuber of layers, so the argument is a bit weak. Perhaps the only answer I should have offered to the charge was a simple "Yes, I did." with a "so what?" left unspoken but implied. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "Randall R Schulz" To: Sent: Sunday, August 17, 2008 11:32 PM Subject: Re: [opensuse] OT: bash F1

On Sunday 17 August 2008 20:03, Brian K. White wrote:

...

...

...

I replied to the thread.

There is no such thing as replying to a thread. You reply to a particular post which is part of a thread. ...

1) Of course there is.

No, there is not.

Of course there is.

Each reply includes a header that specifies the specific message to which it is a reply.

So?

...

This argument is admittedly technically valid, ...

Thank you. Now please don't reply to my posts unless you're addressing something _I_ wrote.

You get to make such a request, but you shouldn't expect it to have any meaning. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 8/18/08, Philipp Thomas wrote:

On Mon, 18 Aug 2008 03:12:39 -0400, Brian K. White wrote:

...

...

No, there is not.

Of course there is.

...

Each reply includes a header that specifies the specific message to which it is a reply.

So?

So you reply to a message within a thread, not a thread itself. Therefore you should always reply to the right message otherwise you won't get a correct threading.

Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I think the main difference is that some mail clients support threading while others don't. To reply properly you should know about both. A user who uses a threading client does not need a lot of quotes, therefore it can seem useless to a "threading" user to post a long quote. A reply to a wrong message can mess up the threading, because some of the threading clients can see what message is used to replie to (google doesn't). A user who uses a non-threading client needs these qoutes but doesn't care wether the reply is posted to the correct message. The quotes should provide him with enough information to understand the problem. Usually this is no problem, because the need to qoute is quite clearly stated and the easiest message to quote from is the message you should reply to anyway. just my €0.02. Neil btw: if my recapping of problems is undesired please tell me. -- There are two kinds of people: 1. People who start their arrays with 1. 1. People who start their arrays with 0. ----------------------------------------------------------------------- ** Hi! I'm a signature virus! Copy me into your signature, please! ** ----------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, August 18, 2008 15:42, Randall R Schulz wrote:

On Monday 18 August 2008 01:53, Neil wrote:

...

...

I think the main difference is that some mail clients support threading while others don't. To reply properly you should know about both.

Yeah, and Mr. White uses Outlook, the worst abomination ever perpertrated by that company in Redmond.

Outlook should be banned from this list. In fact, it should be banned from the Internet.

You are confusing Outlook and Outlook Express. In the headers I saw the following: Mailer: Microsoft Outlook Express 6.00.2900.5512 Outlook Express is installed with Windows and has the same version as Internet Explorer. From version 7 onward, I think it is called MS Live Mail. I agree that OE is complete and utter male cow excrement. It is a highway to hell and an open door for viruses, worms and other nasty stuff. There is only one email client that I hate more, and that is Incredimail. Outlook otoh, is part of the MS Office suite (so it costs money), and is the preferred mail client for MS Exchange servers. It doesn't just do mail, but also calendar, tasks, notes, contacts,... MS Office Outlook has a Linux counterpart: Ximian Evolution. MS Office Outlook can be forced, but with a lot of blood sweat and tears, to behave a bit polite, not like OE who shits in all corners. But please: this list is about OpenSuse, not about anti-M$-rants. -- Amedee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "Randall R Schulz" To: Sent: Monday, August 18, 2008 9:42 AM Subject: Re: [opensuse] Replying to threads (was: Re: OT: bash F1)

On Monday 18 August 2008 01:53, Neil wrote:

...

...

I think the main difference is that some mail clients support threading while others don't. To reply properly you should know about both.

Yeah, and Mr. White uses Outlook, the worst abomination ever perpertrated by that company in Redmond.

No I don't. I can't stand Outlook. As long as we're being oversensative about points of attribution that have no impact on anyones lives other than to cause dumb arguments on mail lists. I use something even worse, because as a die hard old school unix guy I'm too practical and clueful to waste time downloading thunderbird everywhere, or worse, installing linux desktops, or goofy crap like rebooting every machine I sit in front of to a knoppix thumb drive... But, what's it to you? I configure it to send only in plain text. Any other problems it has are purely my problem. I would have posted that stupid reply that has your pants in a bunch exactly the same way in any interface. And my failure to feel chastised over it, which I'm sure is the real problem, would likewise not have been any different had I been using some holier email client. Whether I am using mutt or pine or one of my own self-witten mua's, or outlook express, or pan or swiftdove or *gag* gmail, at no time am I either confused or constipated by which exact message any particular post in a conversation happens to be technically a reply to, as defined by the message-id's in the header. A conversation is a conversation. It's a human abstract construct. The email systems message tagging system is a somewhat handy tool, but it does not dictate what humans say to each other or when or how or why. At least not me. There is such a thing is nettiquette that helps keep things sane for all concerned, but good grief get over it. It wasn't even a mis-attribution! Your name merely appeared in the post that you had in fact been a part of. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "Randall R Schulz" To: Sent: Monday, August 18, 2008 11:24 AM Subject: Re: [opensuse] Replying to threads (was: Re: OT: bash F1)

On Monday 18 August 2008 07:56, Brian K. White wrote:

...

----- Original Message ----- From: "Randall R Schulz" To: Sent: Monday, August 18, 2008 9:42 AM Subject: Re: [opensuse] Replying to threads (was: Re: OT: bash F1)

...

...

Yeah, and Mr. White uses Outlook, the worst abomination ever perpertrated by that company in Redmond.

No I don't.

The headers in your posts say otherwise:

No they don't. How many times & ways must you prove yourself dense?

X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350

This is amazing. You collected the info, copied & pasted it, And still don't know what it says? Outlook != Outlook Express. One is not a subset or superset of the other except by definitions so loose as to be meaningless. If you didn't know this, then you don't know enough about the programs to have any foundation for commenting on their quality or lack of same. That means you're just another mouth repeating what you hear the smart-sounding people say.

...

...

But, what's it to you?

Outlook and Outlook Express don't conform to the standards and this failure, among many problems, leads people to believe that there is no difference between replying to a thread and replying to a specific post.

Who's confused? I'm not the one who can't read. I was not the slightest bit confused about what I was douing when I posted. Forgetting to clean up the attributions _perfectly_ was not confusion but simple sloppiness. Well you got me there! ooooh! And it still had nothing to do with the silly mail client being used at the time. Besides I thought there was no such thing as replying to a thread? Make up your mind. Also-also, what are these standards you speak of? It adheres perfectly with the "standards". (by which I at least mean smtp). Perhaps you confuse obligation with convention? Holy cow you sure packed a lot of gibberish into that one little sentence.

...

.... And my failure to feel chastised over it, which I'm sure is the real problem, ...

Part of ordinary social grace is to admit when you've done something wrong rather than defend your mistake as something that's perfectly OK.

I didn't defend the mistake. There was a teeny actual mistake in there and it got the teeny apology it deserved. (twice, now.) You want more, that's you're problem. And _that's_ all this thread is about any more. You want more apology than you have any right to and you're not going to get it, and apparently haven't come to grips with this fact of life. I am not going to help with this problem you are having in the way that you want. Go join a Martha Stewart list if you value social grace more than the work at hand here. The way I read the charter, this place is here for receiving and dispensing help, and otherwise discussing various aspects of, linux in general and opensuse in particular. Well that's what that post was doing. It was reasonable to bring the slip to my attention. It was not reasonable to actually care about it much even initially. To still care about it by now borders on the obsurd or the pathetic. If it was an actual breach of standards or expressed policy or convention that'd be one thing. Like, say top-posting, posting in html, not quoting enough or at all, quoting too much, etc.. All things I'll perfectly freely admit to having done on occasion btw. But, when you get right down to it, that post actually did none of those things. And that's why this thread is probably going to continue untill you get tired of it. I'm not really stressed or upset or even especially annoyed by your attempts to somehow make some sort of case. So I'm fine with pointing out the flaws in your arguments as long as you want to keep trying to come up with them. And who knows you may make a valid point after all and then I'll have expanded my horizons a little by having something pointed out to me that I hadn't thought of before. I'll then thank you for helping me grow as a person. It could happen. I'm merely firm in my sense of reason, not prejudiced. Do you _really_ suppose there is any _slight_ gain to be had by continuing this thread? How's this for social grace: Let's just say I am actually in the wrong, but I'm such a jerk I'll never admit it. Is there any slight doubt in your mind by now what my stance is on this topic? What does the socially graceful person do when confronted with such a situation? bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "Randall R Schulz" To: Sent: Monday, August 18, 2008 2:10 PM Subject: Re: [opensuse] Replying to threads (was: Re: OT: bash F1)

On Monday 18 August 2008 11:03, Brian K. White wrote:

...

...

Do you _really_ suppose there is any _slight_ gain to be had by continuing this thread? ...

Evidently you do. You've written dozens of words for each one I have.

So what? I'm not in it for gain. I notice a conspicuous lack of address to any substantive point or counterpoint. bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Philip Burness [08-18-08 14:28]:

I think I can speak for the rest of the list when I say SO CAN WE!!!!

Please do not presume upon the *rest* of us and don't shout. If the topic was so unworthy of defense, the voluminous outpouring was certainly unwarranted as was the mere fact of continuation. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 8/18/08, Patrick Shanahan wrote:

* Philip Burness [08-18-08 14:28]:

...

I think I can speak for the rest of the list when I say SO CAN WE!!!!

Please do not presume upon the *rest* of us and don't shout.

If the topic was so unworthy of defense, the voluminous outpouring was certainly unwarranted as was the mere fact of continuation.

-- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I thought there was another mailing list for these discussions: The Opensuse Offtopic list: To unsubscribe, e-mail: opensuse-offtopic+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-offtopic+help@opensuse.org Neil -- There are two kinds of people: 1. People who start their arrays with 1. 1. People who start their arrays with 0. ----------------------------------------------------------------------- ** Hi! I'm a signature virus! Copy me into your signature, please! ** ----------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

*snip* rant between Mr. White & Mr. Schulz *snip* How long are you guys going to continue this? The lack of social grace is detrimental to the work at hand on this list. The time spent on writing rants could be better spent. At first it was a bit funny to read, but now I am seriously considering to move the opensuse list below the spambayes lines in my procmail and moving mail from certain senders to my .ztrain.confirmed-spam folder. It's a shame that a newcomer as myself has to be confronted with such things... -- Amedee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

----- Original Message ----- From: "John Andersen" Cc: Sent: Monday, August 18, 2008 2:43 PM Subject: Re: [opensuse] Replying to threads (was: Re: OT: bash F1)

On Mon, Aug 18, 2008 at 7:56 AM, Brian K. White wrote:

...

But, what's it to you? I configure it to send only in plain text. Any other problems it has are purely my problem.

Without intending to jump into the Flame fest....

Brian, the above is not true, it (OE) causes lots of problems for EVERYBODY on the mailing list because it breaks threading for EVERYONE, not _just_ you.

That's why everyone goes off the deep end about OE so much, not because its broken for you, (which is your business) but, rather, that it breaks threads for everyone else by failure to include the entire thread reference in the headers. It totally messes up a mailing list by fracturing threads of messages into individual posts that appear totally unrelated except by title.

No one can tell you what to use, but if you just want to avoid installing thunderbird, why not get read the list with something that requires NO installation ANYWHERE? Like Gmail?

Hm. In that case you've told me something I didn't know. I happened to stop preferring thread view years ago and prefer to just read new posts in chronological order and "thread" them mentally. That's why I was mystified by the much smaller confusion a while back over another odd post where I needed to add a comment to a thread from a client that had no prior posts locally in the client at all since it was knoppix or maybe a transient install. So I posted with an obviously (to me) similar and related subject but freehand not an exact copy byte for byte, and lacking an actual post to quote I referred to it freehand, paraphrased as it were, and added the new info. I can't understand why that confused anyone. There was no fight or anything that time, it was just a little "twilight zone". Are we that helpless? Sadly I do need to use OE at least sometimes, both for testing so that my software stays perfectly compatible with most of my users mail clients and, In order to support the customers to the standard I wish, I pretty much have to actually use the same things they use. Not all the time for everything, but regularly enough so that I stay fully conversant with it down to the small day to day details. I don't want to tell them things like "configure you email client to use smtp on port 3525", I need to be able to be sitting in a cafe and walk them through each dialog exactly with no pc in front of me at least for the common things. But I don't need to use OE 100% of the time for that I guess. gmail? you like gmail? ('course, it's not like I actually "like" oe either. it just is. So I can't exactly call gmail worse.) -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, August 18, 2008 20:43, John Andersen wrote:

No one can tell you what to use, but if you just want to avoid installing thunderbird, why not get read the list with something that requires NO installation ANYWHERE? Like Gmail?

This is the first constructive message in the entire thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Your cut command looks like it's going to give you "/etc/apache2/sites" every time. You should sort your result because ls garantees no particular order unless using ie -lt which is time anyways not numerical. You don't need expr as long as you are using bash or ksh or zsh or almost anything but stock sh on sco unix or solaris.

There *shouldn't* be anything else there except sites in format like: 001-site1 002-site2 Etc.. The cut actually works OK, if it doesn't find anything, it just gives empty string which I address later on.

#!/bin/bash unalias ls ## grr F*&^* distros... A=`cd /etc/apache2/sites-enabled ;ls |cut -d- -f1 |sort -n |tail -1` A=`printf "%03i\n" $((++A))`

In ksh you don't need to spawn a sub shell just to use printf just to get it back to right-justifid, zero-padded, 3 digits. Nor do you need the subshell nor any of the processes in the backticks with ls either as long as we're making any assumptions about the filenames anyways. There is a quirk that you must start with 001 though. You can have a file 000-site0, and other files of other forms, just this script will never see those.

That's exactly what I've been looking for, somewhat, as 000-site0 should be on servers already, as it will serve default, non named-based access.

#!/bin/ksh typeset -Z3 A=001 cd /etc/apache2/sites-enabled while [ -e ${A}-* ] ;do ((++A)) ;done

In both cases $A holds the new/next value at the end echo Next site is $A

Thanks! -- Best regards, Nick Zeljkovic -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, 17 Aug 2008, Brian K. White wrote:-

Your cut command looks like it's going to give you "/etc/apache2/sites" every time.

It won't. When passed a path without wildcards, ls only returns the filenames and not the full pathname, as shown below: davjam@davids:~> ls tags do_upper_case.c Makefile shrink.o tags2.c tags2.o tags.c do_upper_case.o shrink.c tags2 tags2.c~ tags3.sh tags.sh davjam@davids:~> davjam@davids:~> ls tags/ do_upper_case.c Makefile shrink.o tags2.c tags2.o tags.c do_upper_case.o shrink.c tags2 tags2.c~ tags3.sh tags.sh davjam@davids:~> davjam@davids:~> ls tags/* tags/do_upper_case.c tags/shrink.c tags/tags2.c tags/tags3.sh tags/do_upper_case.o tags/shrink.o tags/tags2.c~ tags/tags.c tags/Makefile tags/tags2 tags/tags2.o tags/tags.sh

You should sort your result because ls garantees no particular order unless using ie -lt which is time anyways not numerical.

Erm, from "man ls" NAME ls - list directory contents SYNOPSIS ls [OPTION]... [FILE]... DESCRIPTION List information about the FILEs (the current directory by default). Sort entries alphabetically if none of -cftuSUX nor --sort. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys SUSE 10.1 32 | | openSUSE 10.3 32b | openSUSE 11.0 32b | openSUSE 10.2 64b | openSUSE 10.3 64b | openSUSE 11.0 64b RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 17 August 2008 16:13, David Bolt wrote:

On Sun, 17 Aug 2008, Nick Zeljkovic wrote:-

...

Hi Listmates,

Current code: CURNUM=`ls /etc/apache2/sites-enabled|cut -d- -f1|tail -1`

# -r allows sed to use regex in the script, # ^0+ matches any number of leading zeros CURNUM=$(ls /etc/apache2/sites-enables|cut -d- -f1|tail -1|sed -r "s#^0+##")

...

NEWNUM=`expr $CURNUM + 1`

# no need for expr to increment $NEWNUM NEWNUM=$(( ${CURNUM} + 1))

Now you're in for BASH's interpretation of digit strings as octal numbers when the first character is a zero.

...

Regards, David Bolt

Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

# no need for expr to increment $NEWNUM NEWNUM=$(( ${CURNUM} + 1))

If CURNUM is empty, or not a number, NEWNUM will be assigned a value of "1"

This whole messy code I came up with was due to bash not liking leading zeros for calculations. If my input of $CURNUM is "001" it will calculate it as "2" instead of "002".

...

NUMLEN=`expr length $NEWNUM`

No need for that line, unless you actually need $NUMLEN at some other point. If you do, you don't need to use expr:

# return the length of the variable $NEWNUM NUMLEN=${#NEWNUM}

Thanks, expr was first thing to come on my mind to do that. I need NUMLEN so I can know how many zeros to add to file identifier.

And these can be reduced to one line:

FID=$(printf "%03u" "${NEW_NUM}")

Thanks! I was missing that, seems to have done the trick replacing my checks, but something funky is going on there with numbers like 010 or anything starting with one zero: root@sgd1 [~/bin]# NEWNUM="015" root@sgd1 [~/bin]# echo $NEWNUM 015 root@sgd1 [~/bin]# printf "%03u" "${NEWNUM}" 013 Any ideas ? -- Best regards, Nick Zeljkovic -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org