 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New <dne### [at] san rr com> wrote:
> > Well, duh. People don't use soft links because Windows doesn't support
> > them. Seems plainly obvious.
> It has some support. People don't use them because they don't need them,
> really.
No. Windows doesn't support them, so user have learned to live without
them, and then they are claiming that they "don't need them" (one of the
most common "windows'isms").
If Windows had supported soft links from day one, they would probably be
in pretty common use, and it would be unthinkable to drop them.
> Software is written to not hard-code paths that don't need to be
> hard-coded.
Yeah, because that's the *only* thing soft links are used for.
> > I'm pretty sure you wouldn't be writing that if Windows had full support
> > for soft links from day one to this day.
> Uh, yes, actually, I would.
You might yourself believe that, but I don't think it's true. I'm pretty
certain that if Windows had supported soft links from the very beginning,
you would today be defending them. (You would *especially* be defending
them if Unix/Linux didn't support them, I'm pretty sure.)
> I think soft links are an abomination, and I've
> only ever seen them used to basically correct flaws in software
> configurations.
Linux distros use them frequently to, for example, make "aliases" of
libraries of different versions to an actual file which is fully compatible.
In other words, if version 1.2.3 of a library is fully backwards compatible
back to version 1.0.0 of the library, the "versionless" library (eg.
"libsomething.so") file will usually be linked to the 1.2.3 version of the
file (eg. "libsomething.so.1.2.3"), as well as the several versioned files
(eg. "libsomething.so.1" would be a soft link to "libsomething.so.1.2.3" if
the latter is fully backwards compatible with version 1).
This is not a question of "bad configuration". It's a question of
practicality (an executable may have been linked against version 1.0.0 of
the library, but it will work ok with the version 1.2.3, so the soft link
will make it load that) and saving disk space (especially if the library is
several megabytes in size).
And before you start nitpicking about how that could be solved in other
ways (which I'm 100% sure you will do), that was just ONE EXAMPLE of many.
(Another cool example is when a software package consists of several
executables, each one doing slightly different things... But instead of
having a 5-megabyte file for each executable, they are all in fact soft
links to one single 6-megabyte executable which then acts different depending
in which name was used to start it. Again, this saves disk space.)
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New <dne### [at] san rr com> wrote:
> 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." :-)
Most of which are very specific, support only a limited amount of
functionalities, cannot be chained to perform more complex operations,
are often inconvenient to use, large and heavy, and litter your system
with tons of setup files and registry entries which it will leave there
even after you uninstall the app. Also if they do very low-level stuff,
they usually don't integrate very well with Windows and its own apps
(such as Windows Explorer).
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
scott <sco### [at] scott com> wrote:
> >> Or, in Windows, you can just type the string into the top right of any
> >> explorer view, in the box that says "Search".
> >
> > I wish it worked. It doesn't.
> Works fine here - I just tested it by typing in "Vector3" (used in XNA game
> studio to represent a 3D vector) and within about 1 second the explorer
> window had filled up with lots of C# source code files, plus lots of POV
> source files (I guess it uses Vector3 too).
Lucky you.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> Heh. I didn't know the shell could do that either. (Although you didn't
> specify *which* shell - Unix has several...)
I don't think there's a unix shell in existence that doesn't do file name
pattern expansion. It would be a rather useless shell if it didn't.
The shell doing the expansion rather than the program is a rather clever
idea. In DOS it was always the program which did the expansion, which meant
that many programs didn't support expansion patterns because the programmers
were lazy. It's also handy because a more advanced shell can support more
complex expansion patterns without the need for the programs to support them.
The program just ends up seeing a bunch of file names in the command line
(because the shell expands them before even launching the program).
> I'm still not seeing what's so useful about being able to search a file
> for something.
Suppose that you have a httpd log file and you want to list all entries
within a specific day. Or the number of requests for a specific file (or
a group of files). Suppose you want to list all entries *except* those
which match a certain pattern (eg. they have a referrer which indicates
that the request was made by a search engine). 'grep' is your tool for that.
> Now, I suppose if you were trying to script something, being able to
> pipe output from another command into grep so that it can grab a
> particular substring that you can then pipe to something else might be
> useful. But then, if *I* wanted to do something like that, I wouldn't
> script it. I'd write a real program, not a script.
Filtering some files through a chain of programs (such as grep and sed)
takes just a few seconds of writing a few commands on the command line.
Writing a program to do that would probably take a hundred times longer.
> I never have 50 small files.
Haha. You are quite humorous sometimes.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> I still don't get why you'd need to do complex searching. And if for
> some strange reason you do need to, why use an obfuscated text string
> with limited processing capabilities when you can use a real programming
> language?
Because you can write a simple search pattern in a matter of seconds,
while writing the equivalent program would take you minutes at least.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
> Lucky you.
Computers don't work on luck :-)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> Invisible <voi### [at] dev null> wrote:
>> I still don't get why you'd need to do complex searching. And if for
>> some strange reason you do need to, why use an obfuscated text string
>> with limited processing capabilities when you can use a real programming
>> language?
>
> Because you can write a simple search pattern in a matter of seconds,
> while writing the equivalent program would take you minutes at least.
Um... why? Three lines of text doesn't take "minutes" to write. And
that's about all it takes to search a folder for a file matching a
condition. (Obviously, it depends on how complicated the condition is...)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
scott wrote:
> Computers don't work on luck :-)
Some days I start to wonder... :-S
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> The shell doing the expansion rather than the program is a rather clever
> idea.
Yeah. But then, it's part of the general Unix philosophy of "make each
tool do one job, and one job well".
With MS-DOS/Windows, the shell's job is basically to launch the
interactive programs that do all the *real* work. The shell itself is
pretty poor. (Although not quite as poor as it seems at first...)
>> I'm still not seeing what's so useful about being able to search a file
>> for something.
>
> Suppose that you have a httpd log file and you want to list all entries
> within a specific day. Or the number of requests for a specific file (or
> a group of files). Suppose you want to list all entries *except* those
> which match a certain pattern (eg. they have a referrer which indicates
> that the request was made by a search engine). 'grep' is your tool for that.
Ah, right. I see.
Personally, I'd import the whole log into a relational database, and
process it that way. (Or maybe even use a webserver that keeps its logs
in a database in the first place, rather than a huge flat file.) But
apparently that's just me...
>> Now, I suppose if you were trying to script something, being able to
>> pipe output from another command into grep so that it can grab a
>> particular substring that you can then pipe to something else might be
>> useful. But then, if *I* wanted to do something like that, I wouldn't
>> script it. I'd write a real program, not a script.
>
> Filtering some files through a chain of programs (such as grep and sed)
> takes just a few seconds of writing a few commands on the command line.
> Writing a program to do that would probably take a hundred times longer.
On the contrary, figuring out how to work grep vs writing a program in a
language I already know well is likely to take *slightly* more than
merely a hundred times longer. (Although you could argue that's a
one-time cost.)
Personally I just dislike scripting languages. I'd rather use a real
language with propper error checking and so on and so forth. But I guess
that's just me.
>> I never have 50 small files.
>
> Haha. You are quite humorous sometimes.
Maybe I just don't try to do the same kinds of tasks as you?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> Personally, I'd import the whole log into a relational database, and
> process it that way. (Or maybe even use a webserver that keeps its logs
> in a database in the first place, rather than a huge flat file.) But
> apparently that's just me...
Talk about an overly complicated solution for a simple problem.
> On the contrary, figuring out how to work grep vs writing a program in a
> language I already know well is likely to take *slightly* more than
> merely a hundred times longer. (Although you could argue that's a
> one-time cost.)
Writing something like "grep 'hello.*there' file.txt" doesn't require a
lot of time or thinking.
> Personally I just dislike scripting languages. I'd rather use a real
> language with propper error checking and so on and so forth. But I guess
> that's just me.
What's the difference between "a scripting language" and "a real language"?
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> Um... why? Three lines of text doesn't take "minutes" to write. And
> that's about all it takes to search a folder for a file matching a
> condition. (Obviously, it depends on how complicated the condition is...)
How long does it take you to write a program which does the same thing
as this:
fgrep '#include "header.hh"' *.cc
How long does it take to write the program *and* compile it *and* run it?
Why would you do that when you *already* have a program which does that
(namely 'grep')?
And I didn't even use any wildcards there.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> Personally, I'd import the whole log into a relational database, and
>> process it that way. (Or maybe even use a webserver that keeps its logs
>> in a database in the first place, rather than a huge flat file.) But
>> apparently that's just me...
>
> Talk about an overly complicated solution for a simple problem.
Once the data is in a real database, you can sort it and search it and
compute stats on it and basically do whatever you want with it,
effortlessly and easily. But sure, if you *only* wanted to quickly see
if a particular IP address appears or something, you could use a text
search. But if I was hunting through web logs, I'd probably want to
build all sorts of statistics or do multi-way searches - the exact task
that databases are especially designed to perform. Why not use the right
tool?
>> On the contrary, figuring out how to work grep vs writing a program in a
>> language I already know well is likely to take *slightly* more than
>> merely a hundred times longer. (Although you could argue that's a
>> one-time cost.)
>
> Writing something like "grep 'hello.*there' file.txt" doesn't require a
> lot of time or thinking.
Nor does opening file.txt in a text editor and running a quick search.
(Not that I can think of a reason to want to do this in the first place...)
>> Personally I just dislike scripting languages.
>
> What's the difference between "a scripting language" and "a real language"?
Now that is surprisingly hard to pin down. ;-)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> Invisible <voi### [at] dev null> wrote:
>> Um... why? Three lines of text doesn't take "minutes" to write. And
>> that's about all it takes to search a folder for a file matching a
>> condition. (Obviously, it depends on how complicated the condition is...)
>
> How long does it take you to write a program which does the same thing
> as this:
>
> fgrep '#include "header.hh"' *.cc
>
> How long does it take to write the program *and* compile it *and* run it?
> Why would you do that when you *already* have a program which does that
> (namely 'grep')?
>
> And I didn't even use any wildcards there.
OK, fair enough. I guess we'll just put this one down as "I personally
have never ever needed to do this" then.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> > Writing something like "grep 'hello.*there' file.txt" doesn't require a
> > lot of time or thinking.
> Nor does opening file.txt in a text editor and running a quick search.
It requires a lot more time, especially if you want to do it for more than
one file. It's you who was talking about "using the right tool".
> (Not that I can think of a reason to want to do this in the first place...)
You are now being stubborn as a matter of principle. I gave you one example
and you admitted that the example was sensible, and even gave an alternative
solution to the same problem (by using a database), and now you are again
repeating the "I can't think of a reason to do this" nonsense.
> >> Personally I just dislike scripting languages.
> >
> > What's the difference between "a scripting language" and "a real language"?
> Now that is surprisingly hard to pin down. ;-)
I think you are simply being prejudiced.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> OK, fair enough. I guess we'll just put this one down as "I personally
> have never ever needed to do this" then.
I don't think that's true. You said that you would use a text editor to
search for specific lines. That means you *know* that you can use a text
editor for that purpose. If you know that, you have probably done it,
probably many times.
You are just being stubborn and arguing for the sake of argument.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>>> Writing something like "grep 'hello.*there' file.txt" doesn't require a
>>> lot of time or thinking.
>
>> Nor does opening file.txt in a text editor and running a quick search.
>
> It requires a lot more time, especially if you want to do it for more than
> one file. It's you who was talking about "using the right tool".
If you have lots of files to search then yes, I guess you don't want to
open each one in a text editor just to search it. (Again, not something
I've ever needed to do.)
>> (Not that I can think of a reason to want to do this in the first place...)
>
> You are now being stubborn as a matter of principle. I gave you one example
> and you admitted that the example was sensible, and even gave an alternative
> solution to the same problem (by using a database), and now you are again
> repeating the "I can't think of a reason to do this" nonsense.
I can't think of a reason to search a text file for "hi there". Maybe
I'm just looking at this too narrowly. As I say, in the kinds of tasks I
do, I almost never need to search for things. (E.g., I don't run a web
server.) So maybe that's why it doesn't seem so vital to me.
>>>> Personally I just dislike scripting languages.
>>> What's the difference between "a scripting language" and "a real language"?
>
>> Now that is surprisingly hard to pin down. ;-)
>
> I think you are simply being prejudiced.
There are languages which are designed for quickly throwing together
small scripts, and there are languages designed for building large-scale
applications. There's no sharp dividing line between them, but they
exist. I tend to prefer the latter; scripting languages tend to be a tad
messy and ad hoc, and many of them try to be too helpful and end up
getting in your way. Still, if the task you're trying to perform really
*is* small, sometimes scripting can be the best way.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> OK, fair enough. I guess we'll just put this one down as "I personally
>> have never ever needed to do this" then.
>
> I don't think that's true. You said that you would use a text editor to
> search for specific lines. That means you *know* that you can use a text
> editor for that purpose. If you know that, you have probably done it,
> probably many times.
Not nearly as many times as you seem to think.
> You are just being stubborn and arguing for the sake of argument.
Well, I could have stood here claiming that "no, you must be wrong".
Instead I said "OK, maybe it's just that you use computers for different
tasks than me". Doesn't sound to me like somebody who's *trying* to
cause an argument. (If anything, your comment sounds more argumentative...)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> (Again, not something I've ever needed to do.)
Do you know what I'm thinking? I'm thinking that you have been in
situations where searching something on a bunch of files would have
been useful, but since you didn't know how, you just skipped it and
forgot about it. Or you perhaps used some really complicated way of
doing it and then forgot about it.
> I can't think of a reason to search a text file for "hi there".
OMG. Do you understand the concept of an example?
Besides, I already gave *real* examples in a previous post (related to
httpd logs). You acknowledged the usefulness, but naturally are now
forgetting about it, for whatever reason I cannot understand.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> >> OK, fair enough. I guess we'll just put this one down as "I personally
> >> have never ever needed to do this" then.
> >
> > I don't think that's true. You said that you would use a text editor to
> > search for specific lines. That means you *know* that you can use a text
> > editor for that purpose. If you know that, you have probably done it,
> > probably many times.
> Not nearly as many times as you seem to think.
That's quite different from "never needed to do this".
You are seriously telling me you have never used the search feature of
a program which handles text?
> > You are just being stubborn and arguing for the sake of argument.
> Well, I could have stood here claiming that "no, you must be wrong".
> Instead I said "OK, maybe it's just that you use computers for different
> tasks than me". Doesn't sound to me like somebody who's *trying* to
> cause an argument. (If anything, your comment sounds more argumentative...)
How hard is it to say "yes, I see how 'grep' or similar tools can be
very useful"? Instead, you keep repeating "I have never needed anything
like that", making it sound like in your opinion it must be one of the
most useless things in existence.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>>>> OK, fair enough. I guess we'll just put this one down as "I personally
>>>> have never ever needed to do this" then.
>>> I don't think that's true. You said that you would use a text editor to
>>> search for specific lines. That means you *know* that you can use a text
>>> editor for that purpose. If you know that, you have probably done it,
>>> probably many times.
>
>> Not nearly as many times as you seem to think.
>
> That's quite different from "never needed to do this".
>
> You are seriously telling me you have never used the search feature of
> a program which handles text?
I do occasionally do a find & replace over a file to rename an
identifier. Not particularly often though. I can't remember the last
time I needed to perform just a normal search.
(Although I'll admit I sometimes end up needing it on web pages. Like, I
google something, and the page that comes back doesn't appear to contain
my search term anywhere, so I do a text search for it.)
> How hard is it to say "yes, I see how 'grep' or similar tools can be
> very useful"? Instead, you keep repeating "I have never needed anything
> like that", making it sound like in your opinion it must be one of the
> most useless things in existence.
The fact that "grep" is used within certain circles as if it's an actual
English verb makes it clear that somebody thinks it's useful. I'm just
puzzled as to what the attraction is, that's all.
From what's happened in this discussion, it seems that it's just that
other people work with far more text files than I do.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
scott wrote:
>> I wish it worked. It doesn't.
> Works fine here -
You missed the part of the conversation where Warp is still using XP, where
the search works poorly, along with the numerous suggestions I gave to make
it work better.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
scott wrote:
> looking for which source file contains certain code. Outside of
> programming/development I can't think of many other common cases (maybe
Songs by a particular singer. Photos by a particular camera. Word documents
commented on by a particular employee. Email messages about a particular
topic. These are all the same search process.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
scott wrote:
> As this isn't easily possible using Windows Explorer then the only
> option sometimes is to search.
Yeah it is, as long as your file has someplace to *put* that data.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> The shell doing the expansion rather than the program is a rather clever
> idea.
It has its drawbacks, too. Having a file named -rf in your home directory
leads to problems, for example. Before shells properly escaped everything,
files with spaces in the names were very problematic as well.
> Filtering some files through a chain of programs (such as grep and sed)
> takes just a few seconds of writing a few commands on the command line.
> Writing a program to do that would probably take a hundred times longer.
Depends on your tools at hand and what kind of files you're searching.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
> 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?
For example, finding where in the file a symbol is defined instead of used.
I do that all the time. "Where is the definition of this macro?"
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
> why use an obfuscated text string
Because it's a text string, and not a programming language. And because
everyone uses essentially the same text strings.
Do you type your three lines of code as the argument to a command-line program?
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New wrote:
> It has its drawbacks, too. Having a file named -rf in your home
> directory leads to problems, for example. Before shells properly
> escaped everything, files with spaces in the names were very problematic
> as well.
Hell, I *still* see programs and libraries saying "don't install this in
a path with spaces".
Wanna guess where the default location for Windows programs is?
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> 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?
>
> For example, finding where in the file a symbol is defined instead of used.
>
> I do that all the time. "Where is the definition of this macro?"
As I say, I've never needed to do that. (Then again, I don't work with
other people's code, only my own.)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> Darren New <dne### [at] san rr com> wrote:
>> Exactly my point. Write a program in Linux that walks a directory tree and
>> does *not* account for soft links (or "..") and you have a problem.
>
> And that's the reason why they are not supported in Unix systems?
> (Oops, they are! Why, since they are so extremely dangerous?)
No, I just said you need to account for it. The Linux tools that walk
directory structures all are aware of sym links. The Windows tools aren't.
Hence, sym links are more dangerous on Windows than on Linux, for exactly
the same reason that it took so long for programs to be able to run without
unnecessary permissions under Windows - it wasn't always like that.
Vista supports symlinks from the command line. There's an extension
(naturally) that lets you do it from explorer. Why do you keep complaining
that your two-generations-outdated OS doesn't come with all the stuff you
can download for free to make it suit your needs?
> So in order to get Windows Explorer to show exact byte counts, I would have
> to download and install Visual Studio, get it to work, write an extension
> manually, install it, and keep it with me in an USB stick so that I can
> install it in a friend's computer if I ever want to see the byte sizes there
> as well?
Pretty much, yah. Same as any other program you write. What did you expect?
You mean if I want to indent files the way I like, I have to download emacs,
write some elisp code, then stick it on a USB stick and carry it around to
every other emacs-enabled computer?
> I think you made some kind of claim containing the word "trivial" in some
> post of yours.
More trivial than rewriting the shell. A 50-line program is pretty trivial, yes?
>>>> And which byte count do you want?
>>> The size of the file. How many bytes it contains. If I opened it with a
>>> program and started reading bytes, how many I would get before EOF.
>
>> Open it raw, or processed, or for backup?
>
> You are nitpicking, and you know it.
You're nitpicking. You want exact byte counts in one window but not the
other. It's trivial to get that information, yet you complain it's
difficult. Plus, you can't even clearly define what it is you want to see.
> Is agreeing with something really so hard?
I already agreed. You kept bashing at it.
> Yeah, because there's exactly one single way of listing files in "Linux".
It generally doesn't put in thousands-separators anywhere.
> Konqueror uses thousands-separators in file sizes.
Good to know.
> So if I want to see the individual byte sizes of 20 files, exactly how do
> I do that "with one extra step"?
"dir"
> What harm could there be if Windows Explorer had an option to show file
> sizes in bytes?
I already agreed there was no harm. You didn't like my answer for some reason.
Again:
>> No, they *can* make that possible. You're not their target audience
>> (namely, a nerd who doesn't program Windows). Hence, they haven't
>> implemented it. They spent their time on other things.
> Each file in a list having its size shown with a different unit is
> confusing. You can't visually see which of the files are larger and
> which ones are smaller.
Click the size column header and it sorts by size.
>>> Except that it doesn't tell that. If you try to copy it to another file
>>> system or an archive file, it will most probably end up taking a completely
>>> different amount of space.
>
>> Hence the "which size do you want" question. :-)
>
> The amount of bytes in the file. What's so damn hard to understand about
> that?
OK, now I ask you "how big is the directory? What's its size? How many bytes
in that Linux directory? What's so damn hard to understand? I just want to
know how many bytes are in it."
"How big is that process? How many bytes does it take in memory? What's so
hard to understand about that?"
Copy the file to another system or an archive file. That's three different
sizes. Copy the file to another file system may or may not lose the
compression. Copying it to an archive file is going to need it to carry the
encryption and ACL overhead as well as alternate streams. That's exactly my
point.
> The amount of bytes in the file. What's so damn hard to understand about
> that?
Because first you ask for the amount of bytes in the file, then you ask for
the amount of bytes you'd read if you opened and read the file. And that's
two different numbers.
>> I think showing it as a readable size ("1.7 meg") is reasonable.
>
> It may be reasonable for *one* file. It's unreasonable when you have 50
> files, each with different size units.
True.
> But Apple has decided to completely hide the actual size of the file from
> the file listing, for some incomprehensible reason.
Dunno about that.
>>> Yeah, start doing that to a dozen files, rather than seeing it in one
>>> glance in the file listing. It *is* extremely inconvenient.
>
>> If I want the total, I pick a dozen files and say "properties" and it tells
>> me the total.
>
> Do you have reading comprehension problems? I was not talking about totals.
The "that" wasn't really clear there. "Start doing that to a dozen files"
doesn't really say whether you mean "one at a time" or "all at once."
> Why are you defending Microsoft on this? I don't get it. What possible harm
> could there be, if there was some option somewhere to make Explorer show file
> sizes in bytes instead of rounding them?
I'm not defending Microsoft per se. I'm just saying you seem to think
there's some big important reason for this feature not to be here. I just
think it's that it didn't sell more copies of Windows. There would be no
downside to providing it except the need to spend resources providing it.
> Yeah, I see how implementing that would take years and years of work.
> This coming from the same person who in this very article posted links to
> tutorials where you could make an extension to do exactly that.
I didn't say years and year. Indeed, I said
>>> There are a zillion things that some people want.
Don't you see? I also gave examples of other things that other people want
that would be pretty trivial to provide, that aren't provided.
I'm not saying Microsoft did right not providing it. I'm just saying that
they're not catering to your personal needs, *and* I'm giving you the
resources to fix your pain.
Maybe I'm like Andrew: I've never needed to put two columns of file sizes
next to each other in explorer windows and compare them.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
>>> ...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++.
Nonsense. Every programming language and every scripting language supports
COM that I've seen. Didn't you tell me Haskell has a COM interface? I know
Tcl does. WSH does. C# has a particularly nice one. Python does.
OK, I'll grant that maybe postscript doesn't do COM. Whoops, nope, I take
that back. Ghostscript supports COM.
What language have you used on Windows that does *not* do COM? That would be
like having a language on Linux that doesn't support environment variables.
> 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?
They both come with Windows.
Obviously "last I checked" didn't include googling before you posted.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> No. Windows doesn't support them, so user have learned to live without
> them, and then they are claiming that they "don't need them" (one of the
> most common "windows'isms").
More like "Programmers learned to live without them." I'd classify that as a
good idea.
What do you *need* symlinks for? I've never found a good use except getting
around paths that are hard-coded that shouldn't be, or distributing files
from one directory onto multiple file systems due to not all file systems
having the same capabilities.
> If Windows had supported soft links from day one, they would probably be
> in pretty common use, and it would be unthinkable to drop them.
Possibly. That wouldn't necessarily be a good thing.
>> Software is written to not hard-code paths that don't need to be
>> hard-coded.
>
> Yeah, because that's the *only* thing soft links are used for.
Well, tell me what else you *need* them for that a configuration variable
wouldn't work just as well.
> You might yourself believe that, but I don't think it's true. I'm pretty
> certain that if Windows had supported soft links from the very beginning,
> you would today be defending them. (You would *especially* be defending
> them if Unix/Linux didn't support them, I'm pretty sure.)
Oh, give it a rest, Warp.
>> I think soft links are an abomination, and I've
>> only ever seen them used to basically correct flaws in software
>> configurations.
>
> Linux distros use them frequently to, for example, make "aliases" of
> libraries of different versions to an actual file which is fully compatible.
OK. Windows puts this information in the files themselves, and the code asks
to load the library with the compatible version. Or it looks up the
registration in the registry. (Hence the name, you see.)
The symlink solution works OK until the upgrade from libxyz.1.2.so to
libxyz.1.3.so breaks the program written to use libxyz.so. And dont tell me
it doesn't happen, as I have not infrequently binary-edited libraries to
change the strings there.
> In other words, if version 1.2.3 of a library is fully backwards compatible
> back to version 1.0.0 of the library, the "versionless" library (eg.
> "libsomething.so") file will usually be linked to the 1.2.3 version of the
> file (eg. "libsomething.so.1.2.3"), as well as the several versioned files
> (eg. "libsomething.so.1" would be a soft link to "libsomething.so.1.2.3" if
> the latter is fully backwards compatible with version 1).
Yes, I know how that works.
> This is not a question of "bad configuration".
Inadequate configuration. The program itself should be telling you which
versions it's compatible with, and the loader should be enforcing that. The
fact that you *can* do it with the file system doesn't mean that's a *good*
way to do it. :-)
> It's a question of
> practicality (an executable may have been linked against version 1.0.0 of
> the library, but it will work ok with the version 1.2.3, so the soft link
> will make it load that) and saving disk space (especially if the library is
> several megabytes in size).
This works less well when you have a bunch of programs that you don't have
the source for which may or may not break when you change library versions.
Hence, "DLL Hell". That's much less common when you can just test every
piece of software written for the platform when you change a library.
> And before you start nitpicking about how that could be solved in other
> ways (which I'm 100% sure you will do), that was just ONE EXAMPLE of many.
Sure. Let's hear some others. Seriously.
> (Another cool example is when a software package consists of several
> executables, each one doing slightly different things... But instead of
> having a 5-megabyte file for each executable, they are all in fact soft
> links to one single 6-megabyte executable which then acts different depending
> in which name was used to start it. Again, this saves disk space.)
Yep. This is what the whole busybox thing is about. Given that, the common
functionality ought be in a shared library. Otherwise, you're taking up more
memory than disk space.
Or in the Windows way, you have one tiny file that launches the library with
different arguments, so you don't have to depend on the file name not
changing in order to make it work. You know, like, a shortcut or something. :-)
How would a *user* use symlinks, is really what I want to hear. Not someone
managing software installations, but an end-user. Why would I want a symlink
in my home directory, for example?
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> Darren New <dne### [at] san rr com> wrote:
>> 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." :-)
>
> Most of which are very specific, support only a limited amount of
> functionalities, cannot be chained to perform more complex operations,
> are often inconvenient to use, large and heavy, and litter your system
> with tons of setup files and registry entries which it will leave there
> even after you uninstall the app.
http://gnuwin32.sourceforge.net/
Jeez, you're really harsh on those GNU guys. Most of those programs are
simple stand-along .exe files.
But that's OK. I understand that you're more into bitching about Windows
than you are in improving your experience, so carry on.
> Also if they do very low-level stuff,
> they usually don't integrate very well with Windows and its own apps
> (such as Windows Explorer).
Well, duh. How well does grep integrate with GNOME?
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
> Darren New wrote:
>
>> I put the task bar on the side. I can probably put 40 tabs on there
>> before it gets close to full.
>
> Logically that makes sense - especially if you have a widescreen
> monitor. But that would just be too weird - for no better reason than
> "it's not what I'm used to".
It wasn't what I was used to etiher, but I got used to it really quickly. I
resisted for years myself.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
>>> 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?
>>
>> For example, finding where in the file a symbol is defined instead of
>> used.
>>
>> I do that all the time. "Where is the definition of this macro?"
>
> As I say, I've never needed to do that. (Then again, I don't work with
> other people's code, only my own.)
Lucky you!
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New wrote:
> The symlink solution works OK until the upgrade from libxyz.1.2.so to
> libxyz.1.3.so breaks the program written to use libxyz.so. And dont tell
> me it doesn't happen, as I have not infrequently binary-edited libraries
> to change the strings there.
BTW, that said, I think it's more like this was a problem,a nd rather than
write code to fix the linker, people started making quicky patches using
symlinks.
Its a quick and simple solution to something that plagues MS for years and
years. I just don't think it's the *right* solution. I'm more of a code
and API kind of programmer than a file system and file format kind of
programmer.
>> This is not a question of "bad configuration".
>
> Inadequate configuration. The program itself should be telling you which
> versions it's compatible with, and the loader should be enforcing that.
> The fact that you *can* do it with the file system doesn't mean that's a
> *good* way to do it. :-)
Oh, and you'll notice that Linux goes thru all the libraries when it starts
anyway to gather up version information, and you'll notice that GNU has
defined a library format that has a textual description of which libraries
you *really* want to load. Both of these are a better (IMO) solution than
using symlinks. And not because Windows doesn't have symlinks, but because
it's less fragile.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New <dne### [at] san rr com> wrote:
> > So in order to get Windows Explorer to show exact byte counts, I would have
> > to download and install Visual Studio, get it to work, write an extension
> > manually, install it, and keep it with me in an USB stick so that I can
> > install it in a friend's computer if I ever want to see the byte sizes there
> > as well?
> Pretty much, yah. Same as any other program you write. What did you expect?
I expect Windows to support such a *basic* feature as showing the sizes of
files in bytes. It's not like it's too much to ask. I'm sure someone at MS
could add the feature in 5 minutes. In fact, I wouldn't even be surprised
that they *already* have the feature but it has been disabled with an #ifdef,
so all it would take to support it is one additional #define.
But they don't. Why not? I have no idea.
> You mean if I want to indent files the way I like, I have to download emacs,
> write some elisp code, then stick it on a USB stick and carry it around to
> every other emacs-enabled computer?
Yeah, because indenting code is in the exact same league as showing file
sizes in bytes rather than rounded.
> > I think you made some kind of claim containing the word "trivial" in some
> > post of yours.
> More trivial than rewriting the shell. A 50-line program is pretty trivial, yes?
No. Trivial is "click here and here, and you are done".
You have a rather odd definition of "trivial". It still sounds like "not
impossible".
> >>>> And which byte count do you want?
> >>> The size of the file. How many bytes it contains. If I opened it with a
> >>> program and started reading bytes, how many I would get before EOF.
> >
> >> Open it raw, or processed, or for backup?
> >
> > You are nitpicking, and you know it.
> You're nitpicking. You want exact byte counts in one window but not the
> other.
What? What window? What other window? I have no idea what you are talking
about.
The only thing I want is an option somewhere that, when checked, will make
Windows Explorer to show file sizes in bytes instead of rounded to kilobytes
or megabytes. That's it. Nothing less, nothing more.
> It's trivial to get that information
I don't want to "get that information". I want Explorer to use bytes when
listing files and their sizes. "Getting" is too laborious. I don't want to
"get" anything, I want it to show it without me doing anything to "get" it
explicitly.
> yet you complain it's difficult.
It's extremely inconvenient and slow. I want a full list of a directory
with file sizes in bytes. That's all. I don't want to have to open some
separate info dialog on every single file just to see the size in bytes.
That's just crazy.
It's not like it would be away from anybody. If someone doesn't want to
see the sizes in bytes, he just doesn't use that specific option. It's that
simple.
> Plus, you can't even clearly define what it is you want to see.
You know *perfectly* what I mean, so stop acting stupid. You are just
arguing for the sake of argument.
> > Is agreeing with something really so hard?
> I already agreed. You kept bashing at it.
"you can't even clearly define what it is you want to see" doesn't sound to
me like agreeing.
> > So if I want to see the individual byte sizes of 20 files, exactly how do
> > I do that "with one extra step"?
> "dir"
You have an odd definition of "one extra step".
Pressing the keys 'd', 'i', 'r' and return is certainly not enough. There
are quite many additional steps involved, including going somewhere else than
Windows Explorer.
> > Each file in a list having its size shown with a different unit is
> > confusing. You can't visually see which of the files are larger and
> > which ones are smaller.
> Click the size column header and it sorts by size.
That doesn't give me visual feedback on the sizes of the files. It only
tells me which files are larger than the others. It doesn't tell me how
much, unless I start deciphering the units one by one.
> >>> Except that it doesn't tell that. If you try to copy it to another file
> >>> system or an archive file, it will most probably end up taking a completely
> >>> different amount of space.
> >
> >> Hence the "which size do you want" question. :-)
> >
> > The amount of bytes in the file. What's so damn hard to understand about
> > that?
> OK, now I ask you "how big is the directory? What's its size? How many bytes
> in that Linux directory? What's so damn hard to understand? I just want to
> know how many bytes are in it."
I'm not interested in the size of a directory. I interested in seeing the
sizes of the files in bytes, that's all.
(Seeing the total size of the files in bytes without having to do anything
extra to get it is useful as well, but a somewhat different issue.)
> "How big is that process? How many bytes does it take in memory? What's so
> hard to understand about that?"
I'm not interested in that in this context.
> Copy the file to another system or an archive file. That's three different
> sizes. Copy the file to another file system may or may not lose the
> compression. Copying it to an archive file is going to need it to carry the
> encryption and ACL overhead as well as alternate streams. That's exactly my
> point.
So what? I'm not interested in how much disk space the file is taking.
I'm interested in its size in bytes. If disk usage is what one wants, *that*
can be put in some info dialog or whatever you want.
> > The amount of bytes in the file. What's so damn hard to understand about
> > that?
> Because first you ask for the amount of bytes in the file, then you ask for
> the amount of bytes you'd read if you opened and read the file. And that's
> two different numbers.
Why do you keep nitpicking? You understand perfectly what I'm talking about.
> >>> Yeah, start doing that to a dozen files, rather than seeing it in one
> >>> glance in the file listing. It *is* extremely inconvenient.
> >
> >> If I want the total, I pick a dozen files and say "properties" and it tells
> >> me the total.
> >
> > Do you have reading comprehension problems? I was not talking about totals.
> The "that" wasn't really clear there. "Start doing that to a dozen files"
> doesn't really say whether you mean "one at a time" or "all at once."
If Windows Explorer showed sizes in bytes for each individual file *and*
for the total (in the status bar), then it would solve both problems at
once, without the need to open any info dialogs. See? Easy.
> I'm not defending Microsoft per se. I'm just saying you seem to think
> there's some big important reason for this feature not to be here.
Well, I have yet to see a good reason for it to not to be there.
(Except Microsoft's incompetence. This is certainly not the only
annoying feature which worked ok eg. on Windows 3 but MS decided to
screw it up for newer versions just for the sake of making it different,
even at the cost of making it usable.)
> I just
> think it's that it didn't sell more copies of Windows. There would be no
> downside to providing it except the need to spend resources providing it.
There are tons of way more useless features in Windows than this. Features
which almost nobody uses. They didn't have resource problems for those.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New <dne### [at] san rr com> wrote:
> What do you *need* symlinks for?
What do you *need* directories for? Useless. Just use a naming convention.
What do you *need* long file names for? 8 characters are plenty for any
amount of files you might need. Useless to have anything larger.
What do you *need* Windows shortcuts for? It's not like the system
couldn't work without them.
If we start dropping everything that is not absolutely necessary, we could
get a pretty bare-bones system.
On the other hand, other people find convencience features useful.
> > You might yourself believe that, but I don't think it's true. I'm pretty
> > certain that if Windows had supported soft links from the very beginning,
> > you would today be defending them. (You would *especially* be defending
> > them if Unix/Linux didn't support them, I'm pretty sure.)
> Oh, give it a rest, Warp.
You are not giving me much reason to.
> >> I think soft links are an abomination, and I've
> >> only ever seen them used to basically correct flaws in software
> >> configurations.
> >
> > Linux distros use them frequently to, for example, make "aliases" of
> > libraries of different versions to an actual file which is fully compatible.
> OK. Windows puts this information in the files themselves, and the code asks
> to load the library with the compatible version. Or it looks up the
> registration in the registry. (Hence the name, you see.)
And once again we have a hard-coded, specific feature which will work
*only* for dll files but nothing else which might be similar.
Generic solutions are much more useful than hard-coded, specific ones.
> The symlink solution works OK until the upgrade from libxyz.1.2.so to
> libxyz.1.3.so breaks the program written to use libxyz.so.
Yeah, I see how programs are constantly breaking when libraries are
updated.
Seemingly you missed the "if the library is backwards-compatible" part.
If it isn't, then it will not be sym-linked so that programs will believe
it's the same library, of course.
> And dont tell me it doesn't happen
I don't remember personally ever seeing it happen in my computer.
OpenSUSE repositories are pretty competent at handling dependencies
properly.
> > In other words, if version 1.2.3 of a library is fully backwards compatible
> > back to version 1.0.0 of the library, the "versionless" library (eg.
> > "libsomething.so") file will usually be linked to the 1.2.3 version of the
> > file (eg. "libsomething.so.1.2.3"), as well as the several versioned files
> > (eg. "libsomething.so.1" would be a soft link to "libsomething.so.1.2.3" if
> > the latter is fully backwards compatible with version 1).
> Yes, I know how that works.
Then why are you asking for examples if you know that?
> > This is not a question of "bad configuration".
> Inadequate configuration. The program itself should be telling you which
> versions it's compatible with
Most programs do. You can use the 'ldd' utility to check which .so files
they depend on, and usually they do have the version number. (Then if you
check the actual .so file itself, you'll usually see that it's a soft link
to a compatible version of the library.)
As said, if program A depends on libSomething.so.3 and program B depends
on libSomething.so.4, and the latter happens to be fully compatible with
the former, it would be a waste of disk space to have both. Instead, the
former is simply made a symbolic link which points to the latter.
> and the loader should be enforcing that. The
> fact that you *can* do it with the file system doesn't mean that's a *good*
> way to do it. :-)
Instead, you want to hard-code such specific features as .so file versions
into a loader routine.
What happens if you are dealing with something similar, but which is not
a bunch of .so files which are loaded by a loader routine?
> > And before you start nitpicking about how that could be solved in other
> > ways (which I'm 100% sure you will do), that was just ONE EXAMPLE of many.
> Sure. Let's hear some others. Seriously.
Why? For any possible example I could mention you will come up with a
contrived reason why it's "better" to do it in some other way. Just for
the sake of argument.
> How would a *user* use symlinks, is really what I want to hear. Not someone
> managing software installations, but an end-user. Why would I want a symlink
> in my home directory, for example?
Have you ever heard of "shortcuts" in Windows? They are like a poor-man's
symbolic link.
Why would a user need those?
(Yes, go on an rant about how these "shortcuts" are so much infinitely
better than symbolic links. After you have done, please explain to me why
shortcuts *are* useful to regular users while symbolic links *aren't*.
You are insinuating that symbolic links would be completely useless for
regular users. "Shortcuts" are functionally the same, and are being
constantly used in Windows. Are you arguing they are also completely
useless?)
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
>> From what I've seen, you can't touch COM unless you're programming in
>> C or C++.
>
> Nonsense. Every programming language and every scripting language
> supports COM that I've seen.
I've yet to find a language that can do it.
> Didn't you tell me Haskell has a COM interface?
Yes, but it doesn't compile on Windows. (That's The Real WTF, right
there!) Then again, a few people have hinted that it's possible to do
things like COM, ODBC, etc on Unix too...
> I know Tcl does.
With an extension? Or natively? I don't recall seeing anything about it
in the docs. (I did find DDE, however. And registry access.)
> OK, I'll grant that maybe postscript doesn't do COM. Whoops, nope, I
> take that back. Ghostscript supports COM.
PostScript does a lot more than many people realise...
> What language have you used on Windows that does *not* do COM? That
> would be like having a language on Linux that doesn't support
> environment variables.
Java, Smalltalk, Eiffel, JavaScript, Tcl, Haskell, POV-Ray (well, duh!)
As far as I know, none of them support it. (As I say, there's a Haskell
library, but it doesn't work. And even if it did, some documentation
would be nice...)
>> 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?
>
> They both come with Windows.
>
> Obviously "last I checked" didn't include googling before you posted.
As I posted in another thread, it appears that WSH now comes with
Windows. Obviously this is kind of game-changing; it changes it from a
novel curiosity to something that might have a real-world use...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> I expect Windows to support such a *basic* feature as showing the sizes of
> files in bytes.
It does. It just doesn't show it *where you want it*. It has shown file
sizes in bytes since before there were windows involved.
> I'm sure someone at MS could add the feature in 5 minutes.
Uh, no. Nothing happens in five minutes in MS. How long do you think it
takes to even translate the help files and header text into 105 different
languages?
> But they don't. Why not? I have no idea.
Did you ask them?
>> More trivial than rewriting the shell. A 50-line program is pretty trivial, yes?
> No. Trivial is "click here and here, and you are done".
And you can do that too. Click "open command window here" then click "d" and
then click "i" and then click "r" and then click "enter."
> You have a rather odd definition of "trivial". It still sounds like "not
> impossible".
No, I mean adding your own extensions is well supported and well documented.
A small extension is short.
But no, it's not in there by default, and they could add it as easily as
they add any other trivial feature, but they haven't.
>>>>>> And which byte count do you want?
>>>>> The size of the file. How many bytes it contains. If I opened it with a
>>>>> program and started reading bytes, how many I would get before EOF.
>>>> Open it raw, or processed, or for backup?
>>> You are nitpicking, and you know it.
>
>> You're nitpicking. You want exact byte counts in one window but not the
>> other.
>
> What? What window? What other window? I have no idea what you are talking
> about.
The properties window or the cmd.exe window.
> The only thing I want is an option somewhere that, when checked, will make
> Windows Explorer to show file sizes in bytes instead of rounded to kilobytes
> or megabytes. That's it. Nothing less, nothing more.
I understand that.
> It's extremely inconvenient and slow. I want a full list of a directory
> with file sizes in bytes. That's all.
09/24/2009 18:39 231,936 XpsRasterService.dll
09/24/2009 19:00 3,068,416 xpsservices.dll
01/20/2008 19:48 942,592 XPSSHHDR.dll
01/20/2008 19:49 2,935,808 xpssvcs.dll
12/31/2006 21:00 625,152 xvidcore.dll
12/31/2006 21:00 120,320 xvidvfw.dll
09/18/2006 14:39 2,650 xwizard.dtd
01/20/2008 19:50 353,280 xwizards.dll
11/02/2006 04:19 94,208 xwreg.dll
01/20/2008 19:49 111,104 xwtpw32.dll
11/08/2008 17:38 <DIR> zh-CHS
11/08/2008 17:30 <DIR> zh-CHT
02/24/2010 16:09 <DIR> zh-CN
12/10/2009 20:05 <DIR> zh-HK
02/24/2010 16:09 <DIR> zh-TW
08/29/2007 17:06 61,952 ZIMF.DLL
04/11/2009 00:11 387,072 zipfldr.dll
08/29/2007 17:06 127,488 ZSPOOL.DLL
08/29/2007 17:06 52,224 ZTAG.DLL
2344 File(s) 1,122,038,817 bytes
98 Dir(s) 57,167,736,832 bytes free
>> Plus, you can't even clearly define what it is you want to see.
>
> You know *perfectly* what I mean, so stop acting stupid. You are just
> arguing for the sake of argument.
I know what *you* mean. I'm just saying that it's not as simple as you
think if you want it usable by more than just you. Perhaps you're just used
to open source, where you can scratch your own personal itch *and* get it
into the official distribution?
>> I already agreed. You kept bashing at it.
>
> "you can't even clearly define what it is you want to see" doesn't sound to
> me like agreeing.
I agreed it would be trivial to put something like this in Windows. I didn't
agree that you can clearly define what you want. ;-)
> You have an odd definition of "one extra step".
If you want sizes for multiple files, then yes, it's maybe five seconds of
work instead of two extra clicks. Maybe four or five mouse clicks, and then
four button presses.
>> OK, now I ask you "how big is the directory? What's its size? How many bytes
>> in that Linux directory? What's so damn hard to understand? I just want to
>> know how many bytes are in it."
>
> I'm not interested in the size of a directory. I interested in seeing the
> sizes of the files in bytes, that's all.
And I'm explaining why, under Windows, that question is ambiguous, by
providing an analogy that shows "how big is it" doesn't always have a
trivial answer.
>> "How big is that process? How many bytes does it take in memory? What's so
>> hard to understand about that?"
>
> I'm not interested in that in this context.
It was an analogy to explain why what *you* want isn't what everyone else
wants. You want "how big would this file be if the only access was
UNIX-style access".
> So what? I'm not interested in how much disk space the file is taking.
But most other people are. Hence the default UI.
> I'm interested in its size in bytes. If disk usage is what one wants, *that*
> can be put in some info dialog or whatever you want.
Indeed, it is.
>>> The amount of bytes in the file. What's so damn hard to understand about
>>> that?
>
>> Because first you ask for the amount of bytes in the file, then you ask for
>> the amount of bytes you'd read if you opened and read the file. And that's
>> two different numbers.
>
> Why do you keep nitpicking? You understand perfectly what I'm talking about.
I'm nitpicking to show that what *you* ask for is different than what many
other people might ask for, even tho they'll all describe it the same way.
I *do* understand what you ask for. Then you ask me "why can't Microsoft do
that?" And I'm explaining that what you ask for isn't general enough to
sell to hundreds of millions of people, and then you get mad for trying to
explain that.
> If Windows Explorer showed sizes in bytes for each individual file *and*
> for the total (in the status bar), then it would solve both problems at
> once, without the need to open any info dialogs. See? Easy.
Indeed it would!
>> I'm not defending Microsoft per se. I'm just saying you seem to think
>> there's some big important reason for this feature not to be here.
>
> Well, I have yet to see a good reason for it to not to be there.
The same reason there's no future value calculations in the calculator. It's
a lot of work for Microsoft to put features in.
> There are tons of way more useless features in Windows than this. Features
> which almost nobody uses. They didn't have resource problems for those.
And you have good statistics for what features get used most on Windows?
Really? Where can *I* see those? Or did you work for that department in
Microsoft or something else proprietary?
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
>>> From what I've seen, you can't touch COM unless you're programming
>>> in C or C++.
>>
>> Nonsense. Every programming language and every scripting language
>> supports COM that I've seen.
>
> I've yet to find a language that can do it.
I've named half a dozen. What languages do you use?
>> Didn't you tell me Haskell has a COM interface?
>
> Yes, but it doesn't compile on Windows.
Are you sure it's "it doesn't compile" and not "I don't know how to compile it"?
>> I know Tcl does.
>
> With an extension? Or natively? I don't recall seeing anything about it
> in the docs. (I did find DDE, however. And registry access.)
http://www.vex.net/~cthuang/tcom/
Extensions *are* native. Tcl is a language for writing extensions in.
>> What language have you used on Windows that does *not* do COM? That
>> would be like having a language on Linux that doesn't support
>> environment variables.
>
> Java, Smalltalk, Eiffel, JavaScript, Tcl, Haskell, POV-Ray (well, duh!)
> As far as I know, none of them support it.
In other words, you didn't take the time to google
java "com interface"
smalltalk "com interface"
eiffel "com interface"
tcl "com interface"
before you said you have no languages that support it.
Javascript per se doesn't, but jscript does, which is pretty much the same
thing with a different name.
OK, POV-Ray doesn't. It uses a different mechanism for some unknown reason
to supply the "GUI Extension" function.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New <dne### [at] san rr com> wrote:
> > But they don't. Why not? I have no idea.
> Did you ask them?
Yeah, like they are going to answer me.
> And you can do that too. Click "open command window here"
Do they have that in Vista? There's an extension for XP (doesn't come by
default, naturally), but it only makes it just slightly less inconvenient.
> > It's extremely inconvenient and slow. I want a full list of a directory
> > with file sizes in bytes. That's all.
> 09/24/2009 18:39 231,936 XpsRasterService.dll
> 09/24/2009 19:00 3,068,416 xpsservices.dll
> 01/20/2008 19:48 942,592 XPSSHHDR.dll
> 01/20/2008 19:49 2,935,808 xpssvcs.dll
> 12/31/2006 21:00 625,152 xvidcore.dll
> 12/31/2006 21:00 120,320 xvidvfw.dll
> 09/18/2006 14:39 2,650 xwizard.dtd
> 01/20/2008 19:50 353,280 xwizards.dll
> 11/02/2006 04:19 94,208 xwreg.dll
> 01/20/2008 19:49 111,104 xwtpw32.dll
> 11/08/2008 17:38 <DIR> zh-CHS
> 11/08/2008 17:30 <DIR> zh-CHT
> 02/24/2010 16:09 <DIR> zh-CN
> 12/10/2009 20:05 <DIR> zh-HK
> 02/24/2010 16:09 <DIR> zh-TW
> 08/29/2007 17:06 61,952 ZIMF.DLL
> 04/11/2009 00:11 387,072 zipfldr.dll
> 08/29/2007 17:06 127,488 ZSPOOL.DLL
> 08/29/2007 17:06 52,224 ZTAG.DLL
> 2344 File(s) 1,122,038,817 bytes
> 98 Dir(s) 57,167,736,832 bytes free
I wish Windows Explorer listed it like that. But it doesn't.
> And I'm explaining why, under Windows, that question is ambiguous, by
> providing an analogy that shows "how big is it" doesn't always have a
> trivial answer.
You yourself gave an unambiguous answer in the above listing.
And Windows Explorer already shows the proper file size. The problem is
that it's rounded.
> > So what? I'm not interested in how much disk space the file is taking.
> But most other people are. Hence the default UI.
Windows Explorer doesn't show the disk space the file is taking. It shows
the size of the file (rounded).
It's MacOS X Finder which shows the disk space rather than the file size.
I have hard time believing Mac users are interested in seeing how much disk
space a file takes instead of seeing the file size. (I bet most of them don't
even know the difference and would be none the wiser if it was changed.)
On the contrary, it's irritating because it's very confusing. I'm not
really interested in how much disk space the files are taking. I don't do
anything with that info. (The only info which may be interesting to me is
seeing how much free space there is left, not how much disk space every
individual file is taking. That's just useless information.)
> > There are tons of way more useless features in Windows than this. Features
> > which almost nobody uses. They didn't have resource problems for those.
> And you have good statistics for what features get used most on Windows?
> Really? Where can *I* see those? Or did you work for that department in
> Microsoft or something else proprietary?
How many regular Windows users even *know* that there's a program called
'dxdiag' or another called 'regedit', much less have ever launched them?
*Those*, if any, are hacker tools, not regular user tools. Yet they are
like a million times more complicated than adding a simple option to
Windows Explorer, and they come by default with Windows.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Darren New <dne### [at] san rr com> wrote:
> >> Didn't you tell me Haskell has a COM interface?
> >
> > Yes, but it doesn't compile on Windows.
> Are you sure it's "it doesn't compile" and not "I don't know how to compile it"?
I wouldn't even be surprised if it was a case of "I haven't even tried
compiling it; I just saw a random forum message about the subject a couple
of years ago". ;)
> OK, POV-Ray doesn't. It uses a different mechanism for some unknown reason
> to supply the "GUI Extension" function.
Which came first, COM or POV-Ray GUI extensions?
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> If we start dropping everything that is not absolutely necessary, we could
> get a pretty bare-bones system.
Sure. Like, UNIX v7 or something. :-)
I'm not saying they can't be handy. I just don't find them particularly
useful myself, and I don't think they solve probems.
>> Oh, give it a rest, Warp.
> You are not giving me much reason to.
I haven't turned anything into personal attacks.
> And once again we have a hard-coded, specific feature which will work
> *only* for dll files but nothing else which might be similar.
Or use the registry. :-) And yes, I think that's sometimes a good idea,
because it gives you a place to leverage when you have to change something.
If all your configuration control is based on symlinks and then you want
something more powerful, it's very difficult to backpatch everything after
the fact.
For example, if you base your configuration on ini files, you're pretty
screwed if you need something more complicated, or if you want to go into a
multi-user system where individual users don't have permissions to change
global ini files. If you base your configuration on an API to read and
write ini files, then you can reimplement that API to store the ini files in
the registry or in a per-user directory. Unless, of course, you have a
program that bypasses the API and tries to write ini files directly into
c:\program files, which causes all kinds of trouble and hackage to fix.
Basically, you're saying "if you don't encapsulate stuff, you can use it
more easily for completely unrelated applications." I find encapsulation is
more future-proof.
> Generic solutions are much more useful than hard-coded, specific ones.
Sure, symlinks can be used for other things too.
>> The symlink solution works OK until the upgrade from libxyz.1.2.so to
>> libxyz.1.3.so breaks the program written to use libxyz.so.
>
> Yeah, I see how programs are constantly breaking when libraries are
> updated.
Were you, by chance, using UNIX variants before Linux had package
management? Because, ya know, I was, and it sucked.
> Seemingly you missed the "if the library is backwards-compatible" part.
That works great until the new library (say) fixes a bug the old library
had, and programs that worked around the bug now break, and programs that
expect it fixed break if you don't.
"Backwards compatible" isn't a binary choice.
>> And dont tell me it doesn't happen
>
> I don't remember personally ever seeing it happen in my computer.
> OpenSUSE repositories are pretty competent at handling dependencies
> properly.
Sure. If everything comes from the repository, you're golden. I'm talking
about stuff not from the repository.
>>> In other words, if version 1.2.3 of a library is fully backwards compatible
>>> back to version 1.0.0 of the library, the "versionless" library (eg.
>>> "libsomething.so") file will usually be linked to the 1.2.3 version of the
>>> file (eg. "libsomething.so.1.2.3"), as well as the several versioned files
>>> (eg. "libsomething.so.1" would be a soft link to "libsomething.so.1.2.3" if
>>> the latter is fully backwards compatible with version 1).
>
>> Yes, I know how that works.
>
> Then why are you asking for examples if you know that?
I hadn't remembered that one. Plus, I was really looking for an example
where *users* would care about symlinks, rather than system administrators.
You gripe that explorer doesn't let you make symlinks. That seemed an odd
gripe if the reason you want them is to manipulate shared library versioning
schemes. It sounded more like a gripe about not being able to have your
music library organized the way you want on your desktop.
> As said, if program A depends on libSomething.so.3 and program B depends
> on libSomething.so.4, and the latter happens to be fully compatible with
> the former, it would be a waste of disk space to have both. Instead, the
> former is simply made a symbolic link which points to the latter.
Yep. You don't really need a *sym* link for that, tho.
> What happens if you are dealing with something similar, but which is not
> a bunch of .so files which are loaded by a loader routine?
Give me an example?
>>> And before you start nitpicking about how that could be solved in other
>>> ways (which I'm 100% sure you will do), that was just ONE EXAMPLE of many.
>
>> Sure. Let's hear some others. Seriously.
>
> Why? For any possible example I could mention you will come up with a
> contrived reason why it's "better" to do it in some other way. Just for
> the sake of argument.
No, because I'm actually interested. Every time someone says "symlinks
rulez" I ask for examples. Virtually nobody gives me decent examples of why
someone would prefer them over hard links, except in very specific
circumstances having to do with crossing file systems.
>> How would a *user* use symlinks, is really what I want to hear. Not someone
>> managing software installations, but an end-user. Why would I want a symlink
>> in my home directory, for example?
>
> Have you ever heard of "shortcuts" in Windows? They are like a poor-man's
> symbolic link.
No, they're interpreted by the shell. They're more like aliases in bash.
> (Yes, go on an rant about how these "shortcuts" are so much infinitely
> better than symbolic links. After you have done, please explain to me why
> shortcuts *are* useful to regular users while symbolic links *aren't*.
Shortcuts are useful because they provide more than just a symlink. They
provide a place to store settings for an executable program, they eliminate
a "path" variable that's 90K long (given that there's no central authority
regulating what you name your program, and you wind up clobbering things if
you put everything into "/bin").
Given that, people have made shortcuts on their desktop to point to network
shares and such, so I see the point, yes. If Windows had symlinks before
shortcuts, Windows probably wouldn't have shortcuts and would probably store
the auxiliary information in a different part of the symlink file or something.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> Darren New <dne### [at] san rr com> wrote:
>>> But they don't. Why not? I have no idea.
>
>> Did you ask them?
>
> Yeah, like they are going to answer me.
I know. I was being mildly sarcastic.
> Do they have that in Vista?
Yes. Sadly, no "open administrative command line here".
> There's an extension for XP (doesn't come by
> default, naturally), but it only makes it just slightly less inconvenient.
Yes. (Lots less, actually, I've found.)
> I wish Windows Explorer listed it like that. But it doesn't.
Yep.
>> And I'm explaining why, under Windows, that question is ambiguous, by
>> providing an analogy that shows "how big is it" doesn't always have a
>> trivial answer.
>
> You yourself gave an unambiguous answer in the above listing.
That's only unambiguous because that's the one they picked.
> And Windows Explorer already shows the proper file size. The problem is
> that it's rounded.
Are you sure?
Actually, it's not showing the file size. It's showing the file last byte
marker. The file could have more data after that, or could be missing data
before that. I can give you a file that shows that number as three million
that has *no* data associated with the file, simply by deleting the bytes
off the start of the file.
>>> So what? I'm not interested in how much disk space the file is taking.
>
>> But most other people are. Hence the default UI.
>
> Windows Explorer doesn't show the disk space the file is taking. It shows
> the size of the file (rounded).
Not quite "size of the file", no. If there are holes in the file, or if
there are alternate streams holding data, neither of those is "the size of
the file". It's more "the place data would get appended were you to append
it to the primary data stream." :-) There's undoubtably an unambiguous name
for that that Microsoft has decided upon.
Perhaps "number of bytes you could read from the file if you first copied it
to a file system that didn't support the stuff NTFS does" or some such.
> It's MacOS X Finder which shows the disk space rather than the file size.
I can't argue for that. But I strongly suspect Apple has done more research
into what people want in MacOS than you have. :-)
> How many regular Windows users even *know* that there's a program called
> 'dxdiag' or another called 'regedit', much less have ever launched them?
I suspect quite a few have used dxdiag when their game didn't run, actually.
The regedit I'll grant you is probably only used by people knowing what
they're doing.
But now you're asking me to justify Microsoft not writing some piece of
code. I don't know. I'm just listing possible reasons, and you're saying
"that's not good enough for me, dammit!"
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 22-4-2010 0:39, Gilles Tran wrote:
> "andrel" <byt### [at] gmail com> a écrit dans le message de groupe de
> discussion : 4BC### [at] gmail com...
>> On 21-4-2010 22:39, Warp wrote:
>>> I really got once stuck because I just *couldn't* find what I was
>>> searching for. I knew the string was in some files and I wanted to know
>>> which of them, but the damn thing simply refused to tell me, no matter
>>> what I tried. (IIRC I was searching for C++ files which include a
>>> specific
>>> header or something like that. I ended up having to figure that out by
>>> other means.)
>>
>> Seems like you have the same problem as me.
>
> Google for messages about search not finding [programming language name]
> files in [windows version]. The general trick is to tell windows to
> index these files and not just the default ones but how to do this is
> version-specific (and well-hidden, particularly in XP). It's indeed
> annoying (I have to search for this at least once a year) but it's not
> exactly difficult to find for folks who program for a living ;)
Matlab files with extension .m in XP
no luck but your google skills are way beyond mine anyway.
Do you have an idea why it would not find those or look into them
anyway? Because if I had a theory about that I could try to find a cure.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> Which came first, COM or POV-Ray GUI extensions?
COM was originally OLE, which was around in Win3 days. Certainly by Win98 it
was a well-established technology.
The only reason I said "unknown reason" is that the windows interface only
works on Windows. The reason for using INI files instead of the INI API is
portability, I'd expect. That wouldn't be an issue with COM and the Windows
editor/interface thing.
I don't know enogh about the history of COM and the Windows port of POV-Ray
to know whether COM could do what the GUI extensions needed when they were
written.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Orchid XP v8 wrote:
> With an extension? Or natively? I don't recall seeing anything about it
> in the docs. (I did find DDE, however. And registry access.)
That said, it's in ActiveState's teapot, so in a sense it's "native" and
"comes with Tcl".
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
andrel wrote:
> Do you have an idea why it would not find those or look into them
> anyway? Because if I had a theory about that I could try to find a cure.
Because it doesn't know how to index them.
It knows where to look in a jpeg to get the metadata. It knows where to look
in a Word file to understand when something is in a different language. You
don't want search finding "Fred" in a jpeg image body, or "Fred" in a word
document in Big-5.
You have to tell the search engine that .m files can be indexed like text.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> What do you *need* directories for? Useless. Just use a naming convention.
BTW, most microcomputer OSes, including DOS and CP/M and MacOS didn't have
directories. So, yeah. :-)
> If we start dropping everything that is not absolutely necessary, we could
> get a pretty bare-bones system.
You'd have FORTH, I expect. ;-)
> Have you ever heard of "shortcuts" in Windows? They are like a poor-man's
> symbolic link.
Thinking on this, one primary difference is that shortcuts don't
*automatically* get followed if the program doesn't specifically prevent
that. I'm not sure that's as useful as the ability to have one file that
acts as a reference to another file.
See, here's my thinking. Given that people don't really type long paths on
Windows very much (at least not as much as UNIX), having a program follow a
link like that automatically doesn't especially seem helpful, especially if
it points to a file system with different semantics (like a network share,
say). Pretty much all but the simplest programs on UNIX have to handle
symlinks anyway, whether they're recursing a directory (like find or grep or
backups or whatever) or whether they're just moving files around (like "mv"
needing to know if it's the same file system or not). A user on Windows
tends to launch a shortcut and it comes up in a window, whether it points to
a file or a directory or something. If they're navigating, they're doing it
one step at a time, so having it happen automatically in the middle of a
path doesn't seem as useful in that situation. But maybe usage patterns
would be different if they were around earlier, sure. Shortcuts were clearly
a hack to support not having a huge PATH variable that grew into a more
general mechanism over time.
(BTW, Windows2000 supported junction points, which are the higher-level
abstraction on which mounted file systems and symbolic links and remote
files are all based. Again, it just didn't come with the OS, but you could
buy programs that did it. Just FYI.)
> (Yes, go on an rant about how these "shortcuts" are so much infinitely
> better than symbolic links.
BTW, I'm not the one "ranting". I'm discussing stuff rationally, I think.
--
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On 22-4-2010 21:21, Darren New wrote:
> andrel wrote:
>> Do you have an idea why it would not find those or look into them
>> anyway? Because if I had a theory about that I could try to find a cure.
>
> Because it doesn't know how to index them.
>
> It knows where to look in a jpeg to get the metadata. It knows where to
> look in a Word file to understand when something is in a different
> language. You don't want search finding "Fred" in a jpeg image body, or
> "Fred" in a word document in Big-5.
>
> You have to tell the search engine that .m files can be indexed like text.
>
Ah ok. And how do I do that? I'll find out next week after some deadlines.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|
 |