On 21 Apr., 21:04, John Cremona <john.crem...@gmail.com> wrote: > On 21 April 2012 19:37, David Roe <roed.m...@gmail.com> wrote: > > > I've seen this as well, but I don't know what causes it. > > I am managing by using the wysiwyg box instead, which I would normally avoid.
You should be able to resize the text box, which IMHO has too few lines by default anyway. > The other thing which annoys me about trac which happens a lot when > several people are working on one ticket at the same time is when it > refuses to post your comment on the grounds that someone else has > changed the ticket since you started typing. This is stupid. It is. And that has been annoying me since I started working with trac; I've run into this hundreds of times. The reason presumably is that you can always change the ticket's description (and state) as well, without having to explicitly request for it. (And there's no way to suppress that. It would further certainly be easy for trac to first check whether you or a concurrent poster actually changed anything before rejecting a post.) > You have to be *very* careful with cut-and-paste not to lose what might be > a long and complicated comment. Well, "luckily" ;-) at least Sage's trac doesn't support HTTPS, so there's always the "go back" button. I have to admit I almost always copy my post into the clipboard before submitting, but for different reasons: * Occasionally trac logs you out, sometimes even without apparent reason (although going back, logging in from a different trac window and submitting again should usually work). * Fragile internet connections, such that one ends up with "server not found". (Same solution.) Things get more complicated if you at the same time do change some fields or the description. > email used to be like this about 20 years ago, when to avoid losing > work one would type into a file and only when finished cut-and-paste > into the email buffer. What ever happened to progress? These Python programmers start from scratch... ;-) -leif P.S.: Google's web interface to the groups isn't much more reliable, although somewhat surprisingly it *does* support concurrent posting, to some extent at least. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
