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
111 - When exiting the formula during selection, the anchor moves to the
112 left of the formula and there's no way to go back.
114 // - Scripts are too large. $\log_2$ exceeds inset frame (non-displayed).
116 - You need two <right> to get past \vec{v}, and all sort of other
119 - \vec{several-characters} doesn't work. \overrightarrow does.
121 - When the cursor is in a subscript (and either isn't at the end of
122 the subscript or there's no subsubscript), pressing <down> should
123 try to *really* go down (to the next line, or denumerator, or
124 whatever). Currently it goes *up*. Ditto for superscripts.
126 :: Please see comment to Dekel's report on the same problem.
128 // - When choosing to insert "\left\Vert \right\Vert" parenthesis using
129 // the maths [sic] panel, a "\left( \right." is inserted instead.
131 - Formula inside tabular cell: red frame of cell inset and purple
132 frame of formula can overlap, causing leftovers when leaving
133 formula. To get an example, insert a 1x1 tabular into a new document,
134 enter the cell its cell and press
135 M-m ( M-f 1 <right> <right> <right> (zoom=100, screenDPI=100)
137 - When selecting multiple cells in a array using the keyboard, <left>
138 etc. should can move whole cell at a time -- no need to navigate
141 - When selecting, maybe give a visual indication of the "original"
142 anchor, when it differs from the "actual" one.
144 // - C-v always pastes into the end of the current math inset, instead of
145 // the cursor location.
147 - Placement of cursor using mouse is seriously broken.
148 Example 1: large fractions.
149 Example 2: type into a new document:
150 "M-d xxxxxxxxx <right> M-x footnote-insert"
151 Can't reach most places in the formula using mouse.
157 - Entering \mathbf{c} in math mode is displayed as written (without
161 Marcus (Suran@gmx.net)
163 // - In math-mode I can switch back to text-mode in a formula but then I am
164 // not able to type Umlauts.
166 ?? - Having selected some part of a formula and creating a fraction with that
167 ?? part in the top my selection-buffer is replaced with the part.
169 - If the math-panel has the focus I can type text but not switch into
170 math-mode or use some of the other keyboard-shortcuts.
172 - In the default-configuration there are shortcuts for al greek characters
173 _except_ varphi wich is used extensively as a default-variable-name.
176 From: Álvaro Tejero Cantero <alvaro@antalia.com>
178 - the most annoying bug by far: bold is "inherited" to super and subscripts.
180 - when you get into equation array mode, the previous equation(s) remain(s)
181 unaligned. I would be soo much faster to have LyX pick the last equal sign
182 from the previous line as a reference for the alignment (and a good heuristic
183 for the 80% of cases, with the advantage that we don't lose anything
184 enforcing it). This is another case that slows down a lot when typing
185 because, as the previous one, requires going back and correcting.
187 - the movement is sometimes clumsy inside this arrayed equations: ie. C-a (or
188 "home" are understood as "beginning of the formula" instead of "beginning of
189 the equation". Again, a lot of movement has to be made. I suggest mapping
190 "beginning of doc" with "beginning of formula" and so on (very intuitive), in
191 case you don't deem appropriate the "namespace idea" below.
193 //- movement between macro boxes is also weird, but in this one it's perhaps
196 - I suggest creating a different "kewybinding namespace" for the formulas,
197 since you could put to good use all those keybindings from the menu (M-?,
198 C-?) thath currently do their job PLUS getting you out of the formula.
199 Seriously, it'd be great to have more keys free, so M-d t would be time
200 derivative and M-d ? derivative with respect to the variable ?. And so on.
202 - I'm no experienced C++ programmer, but if you consider it appropriate, I
203 could write a scritp in python for this one (I'm also very optimistic). Tell
206 Flattening macros. Sometimes it's annoying the fact that once you have
207 written a macro, you can't touch at it's "constant parts". I call flattening
208 to the process of substituting all macros with LaTeX code.
210 Task: designing a macro substitution system that reads from a file
211 (possibly the same file as the document's) the macros and parses the document
212 doing the appropriate replacements
214 This is very useful, because sometimes you have a big expression in a macro
215 and you want to change an index only. What do you do then?. You retype
216 everything (perhaps several times in the document) or you create extremely
217 generic and parametrizable macros that aren't very fast to fill in the
221 - undo-redo seems too coarse in math-mode. You end up losing substantial
222 fragments of your formula. I hate that when it affects tensors,;).
224 - cut&paste inside math-mode doesn't work the X fashion (middle button doesn't
227 - I remember having heard that a search-replace function was planned, so I
228 won't repeat that. Only that the flattening option would be then easier to
229 implement on top of that.
231 - There's something I keep wondering about.. how do new math symbols get into
232 LyX. Do they get ever?. I don't know if it can be done, but if you tell me
233 where to "draw" those symbols or how, I would very glad start doing it. LyX
234 deserves to have support (visual support) for all the AMSTeX constructs. But
235 there must be something structural going on there, because otherwise more
236 math symbols would be ready by now.. just a thought.
238 - Some math symbols aren't very well supported (to my knowledge). I'm
239 thinking of underbraces with extra data in them,or [] options.
244 - it's not possible to enter superscript when the
245 ^-char works as a dead key. with the second ^-
246 or the space the cursor jumps outside the mathbox.
252 - I've been using Lyx for a year or two now, and I have some thoughts on
253 improving the interface. Not the GUI, as such, but the basic Human-Machine
254 interface --- the efficiency with which I can enter information into it.
256 There are a couple of general principles I'm try to uphold here:
258 a) If something's easy & quick in LaTeX then it should be easy & quick in
259 LyX (unless it really isn't very common). b) Actions which are used
260 frequently should be a single key-press, even if that's not very easy to
261 remember. You learn it. c) Actions which are used rarely should be
262 mnemonic -- easy to remember -- even if they are multiple keypresses.
263 Things you do rarely you care less about the time it takes to perform.
265 2) Math-mode entry Under the xemacs keybindings, which I use, (damn it,
266 I don't want to confuse my poor muscle memory more than necessary by
267 learning too many different bindings for the same actions), the key
268 sequence to enter math-mode is 'M-c m'. I'm not sure exactly what to
269 propose instead, but I really think this needs to be only one keypress.
271 As an aside, you may think that I'm whining over nothing. However, when
272 you enter math mode as often as I do (often more than once a sentence) it
273 gets very annoying, especially as compared to simply typing '$' in plain
274 emacs. Also, you may say 'why don't you just change your bindings file?'. I
275 will ;) but I wanted to start some discussion on this since it can benefit
278 More serious, though, than the number of characters which need to be typed
279 is the confusing nature of the command. 'M-c m', typed once, puts you into
280 math-mode. However, typing 'M-c m' again doesn't put you out of math-mode
281 --- it puts you into math-text mode. Then hitting it again puts you back
282 into normal math-mode. IMO, 'modal' keys should either be idempotent (so
283 hitting it the second time does nothing) or self-inverting. In fact, the
284 inverse to 'M-c m' is either 'ESC' or simply a space typed at the end of
285 the block --- which is confusing, since they're not of the same 'shape' as
286 the command that got you in there.
288 Now, I'm not saying that 'space' shouldn't be allowed as a short-cut to get
289 you out of math-mode; it's a most useful and natural one, I like it a lot.
290 However, on balance I think M-c m should also have that effect.
292 3) Math-mode inconsistencies
294 Sometimes 'the same action' has the same keystroke both within and
295 without math-mode. This is very sensible. However, it is very annoying when
296 they don't behave the way you're expecting them to.
298 For example, 'M-c e' puts you into 'emphasise' mode. Ignoring the fact
299 that in text mode this is italics, and in math-mode it stands for the
300 calligraphic character set, I think of these as the same action, so I like
301 the fact that they have the same keys. However, in math-mode, 'M-c e' is
302 idempotent, (and you need 'M-c space' to get back into normal) whereas in
303 text-mode 'M-c e' is self-inverse. These are the two possibilities I listed
304 as acceptable before, but consistency would be nice ;-) IMO, self-inverse
305 would be best for both.
309 Math-mode doesn't handle ERT very well at all. It flips back out of
310 TeX-mode as soon as you type any special character. Very annoying if I
311 wish to typeset an \xymatrix inside math-mode (see also my comment above
312 about table-like environments), since I can't type the &. In fact, my
313 xymatrices end up as $$\xymatrix{..}$$ in text-mode ERT. Also rather
314 annoying when you want to use a \macro with more than one argument (but not
317 5) Proposal : a 'ligatures' or 'autocorrect' system
319 One of the very minor, but useful, features of TeX is the way it lets you
320 type the nearest approximation to what you want using a 'typewriter
321 keyboard', and substitutes the typographically neat equivalent. In
322 particular, 'fancy' quotes (") and en and em dashes (---). I propose that
323 this UI element could be taken up a level into LyX, with a system that does
324 the following (for example):
326 -> becomes \rightarrow
327 <- becomes \leftarrow
328 => becomes \Rightarrow (etc..)
329 ==> becomes \Longrightarrow (etc..)
331 This may only be appropriate in math mode, of course. This family bug me
332 in particular because they take ages to type using a \-escape. Undoubtedly
333 sharp minds will think of others, and also we need some way of actually
334 typing those sequences as literals when we want them.
338 The current macro system is clever, but could be neater. One improvement
339 I'd like is to let LyX know about TeX's scoping rules...
344 - use AMS's \text instead of \mbox. It supports accented characters,
345 among others... (selected via validate()?)
350 > \def\neq{\not=} \let\ne=\neq
354 > \let\gets=\leftarrow
355 > \let\to=\rightarrow
356 > % \let\@@sqrt\sqrtsign
361 - make math lables editable
365 - An inline equation does not get a number, so putting a label there is not
367 Ok. In that case show a message in the bottom similarly as the message
368 "you cannot type two spaces this way". Eg. "You can insert math labels
369 only in display mode"