On Wed, Sep 21, 2016 at 07:32:53PM +0100, Thomas Adam wrote:
> On Wed, Sep 21, 2016 at 09:11:51AM -0700, elliot s wrote:
> > > take another look at the document, since it tells you how functions could
> > > be specified.
> > I missed seeing the example, but it was as i thought.
> > A function is specified all on one line, which means adding \ on all
> > but last line,
> > which means having to make sure \ is on all but last line.
> > A source of copy/paste/delete errors while working on a function.
> No different to how things are now, so it's not anything worth mentioning,
> -- Thomas Adam
Is it worth considering moving away from line-based processing for
entities like functions?
Changing the example in the document to something like:
Function -n func_name
i:TestRc (NoMatch) Break,
Just a thought.