Re: [Freedos-devel] problems with moving in a long history

Hi, > On Jun 5, 2024, at 7:46 AM, Bernd Böckmann via Freedos-devel > wrote: > > >> Am 04.06.2024 um 09:31 schrieb Wolf Bergenheim via Freedos-devel >> : >> >> I did some more digging... Found a wikipedia article discussing it [1] but >> maybe more interesting was a german text on 4dos tips

Re: [Freedos-devel] problems with moving in a long history

> Am 04.06.2024 um 09:31 schrieb Wolf Bergenheim via Freedos-devel > : > > I did some more digging... Found a wikipedia article discussing it [1] but > maybe more interesting was a german text on 4dos tips[2] apparently Windows > 95 only put the rest of the command line in CMDLINE. The 4dos

Re: [Freedos-devel] problems with moving in a long history

I did some more digging... Found a wikipedia article discussing it [1] but maybe more interesting was a german text on 4dos tips[2] apparently Windows 95 only put the rest of the command line in CMDLINE. And it makes sense that it was introduced because of long file name support. With LFN 127 chara

Re: [Freedos-devel] problems with moving in a long history

Hi, On Sun, Jun 2, 2024 at 7:33 AM perditionc--- via Freedos-devel wrote: > > DJGPP is where the cmdline env and extended command line processing is from I > think, that or 4DOS. > it's been a while, but it was based on and made to function like existing > implementations. I think it was a Wi

Re: [Freedos-devel] problems with moving in a long history

On Sun, Jun 2, 2024, 8:05 AM Bernd Böckmann via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > > but then I realized that since it doesn't know about it, it doesn't > actually get the full line. It does only see the first 127 characters, > > which is why you can get odd errors eve

Re: [Freedos-devel] problems with moving in a long history

> but then I realized that since it doesn't know about it, it doesn't actually > get the full line. It does only see the first 127 characters, > which is why you can get odd errors even though your line should be fine, > depending on where the break is... Nice analysis :) The behaviour of si

Re: [Freedos-devel] problems with moving in a long history

On Sun, Jun 2, 2024 at 5:13 AM Jerome Shidel via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > FreeCOM copies the first 126 bytes to the new PSP terminated by 0xd. Then > it creates an environment variable “CMDLINE” with the entire command line. > > Ah I see! Thanks! :D So I supp

Re: [Freedos-devel] problems with moving in a long history

On Jun 1, 2024, at 7:46 PM, Wolf Bergenheim via Freedos-devel wrote:On Sat, Jun 1, 2024 at 8:57 PM Bernd Böckmann via Freedos-devel wrote: On 15.05.2024 16:01, Wilhelm Spiegl via Freedos-devel wrote: > [...] > I hope that this behaviour is reproducable. Some

Re: [Freedos-devel] problems with moving in a long history

On Sat, Jun 1, 2024 at 8:57 PM Bernd Böckmann via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > On 15.05.2024 16:01, Wilhelm Spiegl via Freedos-devel wrote: > [...] > I hope that this behaviour is reproducable. > > Some details: cursor positioning algorithm is broken if scrolli

Re: [Freedos-devel] problems with moving in a long history

On 15.05.2024 16:01, Wilhelm Spiegl via Freedos-devel wrote: The main problem is, that if you type "arrow up" for "history" (repeating the previous command) and then "arrow left" (for moving the cursor into this long command) causes a break in the long option line at both versions. The cursor

[Freedos-devel] problems with moving in a long history

Hi, I have a problem with repeating overlong options, as they appear e.g. at the command "localcfg". This tool is made to create the local settings of country.sys Here is the problem: The command with all options is very long, e.g. for german file:   localcfg test.sys /country:49 /cp:858 /decim:,