3 // - are probably fixed, the reporter is asked to verify this
4 and report success or failure
6 ?? - are not reproducable, the reporter is asked to verify this
7 and report success or failure
9 :: - are questions or comments to the reporter, containing question
10 on how to reproduce the bug exactly or things like that
12 !! - mark "not a bug, a feature" replies, usually with a request for
15 Unmarked items are known unfixed but probably unverified bugs.
17 ----------------------------------------------------------------------
19 General hints for bug reports:
21 - keep the items small
23 - do not provide excessive information on how to reproduce the bug
26 - if a bug is partly fixed, report it as "fixed" and a new bug item
27 that contains the unfixed part only
29 - check this list regularly, comment on the marked items.
31 - plain ASCII text please, not much more than 70 chars per column
33 ----------------------------------------------------------------------
35 "R. Lahaye" <lahaye@users.sourceforge.net>
36 - Mathematical \frac with subscripts, for example:
37 \begin_inset Formula $\frac{\alpha _{1} }{\beta _{2} }$
45 // - Ctrl+enter doesn't work
47 // - When creating a matrix/align/eqnarray all columns are centered.
52 ?? - When changing the macro definition, all instances are not updated.
54 :: I cannot reproduce this.
56 ?? - If I have macros \newcommand{\foo}[1]{[#1]} and
57 ?? \newcommand{\foox}{\foo{x}} then when an instance of \foox is drawn on
58 ?? screen, there are two black frames. While this is "correct", it is
61 :: This is partially fixed?
63 - LyX crashes when you define a recursive macro
67 - If I have x_{1}^{2}, I put the cursor before the 2, and press backspace,
68 the result is 'x2'. The correct result should be 'x_{1}2'
70 - If I mark some text and then press ^, then the marked text is deleted.
71 The correct behavior is to put the marked text in the superscript.
73 - Pressing <down> when cursor is in subscript will move the cursor up
74 (to the base of the subscript) instead of exiting the inset.
75 The same problem happen in fractions
77 !! If you type something there you will see that the corsor has left the
78 !! inset. That's mor or less a "feature". If you don't like it, propose a
79 !! method how a subscript inset can figure out what is "optically" lower
82 // - When you press the mouse just to the left of the middle point of
83 // some char, the cursor will be positioned to the right of the char.
85 - It is possible to put two or more consecutive spaces in math text mode
87 // - Text in superscript is not smaller than normal text.
89 ?? - After insertion of \sum, the cursor is in invalid location
90 ?? There is still a problem when doing c-m \sum S-C-M
92 ?? - The height of the frame is often wrong (e.g. x^2)
93 ?? For example $\sum x$ in an inline formula
95 - InsetFormula::validate is broken
97 // - Changing math space length by pressing the space-bar key doesn't work
98 !! it's M-m space now.
100 - The drawing of decorations on screen is very different than latex.
101 (a low priority bug).
103 - If I change '\alpha' to bold, the result is \mathbf{a}
105 - Just moving the cursor in a math inset causes changing the buffer status
108 - disable the insert->label menu item when in inline formula.
113 - When exiting the formula during selection, the anchor moves to the
114 left of the formula and there's no way to go back.
116 // - Scripts are too large. $\log_2$ exceeds inset frame (non-displayed).
118 - You need two <right> to get past \vec{v}, and all sort of other
121 - \vec{several-characters} doesn't work. \overrightarrow does.
123 - When the cursor is in a subscript (and either isn't at the end of
124 the subscript or there's no subsubscript), pressing <down> should
125 try to *really* go down (to the next line, or denumerator, or
126 whatever). Currently it goes *up*. Ditto for superscripts.
128 :: Please see comment to Dekel's report on the same problem.
130 // - When choosing to insert "\left\Vert \right\Vert" parenthesis using
131 // the maths [sic] panel, a "\left( \right." is inserted instead.
133 - Formula inside tabular cell: red frame of cell inset and purple
134 frame of formula can overlap, causing leftovers when leaving
135 formula. To get an example, insert a 1x1 tabular into a new document,
136 enter the cell its cell and press
137 M-m ( M-f 1 <right> <right> <right> (zoom=100, screenDPI=100)
139 - When selecting multiple cells in a array using the keyboard, <left>
140 etc. should can move whole cell at a time -- no need to navigate
143 - When selecting, maybe give a visual indication of the "original"
144 anchor, when it differs from the "actual" one.
146 // - C-v always pastes into the end of the current math inset, instead of
147 // the cursor location.
149 - Placement of cursor using mouse is seriously broken.
150 Example 1: large fractions.
151 Example 2: type into a new document:
152 "M-d xxxxxxxxx <right> M-x footnote-insert"
153 Can't reach most places in the formula using mouse.
159 - Entering \mathbf{c} in math mode is displayed as written (without
162 - I know the latex code of a lot of math symbols displayed by lyx,
163 but not all of them. Thus I have to use the math panel for only a single
164 symbol in a formula. I think it would be very useful, if the latex code
165 of the symbol would be displayed as a hint, if the mouse positioned over
169 Marcus (Suran@gmx.net)
171 // - In math-mode I can switch back to text-mode in a formula but then I am
172 // not able to type Umlauts.
174 ?? - Having selected some part of a formula and creating a fraction with that
175 ?? part in the top my selection-buffer is replaced with the part.
177 - If the math-panel has the focus I can type text but not switch into
178 math-mode or use some of the other keyboard-shortcuts.
180 - In the default-configuration there are shortcuts for al greek characters
181 _except_ varphi wich is used extensively as a default-variable-name.
184 From: Álvaro Tejero Cantero <alvaro@antalia.com>
186 - the most annoying bug by far: bold is "inherited" to super and subscripts.
188 - when you get into equation array mode, the previous equation(s) remain(s)
189 unaligned. I would be soo much faster to have LyX pick the last equal sign
190 from the previous line as a reference for the alignment (and a good heuristic
191 for the 80% of cases, with the advantage that we don't lose anything
192 enforcing it). This is another case that slows down a lot when typing
193 because, as the previous one, requires going back and correcting.
195 - the movement is sometimes clumsy inside this arrayed equations: ie. C-a (or
196 "home" are understood as "beginning of the formula" instead of "beginning of
197 the equation". Again, a lot of movement has to be made. I suggest mapping
198 "beginning of doc" with "beginning of formula" and so on (very intuitive), in
199 case you don't deem appropriate the "namespace idea" below.
201 //- movement between macro boxes is also weird, but in this one it's perhaps
204 - I suggest creating a different "kewybinding namespace" for the formulas,
205 since you could put to good use all those keybindings from the menu (M-?,
206 C-?) thath currently do their job PLUS getting you out of the formula.
207 Seriously, it'd be great to have more keys free, so M-d t would be time
208 derivative and M-d ? derivative with respect to the variable ?. And so on.
210 - I'm no experienced C++ programmer, but if you consider it appropriate, I
211 could write a scritp in python for this one (I'm also very optimistic). Tell
214 Flattening macros. Sometimes it's annoying the fact that once you have
215 written a macro, you can't touch at it's "constant parts". I call flattening
216 to the process of substituting all macros with LaTeX code.
218 Task: designing a macro substitution system that reads from a file
219 (possibly the same file as the document's) the macros and parses the document
220 doing the appropriate replacements
222 This is very useful, because sometimes you have a big expression in a macro
223 and you want to change an index only. What do you do then?. You retype
224 everything (perhaps several times in the document) or you create extremely
225 generic and parametrizable macros that aren't very fast to fill in the
229 - undo-redo seems too coarse in math-mode. You end up losing substantial
230 fragments of your formula. I hate that when it affects tensors,;).
232 - cut&paste inside math-mode doesn't work the X fashion (middle button doesn't
235 - I remember having heard that a search-replace function was planned, so I
236 won't repeat that. Only that the flattening option would be then easier to
237 implement on top of that.
239 - There's something I keep wondering about.. how do new math symbols get into
240 LyX. Do they get ever?. I don't know if it can be done, but if you tell me
241 where to "draw" those symbols or how, I would very glad start doing it. LyX
242 deserves to have support (visual support) for all the AMSTeX constructs. But
243 there must be something structural going on there, because otherwise more
244 math symbols would be ready by now.. just a thought.
246 - Some math symbols aren't very well supported (to my knowledge). I'm
247 thinking of underbraces with extra data in them,or [] options.
252 - it's not possible to enter superscript when the
253 ^-char works as a dead key. with the second ^-
254 or the space the cursor jumps outside the mathbox.
260 - I've been using Lyx for a year or two now, and I have some thoughts on
261 improving the interface. Not the GUI, as such, but the basic Human-Machine
262 interface --- the efficiency with which I can enter information into it.
264 There are a couple of general principles I'm try to uphold here:
266 a) If something's easy & quick in LaTeX then it should be easy & quick in
267 LyX (unless it really isn't very common). b) Actions which are used
268 frequently should be a single key-press, even if that's not very easy to
269 remember. You learn it. c) Actions which are used rarely should be
270 mnemonic -- easy to remember -- even if they are multiple keypresses.
271 Things you do rarely you care less about the time it takes to perform.
273 2) Math-mode entry Under the xemacs keybindings, which I use, (damn it,
274 I don't want to confuse my poor muscle memory more than necessary by
275 learning too many different bindings for the same actions), the key
276 sequence to enter math-mode is 'M-c m'. I'm not sure exactly what to
277 propose instead, but I really think this needs to be only one keypress.
279 As an aside, you may think that I'm whining over nothing. However, when
280 you enter math mode as often as I do (often more than once a sentence) it
281 gets very annoying, especially as compared to simply typing '$' in plain
282 emacs. Also, you may say 'why don't you just change your bindings file?'. I
283 will ;) but I wanted to start some discussion on this since it can benefit
286 More serious, though, than the number of characters which need to be typed
287 is the confusing nature of the command. 'M-c m', typed once, puts you into
288 math-mode. However, typing 'M-c m' again doesn't put you out of math-mode
289 --- it puts you into math-text mode. Then hitting it again puts you back
290 into normal math-mode. IMO, 'modal' keys should either be idempotent (so
291 hitting it the second time does nothing) or self-inverting. In fact, the
292 inverse to 'M-c m' is either 'ESC' or simply a space typed at the end of
293 the block --- which is confusing, since they're not of the same 'shape' as
294 the command that got you in there.
296 Now, I'm not saying that 'space' shouldn't be allowed as a short-cut to get
297 you out of math-mode; it's a most useful and natural one, I like it a lot.
298 However, on balance I think M-c m should also have that effect.
300 3) Math-mode inconsistencies
302 Sometimes 'the same action' has the same keystroke both within and
303 without math-mode. This is very sensible. However, it is very annoying when
304 they don't behave the way you're expecting them to.
306 For example, 'M-c e' puts you into 'emphasise' mode. Ignoring the fact
307 that in text mode this is italics, and in math-mode it stands for the
308 calligraphic character set, I think of these as the same action, so I like
309 the fact that they have the same keys. However, in math-mode, 'M-c e' is
310 idempotent, (and you need 'M-c space' to get back into normal) whereas in
311 text-mode 'M-c e' is self-inverse. These are the two possibilities I listed
312 as acceptable before, but consistency would be nice ;-) IMO, self-inverse
313 would be best for both.
317 Math-mode doesn't handle ERT very well at all. It flips back out of
318 TeX-mode as soon as you type any special character. Very annoying if I
319 wish to typeset an \xymatrix inside math-mode (see also my comment above
320 about table-like environments), since I can't type the &. In fact, my
321 xymatrices end up as $$\xymatrix{..}$$ in text-mode ERT. Also rather
322 annoying when you want to use a \macro with more than one argument (but not
325 5) Proposal : a 'ligatures' or 'autocorrect' system
327 One of the very minor, but useful, features of TeX is the way it lets you
328 type the nearest approximation to what you want using a 'typewriter
329 keyboard', and substitutes the typographically neat equivalent. In
330 particular, 'fancy' quotes (") and en and em dashes (---). I propose that
331 this UI element could be taken up a level into LyX, with a system that does
332 the following (for example):
334 -> becomes \rightarrow
335 <- becomes \leftarrow
336 => becomes \Rightarrow (etc..)
337 ==> becomes \Longrightarrow (etc..)
339 This may only be appropriate in math mode, of course. This family bug me
340 in particular because they take ages to type using a \-escape. Undoubtedly
341 sharp minds will think of others, and also we need some way of actually
342 typing those sequences as literals when we want them.
346 The current macro system is clever, but could be neater. One improvement
347 I'd like is to let LyX know about TeX's scoping rules...
352 - use AMS's \text instead of \mbox. It supports accented characters,
353 among others... (selected via validate()?)
358 > \def\neq{\not=} \let\ne=\neq
362 > \let\gets=\leftarrow
363 > \let\to=\rightarrow
364 > % \let\@@sqrt\sqrtsign
369 - make math lables editable
373 - An inline equation does not get a number, so putting a label there is not
375 Ok. In that case show a message in the bottom similarly as the message
376 "you cannot type two spaces this way". Eg. "You can insert math labels
377 only in display mode"