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
17 Unmarked items are known unfixed but probably unverified bugs.
19 ----------------------------------------------------------------------
21 General hints for bug reports:
23 - keep the items small
25 - do not provide excessive information on how to reproduce the bug
28 - if a bug is partly fixed, report it as "fixed" and a new bug item
29 that contains the unfixed part only
31 - check this list regularly, comment on the marked items.
33 - plain ASCII text please, not much more than 70 chars per column
35 ----------------------------------------------------------------------
41 // - When changing the macro definition, all instances are not updated.
43 // - If I have macros \newcommand{\foo}[1]{[#1]} and
44 // \newcommand{\foox}{\foo{x}} then when an instance of \foox is drawn on
45 // screen, there are two black frames. While this is "correct", it is
48 - LyX crashes when you define a recursive macro
52 // - If I have x_{1}^{2}, I put the cursor before the 2, and press backspace,
53 // the result is 'x2'. The correct result should be 'x_{1}2'
55 // - If I mark some text and then press ^, then the marked text is deleted.
56 // The correct behavior is to put the marked text in the superscript.
58 // - Pressing <down> when cursor is in subscript will move the cursor up
59 // (to the base of the subscript) instead of exiting the inset.
60 // The same problem happen in fractions
62 // - When you press the mouse just to the left of the middle point of
63 // some char, the cursor will be positioned to the right of the char.
65 pp - It is possible to put two or more consecutive spaces in math text mode
67 // - Text in superscript is not smaller than normal text.
69 // - After insertion of \sum, the cursor is in invalid location
71 // - The height of the frame is often wrong (e.g. x^2)
72 // For example $\sum x$ in an inline formula
74 - InsetFormula::validate is broken
76 // - Changing math space length by pressing the space-bar key doesn't work
77 !! it's M-m space now.
79 // - The drawing of decorations on screen is very different than latex.
80 // (a low priority bug).
82 // - If I change '\alpha' to bold, the result is \mathbf{a}
84 // - Just moving the cursor in a math inset causes changing the buffer status
87 // - disable the insert->label menu item when in inline formula.
92 // - When exiting the formula during selection, the anchor moves to the
93 // left of the formula and there's no way to go back.
95 // - Scripts are too large. $\log_2$ exceeds inset frame (non-displayed).
97 // - You need two <right> to get past \vec{v}, and all sort of other
102 // - \vec{several-characters} doesn't work. \overrightarrow does.
104 // - When the cursor is in a subscript (and either isn't at the end of
105 // the subscript or there's no subsubscript), pressing <down> should
106 // try to *really* go down (to the next line, or denumerator, or
107 // whatever). Currently it goes *up*. Ditto for superscripts.
109 // - When choosing to insert "\left\Vert \right\Vert" parenthesis using
110 // the maths [sic] panel, a "\left( \right." is inserted instead.
112 // - Formula inside tabular cell: red frame of cell inset and purple
113 // frame of formula can overlap, causing leftovers when leaving
114 // formula. To get an example, insert a 1x1 tabular into a new document,
115 // enter the cell its cell and press
116 // M-m ( M-f 1 <right> <right> <right> (zoom=100, screenDPI=100)
118 // - When selecting multiple cells in a array using the keyboard, <left>
119 // etc. should can move whole cell at a time -- no need to navigate
122 - When selecting, maybe give a visual indication of the "original"
123 anchor, when it differs from the "actual" one.
125 // - Placement of cursor using mouse is seriously broken.
126 // Example 1: large fractions.
127 // Example 2: type into a new document:
128 // "M-d xxxxxxxxx <right> M-x footnote-insert"
129 // Can't reach most places in the formula using mouse.
135 - Entering \mathbf{c} in math mode is displayed as written (without
138 - I know the latex code of a lot of math symbols displayed by lyx,
139 but not all of them. Thus I have to use the math panel for only a single
140 symbol in a formula. I think it would be very useful, if the latex code
141 of the symbol would be displayed as a hint, if the mouse positioned over
145 Marcus (Suran@gmx.net)
147 - In math-mode I can switch back to text-mode in a formula but then I am
148 not able to type Umlauts.
150 ?? - Having selected some part of a formula and creating a fraction with that
151 ?? part in the top my selection-buffer is replaced with the part.
153 - If the math-panel has the focus I can type text but not switch into
154 math-mode or use some of the other keyboard-shortcuts.
156 - In the default-configuration there are shortcuts for al greek characters
157 _except_ varphi wich is used extensively as a default-variable-name.
160 From: Álvaro Tejero Cantero <alvaro@antalia.com>
162 - the most annoying bug by far: bold is "inherited" to super and subscripts.
164 // - when you get into equation array mode, the previous equation(s)
165 // remain(s) unaligned. I would be soo much faster to have LyX pick the
166 // last equal sign from the previous line as a reference for the alignment
167 // (and a good heuristic for the 80% of cases, with the advantage that we
168 // don't lose anything enforcing it). This is another case that slows down
169 // a lot when typing because, as the previous one, requires going back
172 // - the movement is sometimes clumsy inside this arrayed equations: ie.
173 // C-a (or "home" are understood as "beginning of the formula" instead of
174 // "beginning of the equation". Again, a lot of movement has to be made.
175 // I suggest mapping "beginning of doc" with "beginning of formula" and so
176 // on (very intuitive), in case you don't deem appropriate the "namespace
179 //- movement between macro boxes is also weird, but in this one it's perhaps
182 - I suggest creating a different "kewybinding namespace" for the formulas,
183 since you could put to good use all those keybindings from the menu (M-?,
184 C-?) thath currently do their job PLUS getting you out of the formula.
185 Seriously, it'd be great to have more keys free, so M-d t would be time
186 derivative and M-d ? derivative with respect to the variable ?. And so on.
188 - I'm no experienced C++ programmer, but if you consider it appropriate, I
189 could write a scritp in python for this one (I'm also very optimistic). Tell
192 Flattening macros. Sometimes it's annoying the fact that once you have
193 written a macro, you can't touch at it's "constant parts". I call flattening
194 to the process of substituting all macros with LaTeX code.
196 Task: designing a macro substitution system that reads from a file
197 (possibly the same file as the document's) the macros and parses the document
198 doing the appropriate replacements
200 This is very useful, because sometimes you have a big expression in a macro
201 and you want to change an index only. What do you do then?. You retype
202 everything (perhaps several times in the document) or you create extremely
203 generic and parametrizable macros that aren't very fast to fill in the
207 - undo-redo seems too coarse in math-mode. You end up losing substantial
208 fragments of your formula. I hate that when it affects tensors,;).
210 - cut&paste inside math-mode doesn't work the X fashion (middle button doesn't
213 - I remember having heard that a search-replace function was planned, so I
214 won't repeat that. Only that the flattening option would be then easier to
215 implement on top of that.
217 // - There's something I keep wondering about.. how do new math symbols get
218 // into LyX. Do they get ever?. I don't know if it can be done, but if you
219 // tell me where to "draw" those symbols or how, I would very glad start
220 // doing it. LyX deserves to have support (visual support) for all the
221 // AMSTeX constructs. But there must be something structural going on
222 // there, because otherwise more math symbols would be ready by now..
225 - Some math symbols aren't very well supported (to my knowledge). I'm
226 thinking of underbraces with extra data in them,or [] options.
231 - it's not possible to enter superscript when the
232 ^-char works as a dead key. with the second ^-
233 or the space the cursor jumps outside the mathbox.
239 - I've been using Lyx for a year or two now, and I have some thoughts on
240 improving the interface. Not the GUI, as such, but the basic Human-Machine
241 interface --- the efficiency with which I can enter information into it.
243 There are a couple of general principles I'm try to uphold here:
245 a) If something's easy & quick in LaTeX then it should be easy & quick in
246 LyX (unless it really isn't very common). b) Actions which are used
247 frequently should be a single key-press, even if that's not very easy to
248 remember. You learn it. c) Actions which are used rarely should be
249 mnemonic -- easy to remember -- even if they are multiple keypresses.
250 Things you do rarely you care less about the time it takes to perform.
252 // 2) Math-mode entry Under the xemacs keybindings, which I use, (damn it,
253 // I don't want to confuse my poor muscle memory more than necessary by
254 // learning too many different bindings for the same actions), the key
255 // sequence to enter math-mode is 'M-c m'. I'm not sure exactly what to
256 // propose instead, but I really think this needs to be only one keypress.
260 As an aside, you may think that I'm whining over nothing. However, when
261 you enter math mode as often as I do (often more than once a sentence) it
262 gets very annoying, especially as compared to simply typing '$' in plain
263 emacs. Also, you may say 'why don't you just change your bindings file?'. I
264 will ;) but I wanted to start some discussion on this since it can benefit
267 More serious, though, than the number of characters which need to be typed
268 is the confusing nature of the command. 'M-c m', typed once, puts you into
269 math-mode. However, typing 'M-c m' again doesn't put you out of math-mode
270 --- it puts you into math-text mode. Then hitting it again puts you back
271 into normal math-mode. IMO, 'modal' keys should either be idempotent (so
272 hitting it the second time does nothing) or self-inverting. In fact, the
273 inverse to 'M-c m' is either 'ESC' or simply a space typed at the end of
274 the block --- which is confusing, since they're not of the same 'shape' as
275 the command that got you in there.
277 Now, I'm not saying that 'space' shouldn't be allowed as a short-cut to get
278 you out of math-mode; it's a most useful and natural one, I like it a lot.
279 However, on balance I think M-c m should also have that effect.
281 3) Math-mode inconsistencies
283 Sometimes 'the same action' has the same keystroke both within and
284 without math-mode. This is very sensible. However, it is very annoying when
285 they don't behave the way you're expecting them to.
287 For example, 'M-c e' puts you into 'emphasise' mode. Ignoring the fact
288 that in text mode this is italics, and in math-mode it stands for the
289 calligraphic character set, I think of these as the same action, so I like
290 the fact that they have the same keys. However, in math-mode, 'M-c e' is
291 idempotent, (and you need 'M-c space' to get back into normal) whereas in
292 text-mode 'M-c e' is self-inverse. These are the two possibilities I listed
293 as acceptable before, but consistency would be nice ;-) IMO, self-inverse
294 would be best for both.
298 Math-mode doesn't handle ERT very well at all. It flips back out of
299 TeX-mode as soon as you type any special character. Very annoying if I
300 wish to typeset an \xymatrix inside math-mode (see also my comment above
301 about table-like environments), since I can't type the &. In fact, my
302 xymatrices end up as $$\xymatrix{..}$$ in text-mode ERT. Also rather
303 annoying when you want to use a \macro with more than one argument (but not
306 5) Proposal : a 'ligatures' or 'autocorrect' system
308 One of the very minor, but useful, features of TeX is the way it lets you
309 type the nearest approximation to what you want using a 'typewriter
310 keyboard', and substitutes the typographically neat equivalent. In
311 particular, 'fancy' quotes (") and en and em dashes (---). I propose that
312 this UI element could be taken up a level into LyX, with a system that does
313 the following (for example):
315 -> becomes \rightarrow
316 <- becomes \leftarrow
317 => becomes \Rightarrow (etc..)
318 ==> becomes \Longrightarrow (etc..)
320 This may only be appropriate in math mode, of course. This family bug me
321 in particular because they take ages to type using a \-escape. Undoubtedly
322 sharp minds will think of others, and also we need some way of actually
323 typing those sequences as literals when we want them.
327 The current macro system is clever, but could be neater. One improvement
328 I'd like is to let LyX know about TeX's scoping rules...
333 - use AMS's \text instead of \mbox. It supports accented characters,
334 among others... (selected via validate()?)
339 // \def\neq{\not=} \let\ne=\neq
343 // \let\gets=\leftarrow
344 // \let\to=\rightarrow
349 - make math lables editable
353 // - An inline equation does not get a number, so putting a label there is not
354 // overly sensible...
355 // Ok. In that case show a message in the bottom similarly as the message
356 // "you cannot type two spaces this way". Eg. "You can insert math labels
357 // only in display mode"
359 :: Not a bug. It's allowed by LaTeX and there might be other reasons for
360 :: putting labels there. I won't add extra code to disable this.