Re: Need help on modifying and assembly of a small program!

From: Frank Kotler (fbkotler_at_comcast.net)
Date: 02/17/05 

Date: Wed, 16 Feb 2005 19:56:50 -0500

Beth wrote:

> > But this changes the spaces in the "href"s to "%20"...
> > Necessary because some people think that unix-folk need
> > hassles like spaces in filenames :)
>
> Use quotes!! Any application that doesn't comprehend quoted arguments is
> technically "broken", as they are supposed to be perfectly permissible...

Sure... 'lynx "Some Damn File Name"' works like a charm.
Now, how do I add the quotes when I'd like to follow a link?
Quit lynx and start again with 'lynx "Some Other Damn File
Name"'? You can claim that anything but IE is "broken", if
you want, but your files still don't work.

> Now that PCs - Windows and Linux - don't have such "crippled" nonsense
> anymore, pardon that I'm now delighted that I can actually give files
> _NAMES_, rather than cryptic initials...well, at least you're only asking
> for the spaces to disappear...if you also insisted on "8.3" filenames, you
> can go doing it yourself!!

Spaces in the filenames aren't the problem. Spaces in the
"href"s are the problem, and Phil's "Perl routine" solves
it. It could use to be "wrapped" in a "script" - it only
removes *one* space per invokation. Something "automated"
that would remove all relevant spaces from all files... and
recurse subdirectories... would be easier... but it's
something we'll only need to do once. And, yes, we need to
quote the filenames when we feed 'em to the "script".

> Anyway, lest anyone think spaces in filenames is any kind of "Windows-ism",
> it isn't...

Okay, how many filenames with spaces in 'em do you find on
your Linux box, besides yours? I don't know *why* they're
not ordinarily used... they're "allowed"... Maybe it's
because I'm not the only one who finds 'em a big fat PITA?

...
> Well, talking to SourceForge "support", then, yes, this is basically the
> "gist" of it all: SourceForge have "black listed" Hotmail
> completely...

Ouch!!! There are a number of options... including "dump
SF". There really *is* supposed to be a human being at the
end of "postmaster@", I guess, but what would SF do with
one if they had one??? Hopefully, they'll quit being
stubborn... doubt if MS will...

...
> Microsoft ain't going to do anything because they hate "open source", SF
> "teaches them a lesson" by boycotting them completely and so on and so
> forth...

The funny thing is that MS has some "open source" software
hosted at SF! "Wix" or something. Or perhaps Nasm is no
longer the only project ever to have been booted off SF :)

> Yes, I am...well, okay, not currently...the machine is switched off...but
> that's the whole point with my "two machine" solution, Frank...I'm running
> both...
>
> I'd actually rather the Linux machine was the "connected" one

It would be nice, yes. With the "two machines" solution, you
can run both at once. If both machines were "connected",
both to the internet, and to each other (with the proper
/etc/sacrifice_chicken ritual observed, of course), that
would be perfect. With my "one machine" setup, I'm limited
to one or the other, at any one time... mostly it's "the
other" :) I really ought to just reformat that Windows
drive, I suppose...

...
> Ah, I'm sure it's probably possible but it'll be complicated and need to be
> "planned out", things bought, OSes re-installed, etc....a little "small
> project" rather than an "overnight" thing...

Tell me about it! I've been "planning" a simple upgrade
for... well, years, probably... I finally obtained a hard
drive (15G), and have it formatted with a Linux partition
and a swap partition - big enough this time, I hope. (my
current swap partition is 27M or something... and the *only*
problem I've had is building HLA. "hlaparse.c" is...
substantial :)

I boot into dos, and start Linux with "loadlin". In the
past, I've started "setup" with "loadlin", too, but now
loadlin reports that "setup.s has become too large for
loadlin - please contact the author about this situation"
(which I haven't). My machine won't boot from my current
cdrom, tho the bios setup offers to. I've obtained another
cdrom to try... all that remains is to move some crap so I
can get the case open, arrange some light on the subject,
and poke the cdrom in, as a "temporary" thing, and try it. I
could copy the files off the cd and install from disk, but
I'd *like* to see what "Joe User" sees with the current
"install" program...

Meanwhile, although "bit rot" is setting in, this
installation is still working... and serves as a test of
"legacy support"... or not...

Best,
Frank

Relevant Pages