On 04/21/10 07:19, Warp wrote:
>   (Yeah yeah, I know, you can do everything you can do in Linux and far more.
> There are all these fancy scripting languages and whatnot, which you might be
> able to use if you install something and something else. Nothing really
> consistent, and always a pain.)

	(aka the "Darren Disclaimer")

-- 
To call a man an ass is to insult the jackass.  M.Twain

Post a reply to this message

Neeum Zawan wrote:
> On 04/21/10 14:02, Darren New wrote:
>> On the rare occasion I wanted exact byte counts, I used Properties. I
>> find it more annoying that Linux doesn't put thousands-separators in
>> numbers, so when it shows me the size of a 20G file, it takes me lots of
>> staring to figure it out. :-)
> 
> 	Umm...I've said this to you lots of times: Use Midnight Commander

I don't want to learn a whole new way of doign things. When I care, I just 
do the ls again with -h.

-- 
Darren New, San Diego CA, USA (PST)
   Linux: Now bringing the quality and usability of
   open source desktop apps to your personal electronics.

Post a reply to this message

Neeum Zawan wrote:
> On 04/21/10 07:19, Warp wrote:
>>   (Yeah yeah, I know, you can do everything you can do in Linux and far more.
>> There are all these fancy scripting languages and whatnot, which you might be
>> able to use if you install something and something else. Nothing really
>> consistent, and always a pain.)
> 
> 	(aka the "Darren Disclaimer")

I.e., "I find Windows difficult because it's not made for nerds by nerds, so 
to make it as nerdy as Linux, I have to download some free programs and 
install them." :-)

<Sound of tiny violins in the background. ;->

-- 
Darren New, San Diego CA, USA (PST)
   Linux: Now bringing the quality and usability of
   open source desktop apps to your personal electronics.

Post a reply to this message

>  You use your text editor to tell you which files in a directory structure
> contain a specified string? Talk about being overly complicated. grep is a
> way, way simpler way to do that.

Or, in Windows, you can just type the string into the top right of any 
explorer view, in the box that says "Search".  Assuming you haven't disabled 
the indexing service it should be pretty fast (otherwise it needs to 
actually manually search every byte of every file, which is obviously slow).

Post a reply to this message

>> Now, in fairness,
>> as far as I can tell Windoze can't do this *at all*. But it was pretty
>> hard to do from Linux either.
> 
> Windows = Internet Connection Sharing
> Linux = at least with openSUSE 11.2, YaST -> Firewall -> Masquerading.  
> Two NICs need to be configured and running.  You can even set port 
> forwarding there.

Interesting. I thought ICS only works for dialup modems?

Post a reply to this message

>>>   Ever heard of the magical word "grep"? Do you know what it's used for in
>>> unix systems? If yes, and you understand why this utility has existed for,
>>> like, forever, then why are you asking "why would you evern want to do such
>>> a thing"?
> 
>> I throught that grep is an overly-complicated way of searching for the 
>> location of a string within one particular file? (I usually just use my 
>> text editor's "search" function.)
> 
>   You use your text editor to tell you which files in a directory structure
> contain a specified string? Talk about being overly complicated. grep is a
> way, way simpler way to do that.

No, I mean... I thought grep can only search within a single file (as 
can any decent text editor). I didn't realise it can search multiple files.

(I'm still having trouble thinking up a use-case for that. About the 
only thing I can think of is trying to find out which header file 
defines a particular symbol or something.)

>> I guess I don't very often edit large files...
> 
>   What does file size have to do with anything?

If it's a small file, you can search it just be scrolling through it and 
looking with your eyes. You don't need an automated search facility. The 
only real reason to use an automated search is if there's too much data 
to hunt through manually.

Post a reply to this message

>> I throught that grep is an overly-complicated way of searching for the
>> location of a string within one particular file? (I usually just use my
>> text editor's "search" function.)
> 
> Does your editor support regular expressions?   Most only support a 
> simple substring search.

Is there some advantage to supporting regular expressions?

I mean, I realise that hypothetically a regex can find things that a 
normal search can't. But in reality, when are you *ever* going to use 
that? What would it be useful for?

> As Warp said, you also can traverse a directory structure with grep to 
> find the file(s) that have the string in them.

I didn't know that. I thought grep was just for searching within one file.

Post a reply to this message

Warp wrote:

>   "Windows is easy for a beginner to use" is a surprisingly widespread
> misconception. I don't understand where it comes from. Probably Microsoft
> propaganda.

LOL! Yeah, well, few companies are going to boast about their products 
being *hard* to use, are they? ;-)

Post a reply to this message

>> ...so how do you actually do this then?
> 
> That's what the whole COM thing is all about, along with things like 
> "Windows Scripting Host" and "Power Shell".

 From what I've seen, you can't touch COM unless you're programming in C 
or C++.

Similarly, I thought WSH was just a way of running JavaScript without 
having to put it into a web browser? It's news to me that you can 
actually do anything new with it.

I have no idea what Power Shell is.

Last time I checked, neither WSH nor Power Shell comes with Windows. You 
said "all of this is trivial using only the scripting tools that come 
with Windows". So how exactly do you do this then?

Post a reply to this message

Darren New wrote:

> <Sound of tiny violins in the background. ;->

Show me a violin that *isn't* tiny. ;-)

Post a reply to this message