Edit still available

I got to vi right after the editor I described earlier in this thread. It
was *wonderful*, like not banging my head against the wall any more.

Actually, I found vi very useful and easy to use. Not now, I'm very out of
practice, but a few of the commands were still at my fingertips the last
time I looked, two or three years ago.

Edlin isn't so bad for what it is - namely, a crappy editor

On Fri, 10 Jul 2009 09:04:03 -0400, Eric wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Even more fun than vi?
>
> "Dave" <Dave@beepbeepbeepbeep.com> wrote in message
> news:eH8s5jPAKHA.3708@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Edlin is available, too.
>>
>>
>> --
>> Windows 7 RC
>>
>>
>>
>> "Stubbo of Oz" <stubbo@invalid.invalid> wrote in message
>> news:sb1d55lj35cuo8t90ttn372kjui81v1rch@4ax.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> On Thu, 9 Jul 2009 16:57:58 -0700 (PDT), WhiteTea
>>> <WhiteTea77581@yahoo.com> wrote:
>>>
>>>>Is edit still available on a cmd window in Vista?
>>>>I would like to be able to edit batch files with in a cmd window.
>>>>
>>>>Thanks.
>>>
>>>
>>> Yes - you can check that yourself by opening a cmd window and
>>> entering:-
>>>
>>> edit /?
>>>
>>>
>>> --
>>> ----------------
>>> Stubbo of Oz
>>> ---------------- <!--colorc--><!--/colorc-->
>><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->


--
Gene E. Bloch letters0x40blochg0x2Ecom

 

On Fri, 10 Jul 2009 09:14:40 -0400, Tim Slattery wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "Gene E. Bloch" <not-me@other.invalid> wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
>>On Fri, 10 Jul 2009 11:42:36 +1000, . wrote:
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Maybe you have 64 bit windows?<!--colorc--><!--/colorc-->
>>
>>Maybe I do.
>>
>>So I take it there is no 32 or 64 bit version provided for victims like me?<!--colorc--><!--/colorc-->
>
> The "edit" command invokes edit.com. The *.com suffix means that it's
> a 16-bit real-mode program (and that it uses the tiny memory model, if
> you remember that far back in x86 programming practice). 16-bit
> programs don't run in MS's 64-bit operating systems, so you won't find
> it in 64-bit Vista.<!--colorc--><!--/colorc-->

Did I say I didn't understand that? I mostly wanted to pretend to complain,
thus the choice of the word "victim" above. And of course to thank <.> for
reminding me that x64 doesn't do 16-bit, and leaving me to realize *all by
myself* that edit is not .ge. 32 bits..

I go back way before 8088, BTW. 7090, 7094, HP 2100, Varian
something-or-other, Data General something-or-other, PDP-1, maybe PDP-8,
and a few others that nobody remembers, including me: some 24-bit machines,
18-bit machines, 16-bit machines, mostly in asm on the minicomputers.

My telephone is way more powerful than most of those. I have have put whole
operas in video on it as a proof of principle.

--
Gene E. Bloch letters0x40blochg0x2Ecom

 

On Fri, 10 Jul 2009 12:44:26 +1000, Stubbo of Oz wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> On Thu, 9 Jul 2009 18:34:35 -0700, "Gene E. Bloch"
> <not-me@other.invalid> wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
>>On Fri, 10 Jul 2009 10:05:01 +1000, Stubbo of Oz wrote:
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> On Thu, 9 Jul 2009 16:57:58 -0700 (PDT), WhiteTea
>>> <WhiteTea77581@yahoo.com> wrote:
>>>
>>>>Is edit still available on a cmd window in Vista?
>>>>I would like to be able to edit batch files with in a cmd window.
>>>>
>>>>Thanks.
>>>
>>>
>>> Yes - you can check that yourself by opening a cmd window and
>>> entering:-
>>>
>>> edit /?<!--colorc--><!--/colorc-->
>>
>>Will he get the same thing I did? Namely:
>>
>>'edit' is not recognized as an internal or external command,
>>operable program or batch file.<!--colorc--><!--/colorc-->
>
> What version of Vista are you using? It is definitely on my Vista Home
> Premium SP2.
>
> Location C:Windowssystem32edit.com<!--colorc--><!--/colorc-->

Yes, <.> answered that question in this thread just a bit before your post.
Edit is a 16-bit program, which x64 doesn't handle (by design, I suspect).
And I have x64

There is a bit of a discussion on that above, leading to a bit of shameless
& uncalled-for bragging on my part.

--
Gene E. Bloch letters0x40blochg0x2Ecom

 

On Jul 10, 7:02 am, WhiteTea <WhiteTea77...@yahoo.com> wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I am trying to find a freeware editor that works in a cmd window.
> UltaEdit is an editor but isn't freeware.
>
> If I can't find one, I may write a program in assembly.<!--colorc--><!--/colorc-->

Zeus Lite -

 

On Jul 10, 6:50 pm, "Gene E. Bloch" <not...@other.invalid> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I got to vi right after the editor I described earlier in this thread. It
> was *wonderful*, like not banging my head against the wall any more.
>
> Actually, I found vi very useful and easy to use. Not now, I'm very out of
> practice, but a few of the commands were still at my fingertips the last
> time I looked, two or three years ago.
>
> Edlin isn't so bad for what it is - namely, a crappy editor <!--colorc--><!--/colorc-->

If your OS goes night-night and all you can do is boot to a command
line,
then you'll have a expensive paperweight for a while.

Andy

 

On Jul 10, 6:40 pm, "mazorj" <maz...@verizon.net> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "WhiteTea" <WhiteTea77...@yahoo.com> wrote in message
>
> news:ea56daee-bd30-4e36-8306-07a93e4d5f58@37g2000yqp.googlegroups.com...
> On Jul 10, 2:48 pm, "mazorj" <maz...@verizon.net> wrote:
>
>
><!--coloro:green--><span style="color:green <!--/coloro-->
> > "Gene E. Bloch" <not...@other.invalid> wrote in
> > messagenews:1x177e1xt55ac$.kxbo6xyu89f5$.dlg@40tude.net...<!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > On Fri, 10 Jul 2009 11:20:39 +1000, . wrote:<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > >> There was once a web site, now gone, that showed how to use edlin
> > >> as a
> > >> newsreader.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > That must have been a lot of fun!<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > I must confess that edlin wasn't the worst editor I ever used. The
> > > worst
> > > was on an HP 2100MX (I'm a bit unsure of the number) - it was a
> > > mini-computer, back when there were such things - probably 1980 or
> > > so. I
> > > forget what they called the editor (although I had some ideas for
> > > a
> > > more
> > > accurate name).<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > One thing I remember: if you had scrolled down to, say, line 173,
> > > you
> > > couldn't go to line 172 or any line < 173 without writing the
> > > whole
> > > buffer
> > > and starting over from line 1. And that was one of the *good*
> > > features.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > --
> > > Gene E. Bloch letters0x40blochg0x2Ecom<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro-->
> > Twenty-five years ago I posted a comment in some forum to the effect
> > that if you're still using and liking edlin, you probably also enjoy
> > dentistry without anesthesia, mow your grass with a reel-action push
> > mower, and light your cigarettes by rubbing two sticks together.<!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro-->
> > They and edlin all would get the job done, but indeed, why would you
> > do it that way? Even then, the relatively simple DOS-based word
> > processors we had made writing and editing text files far, far
> > easier.<!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro-->
> > Can someone explain the OP's desire to edit batch (text) files in a
> > cmd window? Why not just load it into Notepad, or Notepad++ if
> > you're
> > doing coding?<!--colorc--><!--/colorc-->
>
> < "Different strokes for different folks."
> <
> < I don't do coding in a cmd window.
> <
> < I can often do things far faster in a command line than through a
> windows GUI.
>
> Um, okay, some people  are very adept at doing complex work in those
> black DOS-like boxes with nothing but command lines.  I'm not one of
> them, although I started with CP/M then DOS so I'm not uncomfortable
> with simple tasks there.  Vista is making all of us do a lot of >C:
> prompt calls to tweak its odd and otherwise inaccessible parameters.
>
> If you don't mind my asking, why the need for a cmd line editor to
> create/edit batch files?  You still have to open the editor, make your
> changes, then save and close it, so IMO there's not much of a penalty
> for opening Notepad, working there, then diving back into the cmd
> environment.
>
> But if it's just your personal preference to stay in the black cmd box
> for all your work, then I'll stop here - different strokes do indeed
> work for different folks.<!--colorc--><!--/colorc-->

You can do a boat load more than just edit files at the command line.

You are right about Vista "making us do some more things".

It's taken a lot of research to find out how to get Vista to let you
do what was relatively easy in XP.

It was nice learning how to turn off UAC.

I was half expecting Vista to pop up a message saying, "Do you need to
take a bathroom break before Vista updates the time for you?"

Take care,

Andy

 

On Sun, 12 Jul 2009 08:59:34 -0700 (PDT), WhiteTea77581 wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> On Jul 10, 6:50 pm, "Gene E. Bloch" <not...@other.invalid> wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
>> I got to vi right after the editor I described earlier in this thread. It
>> was *wonderful*, like not banging my head against the wall any more.
>>
>> Actually, I found vi very useful and easy to use. Not now, I'm very out of
>> practice, but a few of the commands were still at my fingertips the last
>> time I looked, two or three years ago.
>>
>> Edlin isn't so bad for what it is - namely, a crappy editor <!--colorc--><!--/colorc-->
>
> If your OS goes night-night and all you can do is boot to a command
> line,
> then you'll have a expensive paperweight for a while.
>
> Andy<!--colorc--><!--/colorc-->

I am trying without success to figure out how the above relates to what I
posted. Care to help me?

--
Gene E. Bloch letters0x40blochg0x2Ecom