Skip to Content.
Sympa Menu

texmacs-users - Re: [TeXmacs] Reporting bugs in TeXmacs [was: multiline input]

Subject: mailing-list for TeXmacs Users

List archive

Re: [TeXmacs] Reporting bugs in TeXmacs [was: multiline input]


Chronological Thread 
  • From: Lionel Elie Mamane <address@hidden>
  • To: Joris van der Hoeven <address@hidden>
  • Cc: address@hidden
  • Subject: Re: [TeXmacs] Reporting bugs in TeXmacs [was: multiline input]
  • Date: Sun, 6 Aug 2006 19:27:54 +0200

On Sun, Aug 06, 2006 at 11:33:28AM +0200, Joris van der Hoeven wrote:
> On Sun, Aug 06, 2006 at 06:49:19AM +0200, Lionel Elie Mamane wrote:

>> I was just wondering, what is the best way to report bugs?
>> Use the bug tracker linked from
>> http://www.texmacs.org/tmweb/contact/bugs.en.html or post to this
>> mailing list?

> It depends whether the bug is severe.

> I corrected the multi-line bug, because Kasper just contributed a
> new plug-in and apparently wants to use a bugged feature. If a given
> bug is a real blocking factor for developments around TeXmacs, then
> you can also send a mail to the mailing list. In that case, it is
> good for us to be able to look at actual code, in order to better
> understand what you want to do.

I see... So when a bug block (part of) the development of my TeXmacs
plug-in
(http://www.activemath.org/~paul/MathUI06/proceedings/CoqTeXMacs.html),
I should mention that instead of just reporting the bug "nude". Will
do so in the future.

So, for now:

#16786 does not block development, but makes some documents using my
plug-in look a bit ugly.

#16086: I can work around it, by taking care of always writing the
whole contents of the scheme block before opening a new
block, but this makes the other side (the process that talks
to TeXmacs) more complex.

--
Lionel



Archive powered by MHonArc 2.6.19.

Top of Page