Re: [Freedos-user] DOG version 0.8.4b released

[Anton Shepelev via Freedos-user]

Rugxulo:

> I know PowerShell is default now (written in C#, also has
> a Linux port), but I never used it.

Yes, and it has a philosophy entirely alien to the way I see
the commant prompt: everyting is an object, instead of
everyting is a (text) file. I believe in a simple, concise,
lightweight, and dedicated language for the interpreter,
which C# is not.

> Naive question: what's wrong with Take Command, TCC/LE,
> etc.? (formerly 4NT)

I have not tried it.  Thanks for the pointer.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Rugxulo via Freedos-user]

Hi,

On Wed, Jun 26, 2024 at 9:45 AM Anton Shepelev via Freedos-user
 wrote:
>
> P.S.: As one who writes and maintains some complicated .bat-
>   files, I wish DOG were available for Windows, too.  I
>   am not into Powershell at all at all.

I know PowerShell is default now (written in C#, also has a Linux
port), but I never used it.

Naive question: what's wrong with Take Command, TCC/LE, etc.? (formerly 4NT)

* https://en.wikipedia.org/wiki/Take_Command_Console


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Anton Shepelev via Freedos-user]

Wolf Bergenheim to Anton Shepelev:

> > > Without parameters BP puts ASCII character 07h into
> > > stdout, causing a beep as long as the ANSI driver is
> > > loaded.
> >
> > [...] the reference to the ANSI driver makes no sense:
> > as long as what duration?
>
> From the Cambridge Dictionary
> 
>  :
>
> As long as or so long as also means 'provided that',
> 'providing that' or 'on condition that': You are allowed
> to go as long as you let us know when you arrive.  So long
> as is a little more informal: You can borrow the car so
> long as you don't drive too fast

Yes, of course -- this meaning hadn't occurred to me,
probably because `as long as' sounds really /weird/ in that
context, because implies a process in duration, rather than
a precondition.  This is a very fine nuance:

  


> Since you were confused, maybe others would also be
> confused, so I replaced it with "provided that".

I do not believe in simplifying your language because
someone might be confused.  I for one will be have even the
richest and most complex expressions /as long as/ as their
are good English (-: I would simply say `if /an/ ANSI driver
is loaded' (there may exist more than one ANSI driver,
right?)

> > I wonder whether the effect of a command should be
> > descirbed /before/ its syntax and parameters, so that
> > the reader should understand the context of what he is
> > reading.
>
> I thought about it, but ultimately the manual is for users
> who want to know how to use a command rather than know
> what it does, so I feel the syntax is more important.

My point is not about the order of importence, but rather
about the sequence of exposition.  A good document is
readable from to bottom, which means that all the context
required to understand a passage must needs have been
provided /above/ it, and declaring the purpose of a command
prior to describing its parameters helps establish the
context necessary for understanding.  For example, look at
man pages:


They all begin with a brief description of what a command of
function does, and only then do they provide the syntax and
delve into details.  This is very good, time-honoured
structure.

P.S.: As one who writes and maintains some complicated .bat-
  files, I wish DOG were available for Windows, too.  I
  am not into Powershell at all at all.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Wolf Bergenheim via Freedos-user]

On Sat, Jun 22, 2024 at 10:13 PM Anton Shepelev via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> There is no problem with a comma after `or'.  But another
> comma is actually missing -- the one after the parenthetical
> expression "if not all", so the second sentence should read:
>
>DOG works on most, if not all, flavors of DOS.
>
>
Agreed. Fixed.


> Some more errors in the online manual:

1. ... 8.
>
Fixed


> 9.  Without parameters BP puts ASCII character 07h into
> ...



A comma is missing after `parameters', and the reference
> to the ANSI driver makes no sense: as long as what
> duration?
>

>From the Cambridge Dictionary

:

As long as or so long as also means 'provided that', 'providing that' or
'on condition that':
You are allowed to go as long as you let us know when you arrive.
So long as is a little more informal: You can borrow the car so long as you
don't drive too fast

Since you were confused, maybe others would also be confused, so I replaced
it with "provided that".


> 10. DT dispolays the current date and time.
>

Fixed.


> I wonder whether the effect of a command should be descirbed
> /before/ its syntax and parameters, so that the reader
> should understand the context of what he is reading.
>

I thought about it, but ultimately the manual is for users who want to know
how to use a command rather than know what it does, so I feel the syntax is
more important.

Thanks for all the feedback! I really appreciate that you took time to read
through the whole manual! :D

--Wolf

-- 

  |\_
  | .\---.
 /   ,__/
/   /Wolf _
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Anton Shepelev via Freedos-user]

Roger:

> "DOG is a DOS SHELL, or command interpreter. DOG works on
> most, if not all flavors of DOG."
>
> So, this is pun at DOS for being a dog? ;-)  This is found
> on the Github page.
>
> Think you meant to state, "DOG is a DOS shell or command
> interpreter. DOG shell works on most, if not all flavors
> of DOS."

`shell', being a normal noun, should indeed not spelled in
uppercase, but the comma after `shell' need not have been
removed, if the author used it to denote a pause of
pondering before an explanation, cf. the punctuation in the
following titles:

   Frankenstein; or, The Modern Prometheus
   Moby-Dick; or, The Whale

There is no problem with a comma after `or'.  But another
comma is actually missing -- the one after the parenthetical
expression "if not all", so the second sentence should read:

   DOG works on most, if not all, flavors of DOS.

Some more errors in the online manual:

1.  When working with DOG in the prompt you typically use
the internal and external commends, and other programs.

Here, a comma is missing after `prompt', and `commands'
is written with a typo of `e' for `a'.

2.  These internal commands are built-in to the DOG binary

`built-in' is an adjective.  Say "are built into".

3.  It has the same effect as if you would have typed the
expansion.

Simplify: "as if you typed".

4.  In DOG directories are executable:

A comma is missing after `DOG'.

5.  HH alone simply lists the DOG commands.

Much better: "displays a list of all DOG commands"
(without the article).

6.  Name or path of EMPTY directory to remove.

An indefinite artcile is missing before `directory':
"of an empty directory".

7.  PATH - A list of directories used to search for
commands. Paths in the list are separated by the ;
character.

the list of paths where to search for commands.  The
paths are separated by the ; character.

8.  Exit the current DOG shell. Works only if the shell is
not a primary shell.

The grammar is good, but what is the effect in the
primary shell?  Probably no effect all, which should be
documented, e.g.:

Exit the current DOG shell, unless it is the primary
shell, in which case the command has no effect (or shows
an error?).

9.  Without parameters BP puts ASCII character 07h into
stdout, causing a beep as long as the ANSI driver is
loaded.

A comma is missing after `parameters', and the reference
to the ANSI driver makes no sense: as long as what
duration?

10. DT dispolays the current date and time.

Typo in `dispolays'.

I wonder whether the effect of a command should be descirbed
/before/ its syntax and parameters, so that the reader
should understand the context of what he is reading.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Wolf Bergenheim via Freedos-user]

Thanks, please do! :) I should have also added that to email. Next time...

-- 

  |\_
  | .\---.
 /   ,__/
/   /Wolf _



On Sat, Jun 22, 2024 at 12:47 PM Jim Hall via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> >>"DOG is a DOS SHELL, or command interpreter. DOG works on most, if not
> all flavors of DOS."
>
> I should add that to the news item I posted to the website last night. I
> remembered DOG was a shell, but others will not know.
>
>
>
> On Sat, Jun 22, 2024, 3:18 AM Wolf Bergenheim via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
>
>> On Sat, Jun 22, 2024 at 9:38 AM Mart Zirnask via Freedos-user <
>> freedos-user@lists.sourceforge.net> wrote:
>>
>>> Thanks for putting the manual online. I was not aware of DOG, but got
>>> curious already when you presented an earlier version update in this
>>> list some time ago.
>>>
>>
>> Great to hear! The old DOG website had actually been taken down at some
>> point when I wasn't looking.
>>
>>
>>>
>>> I like how all the commands consist of only two letters. Might be a
>>> personal preference (of my particular brain :), but somehow this works
>>> really well as a mnemonic.
>>>
>>
>> It (obviously) works for me too, somehow. I find that I tend to make 2
>> letter aliases of commands I use at work too. :)
>>
>>
>>>
>>> Maybe you could also share examples of some lenghtier, more complex
>>> batch files (or, as you call them, DOGFILES :).
>>>
>>>
>> Good idea! I think I could demonstrate how to build a menu system using
>> DOGfiles. 🤔 I've made a note, so it's going to happen.
>> Thanks for your feedback!
>>
>> --Wolf
>>
>> --
>>
>>   |\_
>>   | .\---.
>>  /   ,__/
>> /   /Wolf _
>>
>>
>>
>> Best,
>>> Mart
>>>
>>> On Sat, 22 Jun 2024 at 07:40, Roger via Freedos-user
>>>  wrote:
>>> >
>>> > "DOG is a DOS SHELL, or command interpreter. DOG works on most, if not
>>> all flavors of DOG."
>>> >
>>> > So, this is pun at DOS for being a dog? ;-)  This is found on the
>>> Github page.
>>> >
>>> > Think you meant to state, "DOG is a DOS shell or command interpreter.
>>> DOG shell works on most, if not all flavors of DOS."
>>> >
>>> > Added some minor grammar, or reading flow improvements, I think.
>>> >
>>> > On Fri, Jun 21, 2024 at 8:07 PM Wolf Bergenheim via Freedos-user <
>>> freedos-user@lists.sourceforge.net> wrote:
>>> >>
>>> >> Hi all!
>>> >>
>>> >> After 22 years of being dormant I recently re-discovered the joy of
>>> DOS and my old DOG project.
>>> >>
>>> >> Today I'm proud to release version 0.8.4b together with a migration
>>> to github and a brand new website.
>>> >>
>>> >> You can find the new DOG Operating Guide at https://dog.zumppe.net/
>>> and the github project is at https://github.com/susi/dog
>>> >>
>>> >> Please give it a spin, if you're curious, and if you find bugs or
>>> have feature requests, please report them in GitHub:
>>> https://github.com/susi/dog/issues
>>> >>
>>> >> ^..^
>>> >>
>>> >> Fixes/changes:
>>> >> ==
>>> >>
>>> >> DOG:
>>> >> - Fixed init + mkudata (for env and alias blocks).
>>> >> - Restored the old DOG prompt as the default when no PROMPT variable
>>> is set.
>>> >> - Now using Borland C++ 3.1 to build, and Make instead of the batch
>>> files
>>> >>   in previous versions.
>>> >> - HH utilizes HELP to display more thorough help texts, through the
>>> alias HHH.
>>> >>   The example DOG.DOG file sets up the alias:
>>> >>   al hhh %DOGDIR%\bin\help.com
>>> >> - Updated the IF syntax to be more versatile and to be similar with
>>> DO.
>>> >> - Implemented 44 and DO and IN and TI.
>>> >> - Fixed the Control-C implementation. Now it asks the user if they
>>> want to
>>> >>   abort the program.
>>> >> - Implemented a proper Critical Error handler.
>>> >> - Fixed environment initialization and management.
>>> >> - Default dog.dog is used to set up the basic environment, edit this
>>> to suit your needs.
>>> >>
>>> >> External commands:
>>> >> - CP: now takes more options: -i (interactive), -f (force)
>>> >> - VR: Fixed FreeDOS detection + print FD kernel string. Also added
>>> DOSbox detection.
>>> >> - LS: -w option to display a wide listing with no details -z to show
>>> human readable sizes.
>>> >> - RT: Is now built from the rm.c file in addition to RM.
>>> >>
>>> >> Utilities:
>>> >> - HELP - Expanded help to fully document all commands and DOG itself.
>>> The manual.txt is
>>> >> built with HELP.
>>> >> - GENERR - is a silly utility which returns the error code given as
>>> arg 1. Used in
>>> >>   testbat.dog to have predictable errorlevels.
>>> >> - TINT24 - test utility for testing the critical error handler.
>>> >>
>>> >> --Wolf
>>> >>
>>> >> --
>>> >>
>>> >>   |\_
>>> >>   | .\---.
>>> >>  /   ,__/
>>> >> /   /Wolf _
>>> >>
>>> >> ___
>>> >> Freedos-user mailing list
>>> >> Freedos-user@lists.sourceforge.net
>>> >> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>> >
>>> > ___
>>> > Fr

Re: [Freedos-user] DOG version 0.8.4b released

[Jim Hall via Freedos-user]

>>"DOG is a DOS SHELL, or command interpreter. DOG works on most, if not
all flavors of DOS."

I should add that to the news item I posted to the website last night. I
remembered DOG was a shell, but others will not know.



On Sat, Jun 22, 2024, 3:18 AM Wolf Bergenheim via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> On Sat, Jun 22, 2024 at 9:38 AM Mart Zirnask via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
>
>> Thanks for putting the manual online. I was not aware of DOG, but got
>> curious already when you presented an earlier version update in this
>> list some time ago.
>>
>
> Great to hear! The old DOG website had actually been taken down at some
> point when I wasn't looking.
>
>
>>
>> I like how all the commands consist of only two letters. Might be a
>> personal preference (of my particular brain :), but somehow this works
>> really well as a mnemonic.
>>
>
> It (obviously) works for me too, somehow. I find that I tend to make 2
> letter aliases of commands I use at work too. :)
>
>
>>
>> Maybe you could also share examples of some lenghtier, more complex
>> batch files (or, as you call them, DOGFILES :).
>>
>>
> Good idea! I think I could demonstrate how to build a menu system using
> DOGfiles. 🤔 I've made a note, so it's going to happen.
> Thanks for your feedback!
>
> --Wolf
>
> --
>
>   |\_
>   | .\---.
>  /   ,__/
> /   /Wolf _
>
>
>
> Best,
>> Mart
>>
>> On Sat, 22 Jun 2024 at 07:40, Roger via Freedos-user
>>  wrote:
>> >
>> > "DOG is a DOS SHELL, or command interpreter. DOG works on most, if not
>> all flavors of DOG."
>> >
>> > So, this is pun at DOS for being a dog? ;-)  This is found on the
>> Github page.
>> >
>> > Think you meant to state, "DOG is a DOS shell or command interpreter.
>> DOG shell works on most, if not all flavors of DOS."
>> >
>> > Added some minor grammar, or reading flow improvements, I think.
>> >
>> > On Fri, Jun 21, 2024 at 8:07 PM Wolf Bergenheim via Freedos-user <
>> freedos-user@lists.sourceforge.net> wrote:
>> >>
>> >> Hi all!
>> >>
>> >> After 22 years of being dormant I recently re-discovered the joy of
>> DOS and my old DOG project.
>> >>
>> >> Today I'm proud to release version 0.8.4b together with a migration to
>> github and a brand new website.
>> >>
>> >> You can find the new DOG Operating Guide at https://dog.zumppe.net/
>> and the github project is at https://github.com/susi/dog
>> >>
>> >> Please give it a spin, if you're curious, and if you find bugs or have
>> feature requests, please report them in GitHub:
>> https://github.com/susi/dog/issues
>> >>
>> >> ^..^
>> >>
>> >> Fixes/changes:
>> >> ==
>> >>
>> >> DOG:
>> >> - Fixed init + mkudata (for env and alias blocks).
>> >> - Restored the old DOG prompt as the default when no PROMPT variable
>> is set.
>> >> - Now using Borland C++ 3.1 to build, and Make instead of the batch
>> files
>> >>   in previous versions.
>> >> - HH utilizes HELP to display more thorough help texts, through the
>> alias HHH.
>> >>   The example DOG.DOG file sets up the alias:
>> >>   al hhh %DOGDIR%\bin\help.com
>> >> - Updated the IF syntax to be more versatile and to be similar with DO.
>> >> - Implemented 44 and DO and IN and TI.
>> >> - Fixed the Control-C implementation. Now it asks the user if they
>> want to
>> >>   abort the program.
>> >> - Implemented a proper Critical Error handler.
>> >> - Fixed environment initialization and management.
>> >> - Default dog.dog is used to set up the basic environment, edit this
>> to suit your needs.
>> >>
>> >> External commands:
>> >> - CP: now takes more options: -i (interactive), -f (force)
>> >> - VR: Fixed FreeDOS detection + print FD kernel string. Also added
>> DOSbox detection.
>> >> - LS: -w option to display a wide listing with no details -z to show
>> human readable sizes.
>> >> - RT: Is now built from the rm.c file in addition to RM.
>> >>
>> >> Utilities:
>> >> - HELP - Expanded help to fully document all commands and DOG itself.
>> The manual.txt is
>> >> built with HELP.
>> >> - GENERR - is a silly utility which returns the error code given as
>> arg 1. Used in
>> >>   testbat.dog to have predictable errorlevels.
>> >> - TINT24 - test utility for testing the critical error handler.
>> >>
>> >> --Wolf
>> >>
>> >> --
>> >>
>> >>   |\_
>> >>   | .\---.
>> >>  /   ,__/
>> >> /   /Wolf _
>> >>
>> >> ___
>> >> Freedos-user mailing list
>> >> Freedos-user@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> >
>> > ___
>> > Freedos-user mailing list
>> > Freedos-user@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> ___
> Freedos-user maili

Re: [Freedos-user] DOG version 0.8.4b released

[Wolf Bergenheim via Freedos-user]

On Sat, Jun 22, 2024 at 9:38 AM Mart Zirnask via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Thanks for putting the manual online. I was not aware of DOG, but got
> curious already when you presented an earlier version update in this
> list some time ago.
>

Great to hear! The old DOG website had actually been taken down at some
point when I wasn't looking.


>
> I like how all the commands consist of only two letters. Might be a
> personal preference (of my particular brain :), but somehow this works
> really well as a mnemonic.
>

It (obviously) works for me too, somehow. I find that I tend to make 2
letter aliases of commands I use at work too. :)


>
> Maybe you could also share examples of some lenghtier, more complex
> batch files (or, as you call them, DOGFILES :).
>
>
Good idea! I think I could demonstrate how to build a menu system using
DOGfiles. 🤔 I've made a note, so it's going to happen.
Thanks for your feedback!

--Wolf

-- 

  |\_
  | .\---.
 /   ,__/
/   /Wolf _



Best,
> Mart
>
> On Sat, 22 Jun 2024 at 07:40, Roger via Freedos-user
>  wrote:
> >
> > "DOG is a DOS SHELL, or command interpreter. DOG works on most, if not
> all flavors of DOG."
> >
> > So, this is pun at DOS for being a dog? ;-)  This is found on the Github
> page.
> >
> > Think you meant to state, "DOG is a DOS shell or command interpreter.
> DOG shell works on most, if not all flavors of DOS."
> >
> > Added some minor grammar, or reading flow improvements, I think.
> >
> > On Fri, Jun 21, 2024 at 8:07 PM Wolf Bergenheim via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
> >>
> >> Hi all!
> >>
> >> After 22 years of being dormant I recently re-discovered the joy of DOS
> and my old DOG project.
> >>
> >> Today I'm proud to release version 0.8.4b together with a migration to
> github and a brand new website.
> >>
> >> You can find the new DOG Operating Guide at https://dog.zumppe.net/
> and the github project is at https://github.com/susi/dog
> >>
> >> Please give it a spin, if you're curious, and if you find bugs or have
> feature requests, please report them in GitHub:
> https://github.com/susi/dog/issues
> >>
> >> ^..^
> >>
> >> Fixes/changes:
> >> ==
> >>
> >> DOG:
> >> - Fixed init + mkudata (for env and alias blocks).
> >> - Restored the old DOG prompt as the default when no PROMPT variable is
> set.
> >> - Now using Borland C++ 3.1 to build, and Make instead of the batch
> files
> >>   in previous versions.
> >> - HH utilizes HELP to display more thorough help texts, through the
> alias HHH.
> >>   The example DOG.DOG file sets up the alias:
> >>   al hhh %DOGDIR%\bin\help.com
> >> - Updated the IF syntax to be more versatile and to be similar with DO.
> >> - Implemented 44 and DO and IN and TI.
> >> - Fixed the Control-C implementation. Now it asks the user if they want
> to
> >>   abort the program.
> >> - Implemented a proper Critical Error handler.
> >> - Fixed environment initialization and management.
> >> - Default dog.dog is used to set up the basic environment, edit this to
> suit your needs.
> >>
> >> External commands:
> >> - CP: now takes more options: -i (interactive), -f (force)
> >> - VR: Fixed FreeDOS detection + print FD kernel string. Also added
> DOSbox detection.
> >> - LS: -w option to display a wide listing with no details -z to show
> human readable sizes.
> >> - RT: Is now built from the rm.c file in addition to RM.
> >>
> >> Utilities:
> >> - HELP - Expanded help to fully document all commands and DOG itself.
> The manual.txt is
> >> built with HELP.
> >> - GENERR - is a silly utility which returns the error code given as arg
> 1. Used in
> >>   testbat.dog to have predictable errorlevels.
> >> - TINT24 - test utility for testing the critical error handler.
> >>
> >> --Wolf
> >>
> >> --
> >>
> >>   |\_
> >>   | .\---.
> >>  /   ,__/
> >> /   /Wolf _
> >>
> >> ___
> >> Freedos-user mailing list
> >> Freedos-user@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/freedos-user
> >
> > ___
> > Freedos-user mailing list
> > Freedos-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Wolf Bergenheim via Freedos-user]

On Sat, Jun 22, 2024 at 6:39 AM Roger via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> "DOG is a DOS SHELL, or command interpreter. DOG works on most, if not all
> flavors of DOG."
>
> So, this is pun at DOS for being a dog? ;-)  This is found on the Github
> page.
>
> Think you meant to state, "DOG is a DOS shell or command interpreter. DOG
> shell works on most, if not all flavors of DOS."
>
> Added some minor grammar, or reading flow improvements, I think.
>
>
Thanks! I completely didn't see that! I think it's fixed now :)

--Wolf

-- 

  |\_
  | .\---.
 /   ,__/
/   /Wolf _




> On Fri, Jun 21, 2024 at 8:07 PM Wolf Bergenheim via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
>
>> Hi all!
>>
>> After 22 years of being dormant I recently re-discovered the joy of DOS
>> and my old DOG project.
>>
>> Today I'm proud to release version 0.8.4b together with a migration to
>> github and a brand new website.
>>
>> You can find the new DOG Operating Guide at https://dog.zumppe.net/ and
>> the github project is at https://github.com/susi/dog
>>
>> Please give it a spin, if you're curious, and if you find bugs or have
>> feature requests, please report them in GitHub:
>> https://github.com/susi/dog/issues
>>
>> ^..^
>>
>> Fixes/changes:
>> ==
>>
>> DOG:
>> - Fixed init + mkudata (for env and alias blocks).
>> - Restored the old DOG prompt as the default when no PROMPT variable is
>> set.
>> - Now using Borland C++ 3.1 to build, and Make instead of the batch files
>>   in previous versions.
>> - HH utilizes HELP to display more thorough help texts, through the alias
>> HHH.
>>   The example DOG.DOG file sets up the alias:
>>   al hhh %DOGDIR%\bin\help.com
>> - Updated the IF syntax to be more versatile and to be similar with DO.
>> - Implemented 44 and DO and IN and TI.
>> - Fixed the Control-C implementation. Now it asks the user if they want to
>>   abort the program.
>> - Implemented a proper Critical Error handler.
>> - Fixed environment initialization and management.
>> - Default dog.dog is used to set up the basic environment, edit this to
>> suit your needs.
>>
>> External commands:
>> - CP: now takes more options: -i (interactive), -f (force)
>> - VR: Fixed FreeDOS detection + print FD kernel string. Also added DOSbox
>> detection.
>> - LS: -w option to display a wide listing with no details -z to show
>> human readable sizes.
>> - RT: Is now built from the rm.c file in addition to RM.
>>
>> Utilities:
>> - HELP - Expanded help to fully document all commands and DOG itself. The
>> manual.txt is
>> built with HELP.
>> - GENERR - is a silly utility which returns the error code given as arg
>> 1. Used in
>>   testbat.dog to have predictable errorlevels.
>> - TINT24 - test utility for testing the critical error handler.
>>
>> --Wolf
>>
>> --
>>
>>   |\_
>>   | .\---.
>>  /   ,__/
>> /   /Wolf _
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Mart Zirnask via Freedos-user]

Thanks for putting the manual online. I was not aware of DOG, but got
curious already when you presented an earlier version update in this
list some time ago.

I like how all the commands consist of only two letters. Might be a
personal preference (of my particular brain :), but somehow this works
really well as a mnemonic.

Maybe you could also share examples of some lenghtier, more complex
batch files (or, as you call them, DOGFILES :).

Best,
Mart

On Sat, 22 Jun 2024 at 07:40, Roger via Freedos-user
 wrote:
>
> "DOG is a DOS SHELL, or command interpreter. DOG works on most, if not all 
> flavors of DOG."
>
> So, this is pun at DOS for being a dog? ;-)  This is found on the Github page.
>
> Think you meant to state, "DOG is a DOS shell or command interpreter. DOG 
> shell works on most, if not all flavors of DOS."
>
> Added some minor grammar, or reading flow improvements, I think.
>
> On Fri, Jun 21, 2024 at 8:07 PM Wolf Bergenheim via Freedos-user 
>  wrote:
>>
>> Hi all!
>>
>> After 22 years of being dormant I recently re-discovered the joy of DOS and 
>> my old DOG project.
>>
>> Today I'm proud to release version 0.8.4b together with a migration to 
>> github and a brand new website.
>>
>> You can find the new DOG Operating Guide at https://dog.zumppe.net/ and the 
>> github project is at https://github.com/susi/dog
>>
>> Please give it a spin, if you're curious, and if you find bugs or have 
>> feature requests, please report them in GitHub: 
>> https://github.com/susi/dog/issues
>>
>> ^..^
>>
>> Fixes/changes:
>> ==
>>
>> DOG:
>> - Fixed init + mkudata (for env and alias blocks).
>> - Restored the old DOG prompt as the default when no PROMPT variable is set.
>> - Now using Borland C++ 3.1 to build, and Make instead of the batch files
>>   in previous versions.
>> - HH utilizes HELP to display more thorough help texts, through the alias 
>> HHH.
>>   The example DOG.DOG file sets up the alias:
>>   al hhh %DOGDIR%\bin\help.com
>> - Updated the IF syntax to be more versatile and to be similar with DO.
>> - Implemented 44 and DO and IN and TI.
>> - Fixed the Control-C implementation. Now it asks the user if they want to
>>   abort the program.
>> - Implemented a proper Critical Error handler.
>> - Fixed environment initialization and management.
>> - Default dog.dog is used to set up the basic environment, edit this to suit 
>> your needs.
>>
>> External commands:
>> - CP: now takes more options: -i (interactive), -f (force)
>> - VR: Fixed FreeDOS detection + print FD kernel string. Also added DOSbox 
>> detection.
>> - LS: -w option to display a wide listing with no details -z to show human 
>> readable sizes.
>> - RT: Is now built from the rm.c file in addition to RM.
>>
>> Utilities:
>> - HELP - Expanded help to fully document all commands and DOG itself. The 
>> manual.txt is
>> built with HELP.
>> - GENERR - is a silly utility which returns the error code given as arg 1. 
>> Used in
>>   testbat.dog to have predictable errorlevels.
>> - TINT24 - test utility for testing the critical error handler.
>>
>> --Wolf
>>
>> --
>>
>>   |\_
>>   | .\---.
>>  /   ,__/
>> /   /Wolf _
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOG version 0.8.4b released

[Roger via Freedos-user]

"DOG is a DOS SHELL, or command interpreter. DOG works on most, if not all
flavors of DOG."

So, this is pun at DOS for being a dog? ;-)  This is found on the Github
page.

Think you meant to state, "DOG is a DOS shell or command interpreter. DOG
shell works on most, if not all flavors of DOS."

Added some minor grammar, or reading flow improvements, I think.

On Fri, Jun 21, 2024 at 8:07 PM Wolf Bergenheim via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hi all!
>
> After 22 years of being dormant I recently re-discovered the joy of DOS
> and my old DOG project.
>
> Today I'm proud to release version 0.8.4b together with a migration to
> github and a brand new website.
>
> You can find the new DOG Operating Guide at https://dog.zumppe.net/ and
> the github project is at https://github.com/susi/dog
>
> Please give it a spin, if you're curious, and if you find bugs or have
> feature requests, please report them in GitHub:
> https://github.com/susi/dog/issues
>
> ^..^
>
> Fixes/changes:
> ==
>
> DOG:
> - Fixed init + mkudata (for env and alias blocks).
> - Restored the old DOG prompt as the default when no PROMPT variable is
> set.
> - Now using Borland C++ 3.1 to build, and Make instead of the batch files
>   in previous versions.
> - HH utilizes HELP to display more thorough help texts, through the alias
> HHH.
>   The example DOG.DOG file sets up the alias:
>   al hhh %DOGDIR%\bin\help.com
> - Updated the IF syntax to be more versatile and to be similar with DO.
> - Implemented 44 and DO and IN and TI.
> - Fixed the Control-C implementation. Now it asks the user if they want to
>   abort the program.
> - Implemented a proper Critical Error handler.
> - Fixed environment initialization and management.
> - Default dog.dog is used to set up the basic environment, edit this to
> suit your needs.
>
> External commands:
> - CP: now takes more options: -i (interactive), -f (force)
> - VR: Fixed FreeDOS detection + print FD kernel string. Also added DOSbox
> detection.
> - LS: -w option to display a wide listing with no details -z to show human
> readable sizes.
> - RT: Is now built from the rm.c file in addition to RM.
>
> Utilities:
> - HELP - Expanded help to fully document all commands and DOG itself. The
> manual.txt is
> built with HELP.
> - GENERR - is a silly utility which returns the error code given as arg 1.
> Used in
>   testbat.dog to have predictable errorlevels.
> - TINT24 - test utility for testing the critical error handler.
>
> --Wolf
>
> --
>
>   |\_
>   | .\---.
>  /   ,__/
> /   /Wolf _
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] DOG version 0.8.4b released

[Wolf Bergenheim via Freedos-user]

Hi all!

After 22 years of being dormant I recently re-discovered the joy of DOS and
my old DOG project.

Today I'm proud to release version 0.8.4b together with a migration to
github and a brand new website.

You can find the new DOG Operating Guide at https://dog.zumppe.net/ and the
github project is at https://github.com/susi/dog

Please give it a spin, if you're curious, and if you find bugs or have
feature requests, please report them in GitHub:
https://github.com/susi/dog/issues

^..^

Fixes/changes:
==

DOG:
- Fixed init + mkudata (for env and alias blocks).
- Restored the old DOG prompt as the default when no PROMPT variable is set.
- Now using Borland C++ 3.1 to build, and Make instead of the batch files
  in previous versions.
- HH utilizes HELP to display more thorough help texts, through the alias
HHH.
  The example DOG.DOG file sets up the alias:
  al hhh %DOGDIR%\bin\help.com
- Updated the IF syntax to be more versatile and to be similar with DO.
- Implemented 44 and DO and IN and TI.
- Fixed the Control-C implementation. Now it asks the user if they want to
  abort the program.
- Implemented a proper Critical Error handler.
- Fixed environment initialization and management.
- Default dog.dog is used to set up the basic environment, edit this to
suit your needs.

External commands:
- CP: now takes more options: -i (interactive), -f (force)
- VR: Fixed FreeDOS detection + print FD kernel string. Also added DOSbox
detection.
- LS: -w option to display a wide listing with no details -z to show human
readable sizes.
- RT: Is now built from the rm.c file in addition to RM.

Utilities:
- HELP - Expanded help to fully document all commands and DOG itself. The
manual.txt is
built with HELP.
- GENERR - is a silly utility which returns the error code given as arg 1.
Used in
  testbat.dog to have predictable errorlevels.
- TINT24 - test utility for testing the critical error handler.

--Wolf

-- 

  |\_
  | .\---.
 /   ,__/
/   /Wolf _
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user