Re: Is it OK to use 'compile' and 'run' for hypertext documents?

From: Jay <>
Date: Wed, 5 May 2010 21:26:10 -0700 (PDT)

One thing I had fixed(?) in my 2.0 version of Textadept, was that the
compile function doesn't save the buffer before doing its magic (which
has caused me confusion in the past)

function compile()
  if not buffer.filename then return end
  -- FIX --
  -- END --
  local action = compile_command[buffer.filename:match('[^.]+$')]
  if action then execute(type(action) == 'function' and action() or
action) end

It would be nice if this could get pushed back into the trunk (unless
there are objections of course!)

On Apr 11, 1:39 am, mitchell <> wrote:
> Hi,
> > While talking about it, would it be possible to read the line-comment
> > string from the definition in the respective lexer and have this used
> > for the ctrl-q commenting function? So each language with a line-
> > comment could be easily commented this way?
> Not all lexers have a comment string. For example forth has lpeg.S('|\
> \'), Io has lpeg.P('#') + '//', etc. These patterns cannot be easily
> interpreted.
> Instead I have gone the language-specific module route like with run
> commands. This is in latest hg (r560). Supplemental comments can be
> found here:
> Note the incompatibility with 2.2 beta. Available only from hg. Thanks
> to Brian Schott for supplying the comment table.
> Mitchell
> > Robert

You received this message because you are subscribed to the Google Groups "textadept" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at
Received on Thu 06 May 2010 - 00:26:10 EDT

This archive was generated by hypermail 2.2.0 : Thu 08 Mar 2012 - 11:42:30 EST