public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]
Date: Thu, 18 Sep 2003 23:26:54 -0500	[thread overview]
Message-ID: <20030919042654.GS1804@dbz.icequake.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0309181238300.29182-100000@enm-bo-lt.localdomain>


Hi,

On Thu, Sep 18, 2003 at 12:52:41PM +0100, Bart Oldeman wrote:
> On Thu, 18 Sep 2003, Ryan Underwood wrote:
> 
> > On Tue, Sep 16, 2003 at 04:33:50AM -0500, Ryan Underwood wrote:
> > >
> > > While on the topic, is there a document that explains how to add a new
> > > configuration option?  I have modified, parser.y, config.c, global.conf,
> > > and lexer.l and having a little trouble getting the new variable to be
> > > "seen".  I grepped through the docs for "lexer" and "parser" but didn't
> > > see much useful right away.
> >
> > I take it from lack of response that nobody knows? :)
> >
> > Just kidding, but I really have some problems implementing a new
> > configuration option, so any hints would be helpful.
> 
> have a look at a small prepatch that does exactly that, eg. patch-1.1.5.5
> added a $_lfn_support option.

Here is the procedure I undertook, to hopefully shed some more light:

1. First I added a new variable to the config struct in
src/include/emu.h called delay_interval

2. in src/base/init/lexer.l.in:
delay_interval          RETURN(DELAY_INTERVAL);

3. in src/base/init/parser.y.in:
%token DELAY_INTERVAL

4. in src/base/init/parser.y.in also:
	| DELAY_INTERVAL expression
		{
		c_printf("Hello, this is delay_interval speaking\n");
		}

5. in global.conf, under checkuservar, I add $_delay_interval.
In the parser_version_3 scope, I add:
delay_interval $_delay_intervala

6. in dosemu.conf on my system, I add $_delay_interval = (1234)

7. I run the new dosemu.bin -D+C, and my c_printf is never displayed.

Any ideas?

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

  parent reply	other threads:[~2003-09-19  4:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16  3:29 1.0.2.1 and latest kernel? Stas Sergeev
2003-09-16  3:51 ` Ryan Underwood
2003-09-16  9:05   ` 1.0.2.1 and latest kernel?a [1.1.5.7 now] Ryan Underwood
2003-09-16  9:12     ` Bart Oldeman
2003-09-16  9:21       ` Ryan Underwood
2003-09-16  9:33       ` Ryan Underwood
2003-09-18  9:07         ` Ryan Underwood
2003-09-18 11:52           ` Bart Oldeman
2003-09-18 12:50             ` Ryan Underwood
2003-09-19  4:26             ` Ryan Underwood [this message]
2003-09-19  5:08               ` Ryan Underwood
2003-09-19  9:30               ` Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2003-09-18 19:22 Stas Sergeev
2003-09-18 23:42 ` Bart Oldeman
2003-09-19  5:30   ` Ryan Underwood
2003-09-19  2:05 ` Ryan Underwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030919042654.GS1804@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox