Please send me (privately) your preferred user name, and a temporary
password, and I'll register you.
We had to disable registration because of a ridiculously large number of
fake accounts that were spamming us. Unfortunately, trac does not seem
to support any sort of preventative measure.
R
Registration via website https://www.lyx.org/trac/wiki/register2 does not work.
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel
> I sent new login privately. P
It worked, thanks!
I'm going to report the bugs there so you got them thrice :)
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Wed, Mar 13, 2024 at 09:19:45PM -0300, Carlos Pita wrote:
> I've been trying to report a couple of bugs to your Trac (which I
> haven't used for ages) but to no avail. I've a password although it
> doesn't seem to be the right one, so I tried to reset my password many
> times but the email never
r). And
registration is disabled, so I'm out of luck.
Now, I've just read in you site that:
> This list [lyx-devel] is intended for the discussion of subjects relevant to
> the
> implementation, planning, hacking and improvements of LyX. This
> means that bug reports shoul
John McCabe-Dansted wrote:
> It does not introduce any filenames with ':' though :).
its in.
pavel
This fixes a bug where get_pid mistakes "gdb lyx" for the lyx process,
preventing it from working at all unless lyx is a symbolic link.
Additionally this patch reduces the size of the log, as it no longer
generates 3+ lines in the log for every key sent. It also adds more
sanity checking and variou
On Mon, Jan 4, 2010 at 6:49 PM, Vincent van Ravesteijn - TNW
wrote:
>>Specifically I reproduced the bug manually, and put
>>the backtrace in.
>
> Hmm. I'm wondering why you can reproduce it manually.
>
> Did you customize the converter settings ? If so, can you show us your
> "lyxrc.defaults" and
>Specifically I reproduced the bug manually, and put
>the backtrace in.
Hmm. I'm wondering why you can reproduce it manually.
Did you customize the converter settings ? If so, can you show us your
"lyxrc.defaults" and "preferences" file, such that we might reproduce the
problem. (Maybe you hav
Am 03.01.2010 00:35, schrieb Pavel Sanda:
This commit breaks SVN completely: SVN cleanup doesn't help and also no
completely new checkout.
ouch. can you try whether svn works now?
It works now, many thanks.
regards Uwe
On Sun, Jan 3, 2010 at 7:31 AM, Uwe Stöhr wrote:
> The reason is that you committed a file named "view:1" This is an invlaid
> filename on Windows and thus screws up SVN. Can anybody on Linux please
> rename the file so that has no "\", "/", ":", "|" "?", "*", "<", ">" and '"'
> in its name.
Sorr
Uwe Stöhr wrote:
> > i have commited the patch. hopefully without errs, but rather check it ;)
>
> This commit breaks SVN completely: SVN cleanup doesn't help and also no
> completely new checkout.
ouch. can you try whether svn works now?
pavel
> i have commited the patch. hopefully without errs, but rather check it ;)
This commit breaks SVN completely: SVN cleanup doesn't help and also no
completely new checkout.
The reason is that you committed a file named "view:1" This is an invlaid filename on Windows and
thus screws up SVN. Can
John McCabe-Dansted wrote:
> have changed Keytest now so that it keeps a log of the svn revision
> when it logs a crash so this won't be required. Patch is attached,
i have commited the patch. hopefully without errs, but rather check it ;)
pavel
On Thu, Dec 31, 2009 at 7:36 PM, John McCabe-Dansted wrote:
> Ah, I manually broke this :(
Specifically I reproduced the bug manually, and put the backtrace in.
I did this to make sure this was really from the same svn revision. I
have changed Keytest now so that it keeps a log of the svn revisio
On Thu, Dec 31, 2009 at 7:08 PM, Vincent van Ravesteijn - TNW <
v.f.vanraveste...@tudelft.nl> wrote:
> > An example of a bug entered using this button:
> >http://www.lyx.org/trac/ticket/6424
> >
>
> It appears that the backtrace shown there is not related to the bug. The
> backtrace is differ
> An example of a bug entered using this button:
>http://www.lyx.org/trac/ticket/6424
>
It appears that the backtrace shown there is not related to the bug. The
backtrace is different from the one I see when I follow the "Keytest
Report" link, it is not an assertion as the keyword indicates
The attached patch allows most of the fields in the trac bugreport to filled
in with one click from the keytest summary page. The hope is that this would
help ensure that the keytest bug-reports are consistent, complete and
accurate.
An example of a bug entered using this button:
http
On Tue, 7 Apr 2009, Guenter Milde wrote:
Are there still plans to try a bugzilla revival?
I think there is still a shortage of someone with the skill to install and
maintain a bugzilla installation, so I think this is still not likely to
happen.
I can't answer any of your other questions,
Dear Developers,
I would like to know the current state regarding the bug tracker
migration.
Is Trac open for new bug reports and updates?
Is Trac open for ordinary users?
Are there still plans to try a bugzilla revival?
What is the recommended way to report problems/wishes
* Trac
* user
Hi,
FYI: I just added two more bug reports to bugzilla.
AFAICS, we detect new bugs at a higher speed than we are able to fix
known bugs.
Presently, http://tinyurl.com/y7hdzc gives 524 bugs. About three weeks
ago, we only had 500 entries - whatever that means and whatever the
implications
Enrico Forestieri wrote:
On Fri, Dec 15, 2006 at 12:00:58PM +0100, Abdelrazak Younes wrote:
Enrico Forestieri wrote:
However, playing a bit with this issue I discovered some other oddities.
The cursor behaves strangely when a word is in a small caps font.
Moving the cursor over such a word it m
On Fri, Dec 15, 2006 at 12:00:58PM +0100, Abdelrazak Younes wrote:
> Enrico Forestieri wrote:
> >
> > However, playing a bit with this issue I discovered some other oddities.
> > The cursor behaves strangely when a word is in a small caps font.
> > Moving the cursor over such a word it may happen
Enrico Forestieri wrote:
However, playing a bit with this issue I discovered some other oddities.
The cursor behaves strangely when a word is in a small caps font.
Moving the cursor over such a word it may happen to be positioned right
in the middle of a character instead that on a side of it. Y
Enrico Forestieri schrieb:
However, playing a bit with this issue I discovered some other oddities.
The cursor behaves strangely when a word is in a small caps font.
Moving the cursor over such a word it may happen to be positioned right
in the middle of a character instead that on a side of it.
Bo Peng schrieb:
I sync'ed with the latest 1.5.0svn. I still can reproduce the bug. Just
open some doc, highlight the first word and invoke "ert-insert".
Is this under windows? VC or mingw? Scons or cmake?
Yes. VC. Scons.
(Joost's default recipe)
Michael
On Thu, Dec 07, 2006 at 06:49:31PM +0100, Michael Gerz wrote:
> Enrico Forestieri schrieb:
> >On Thu, Dec 07, 2006 at 01:17:44PM +0100, Michael Gerz wrote:
> >
> >>Added to Status.15x:
> >>
> >>+* Open some arbitrary doc; mark some text; invoke "ert-insert" => seg
> >>fault
> >>
> >
> >Canno
I sync'ed with the latest 1.5.0svn. I still can reproduce the bug. Just
open some doc, highlight the first word and invoke "ert-insert".
Is this under windows? VC or mingw? Scons or cmake?
Bo
Enrico Forestieri schrieb:
On Thu, Dec 07, 2006 at 01:17:44PM +0100, Michael Gerz wrote:
Added to Status.15x:
+* Open some arbitrary doc; mark some text; invoke "ert-insert" => seg fault
Cannot reproduce this one neither on Cygwin nor on Solaris.
I sync'ed with the latest 1.5.0svn.
> +* Open some arbitrary doc; mark some text; invoke "ert-insert" => seg fault
Cannot reproduce this one neither on Cygwin nor on Solaris.
I can not reproduce exactly this, but if I play with such things a
while, and then select some text, maybe with a button, lyx will crash.
I have seen this
On Thu, Dec 07, 2006 at 01:17:44PM +0100, Michael Gerz wrote:
> Added to Status.15x:
>
> +* Open some arbitrary doc; mark some text; invoke "ert-insert" => seg fault
Cannot reproduce this one neither on Cygwin nor on Solaris.
--
Enrico
Added to Status.15x:
+* Open some arbitrary doc; mark some text; invoke "ert-insert" => seg fault
+* Open de_Intro.lyx => The footnote text in the title section exceeds
the footnote frame
+* Open de_UserGuide.lyx; go to the end of the document; click into the
footnote (with the mouse -
+ t
any cvs commit to the frontend within
Michael> the past 12 months. If we do not want to support xforms in
Michael> the future, we should inform 1.4.0 users about it so that
Michael> they do not add new bug reports.
There has not been much work on the qt frontend in the last 12 month
e
so that they do not add new bug reports.
I think it would also make sense to go through the whole list of open
bugs and check whether they are still valid. There are some very old
entries. I probably cannot check all 315 entries by myself but if others
volunteer as well it should be doable wi
Michael Schmitt wrote:
> 1. New doc; choose "Section" layout; insert short title => Good bye!
http://bugzilla.lyx.org/show_bug.cgi?id=1890
> 2. New doc; Navigate>Next Note => Good bye!
http://bugzilla.lyx.org/show_bug.cgi?id=1891
> 3. New doc; enter "Hello"; move cursor after "e"; insert index
Michael Schmitt wrote:
> 1. New doc; choose "Section" layout; insert short title => Good bye!
Confirmed.
> 2. New doc; Navigate>Next Note => Good bye!
Confirmed (I had to hit it twice, though).
> 3. New doc; enter "Hello"; move cursor after "e"; insert index entry =>
> Cursor is placed after "l
On Wed, May 18, 2005 at 11:05:03PM +0200, Michael Schmitt wrote:
> 4. "Accept All Changes" and "Revert All Changes" should be atomic
> operations; otherwise "undo" is a real pain
This one's filed already
john
Hello,
some new (?) bug reports and comments:
1. New doc; choose "Section" layout; insert short title => Good bye!
2. New doc; Navigate>Next Note => Good bye!
3. New doc; enter "Hello"; move cursor after "e"; insert index entry =>
Cursor is placed afte
On Thu, Aug 02, 2001 at 04:37:34PM +0200, Andre Poenitz wrote:
> > this is perfectly acceptable for you to do this as a bug reporter. Any
> > bugs that last will hopefully end up on the tracker via me (that's /my/
> > job)
>
> I can see a problem with people like me who do not check the bug trac
> I also think that before we can release a "pre" we have to fix all open
> bugs!
See you next year then... ;-}
> I'm on the way to fix my share, but that is quite large and I would
> be really happy if someone could also have a look at reported bugs. IMO
> we are now in some sort of FREEZE wher
On Fri, Aug 03, 2001 at 10:03:44AM +0200, Jean-Marc Lasgouttes wrote:
> John> and major remaining issues, in a way a shared BUGS file is never
> John> going to manage ...
>
> I think the tracker is really needed. It would be better of course if
> we could intereact with it through e-mail, like t
On Fri, Aug 03, 2001 at 09:00:08AM +0200, Andre Poenitz wrote:
> > > What am I supposed to do if the bug is fixed?
> >
> > if I fail to notice you can tell me I suppose ?
>
> parse error?
>
> Aehm: what I mean: It is fine with me if you assign mathed bugs to me.
> The question is: Should I inf
On Thu, Aug 02, 2001 at 04:37:34PM +0200, Andre Poenitz wrote:
> > this is perfectly acceptable for you to do this as a bug reporter. Any
> > bugs that last will hopefully end up on the tracker via me (that's /my/
> > job)
>
> I can see a problem with people like me who do not check the bug trac
> this is perfectly acceptable for you to do this as a bug reporter. Any
> bugs that last will hopefully end up on the tracker via me (that's /my/
> job)
I can see a problem with people like me who do not check the bug tracking
thingy regularly. I certainly would have a look at some src/BUGS or
s
On Thu, Aug 02, 2001 at 04:24:32PM +0200, Michael Schmitt wrote:
> Some time ago, you convinced me to use SF but it was an unacceptable
> burden for me to cope with SF's WWW frontend during my regular work.
> (Reports have to be made quickly; I have another job I am paid for)
this is fine, Micha
> if mathed bugs appear, I can assign them to you. Then you should get an email
> (I think). Or I can tell lyx-devel ... is that good enough ?
What am I supposed to do if the bug is fixed?
Andre'
--
André Pönitz . [EMAIL PROTECTED]
Hello everybody,
as you know there is a bug tracker for LyX at SourceForge. However, as you
also might know the system requires some administration and it is not
appropriate for bugs occuring during the main development phase, since
they only live for a very short time.
Some time ago, you convin
Hi,
I will be on vacation for the next two weeks. Please don't wait for any
response in case one of my reports at SourceForce is fixed/needs
clarification.
Michael
PS: Two weeks without Email. Hard times...
--
==
Michael Schm
On Wed, 28 Feb 2001, Allan Rae wrote:
> > Michael, what's the exact problems with compiling sigc++ on sunos cc ?
>
> cc-5.0 will never work. cc-5.1 might work with horrible header macros.
Indeed, CC 5.0 is rather incomplete wrt. ANSI C++. CC 5.1 (aka Forte
6.0) is much better.
CC 5.1 and 5.2 a
On Tue, 27 Feb 2001, John Levon wrote:
>
> Michael, what's the exact problems with compiling sigc++ on sunos cc ?
cc-5.0 will never work. cc-5.1 might work with horrible header macros.
Sun's cc is crap. It can't handle partial specialization -- at least not
the way everyone else interprets th
Michael, what's the exact problems with compiling sigc++ on sunos cc ?
Sourceforge have a compile box nearly up and running, so I imagine the
sigc++ people can test this soon.
Is your bug listed at
http://sourceforge.net/tracker/?group_id=1970&atid=101970
?
thanks
john
--
"Please crack do
On Tue, 27 Feb 2001, Michael Schmitt wrote:
> Hello!
>
> I have flooded lyxbugs.sourceforge.net with another 14 bug reports. I hope you
> consider them useful even though some of them a rather imprecise and some bugs
> may only occur under certain unknown circumstances
Hello!
I have flooded lyxbugs.sourceforge.net with another 14 bug reports. I hope you
consider them useful even though some of them a rather imprecise and some bugs
may only occur under certain unknown circumstances. Any fixes are appreciated.
Michael
PS: I have noticed that somebody worked on
Michael Schmitt wrote:
> Ronny Buchmann wrote:
>
>
>> look at http://www.educat.hu-berlin.de/~voss/lyx/ (archived lyx tips)
>
>
> Wow, what a comprehensive list of tricks! If the LyX developers feel like LyX
> is feature complete, they should (first ask me ;-) and than) have a look at
> you
Ronny Buchmann wrote:
> look at http://www.educat.hu-berlin.de/~voss/lyx/ (archived lyx tips)
Wow, what a comprehensive list of tricks! If the LyX developers feel like LyX
is feature complete, they should (first ask me ;-) and than) have a look at
your page. Thank very much!
> > ***
Michael Schmitt wrote:
> Hello,
>
> when trying to export the LyX User Manual to PDF (pdflatex), I got 6 error
> messages concerning eps files. It seems like pdflatex does not accept
> postscript files. Does anybody have an idea how to handle that situation? (I
> once heard about a "metapost" fo
Dekel Tsur wrote:
> hyperref - We can't just add \usepackage[options]{hyperref} because we need
> to let the user select which options he wants to use, namely, we need to add
> a new tab in the document dialog.
I don't mind if you add another tab for 'hyperref'. But I cannot imagine that
any use
On Mon, Jan 22, 2001 at 02:33:08PM +0100, Michael Schmitt wrote:
> Ah, meanwhile I found out that the errors are listed in the document! But menu
> item "Navigate/Error" and CTRL-G are disabled!
This is weird. The Navigate->Error menu-item shoud alway be enabled!
> I noticed that Chapter 3.3.6.
Dekel Tsur wrote:
> > Please note that it is not possible to go to one of these errors in LyX - you
> > have to read the latex output!
>
> I don't have this problem.
> Can you send your latex log file ?
Ah, meanwhile I found out that the errors are listed in the document! But menu
item "Navigat
On Mon, Jan 22, 2001 at 10:55:21AM +0100, Michael Schmitt wrote:
> when trying to export the LyX User Manual to PDF (pdflatex), I got 6 error
> messages concerning eps files. It seems like pdflatex does not accept
> postscript files. Does anybody have an idea how to handle that situation? (I
> onc
Hello,
when trying to export the LyX User Manual to PDF (pdflatex), I got 6 error
messages concerning eps files. It seems like pdflatex does not accept
postscript files. Does anybody have an idea how to handle that situation? (I
once heard about a "metapost" format but I have no details).
Pleas
Hello,
here are two short comments on the latest lyx version:
when adding two bibtex bibliographies as separate insets, adding some
citations, changing the order of the bibliographies and manipulating the
citations again, lyx-1.1.5fix1 crashes. The error does not occur, if you
specify both bibli
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> played around with figures. They causes a lot of problems in
Michael> the past. One of my students was very unhappy about lyx
Michael> because of lot of figure-related crashed. But I will continue
Michael> force him to use ly
Hi,
played around with figures. They causes a lot of problems in the past.
One of my students was very unhappy about lyx because of lot of
figure-related crashed. But I will continue force him to use lyx :-)
Unfortunately, I did not manage to crash lyx so far but the following
list of bugs seems
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> Well, here are a few additional problems reported by Purify
Michael> when just browsing through some existing Lyx files (without
Michael> changing anything).
I took a quick look and found a potentially serious bug in figinse
Hello,
nothing else to do?
Well, here are a few additional problems reported by Purify when just
browsing through some existing Lyx files (without changing anything).
Michael
--
==
Michael Schmitt
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> today, I finally managed to run lyx-devel (1.1.4cvs) with
Michael> Purify, a run-time memory checker. So far I did not trap into
Michael> serious problems (such like segmentation faults).
Michael> Nevertheless, Purify reporte
Hello everybody,
today, I finally managed to run lyx-devel (1.1.4cvs) with Purify, a
run-time memory checker. So far I did not trap into serious problems
(such like segmentation faults). Nevertheless, Purify reported some
problems that should not occur normally.
A full list of warnings is attach
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> The problem here IIRC is that an open math panel is associated
Allan> with a particular math inset. That math inset is now hidden
Allan> because you changed buffers. I think that was why I made it
Allan> hide the math panel. To get aro
On Thu, 4 Nov 1999, Shaul Karl wrote:
> Package: lyx
> Version: 1.0.4-3
> Severity: wishlist
>
> 1) Changing the document causes any open math tools window to be closed. IMHO
>these window should be kept open, just like the table of contents window
> stays
>open in this circumstances.
Package: lyx
Version: 1.0.4-3
Severity: wishlist
1) Changing the document causes any open math tools window to be closed. IMHO
these window should be kept open, just like the table of contents window
stays
open in this circumstances.
2) Iconifying the main windows does not iconify any open
71 matches
Mail list logo
