Quoting Bert Wesarg <[email protected]>:

> On Mon, Nov 23, 2009 at 23:47, Tony Balinski <[email protected]> wrote:
> > Quoting Bert Wesarg <[email protected]>:
> >
> >> Hi,
> >>
> >> I think I have found at least one bug and one oddity:
> >>
> >> The -do command is only reset to "" in the !VMS case. Which would
> >> result that the -do macro is executed for all following files. Because
> >> VMS does wildcard expension by itself, I would also propose to add a
> >> warning, if a -do macro would be executed for file arguments which
> >> expands to more than one file.
> >>
> >> The second is an oddity that the -line argument is not reset after a
> >> file argument, That is, all following files after a -line argument
> >> will be opened with this line.
> >>
> >> As a general question: should we add more options to this reset-list?
> >> To get a finer control to the effect of these options to file
> >> arguments. It is also possible to add new options, which disable
> >> previous one, like -noread, -nocreate, -nolm, -noiconic?
> >>
> >> Bert
> >
> > Well spotted. Certainly the -line should only apply to the following
> file.
> > -iconic already has -noiconic (not sure whether it behaves as you
> suggest).
> > Then there's -wrap, -nowrap (same comment). -group could perhaps have a
> > -nogroup too, to stop grouping on following files. Otherwise the other
> options
> > listed by nedit -h are probably fine as they are. Some seem to apply to
> all
> > (-display, -import), others to the following files (-rows, -geometry).
> I'd
> > have to experiment to work out each one's behaviour. I also think we
> should
> > try to avoid other -no... options unless they really make sense.
> >
> > That's my quick reply anyway...
> Thanks. The -line options handling in nedit(nedit.c) and nc(server.c)
> are effected. -do only in nc. I think this is worth to put into the
> BETA-5-6 branch. The reset should be evaluated in a second step.
> Objections?

I'm happy with that.
T

-- 
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop

Reply via email to