Thanks for the feedback. We’ll look into changing the default colour theme to make the highlight darker. In the mean time, note that you can choose from a variety of colour themes in your settings. :)
Update: You can now set your own title for display on your My Projects page by clicking on the gear icon in the top right of the project, or by choosing the Rename option on your My Projects dashboard. Smarter ‘de-tex’-ing for titles is still planned. Thanks for the feedback!
Thanks for the feedback. We will see what we can do to find titles in non-main files. In the mean time, you can set your own title by clicking on the gear icon in the top right of the project or by choosing the rename option on your My Projects dashboard.
Thanks for reporting this issue with the vim mode — we’ll look at it together with the other issue you reported.
Thanks for the feedback. We'll look into spaces vs. tabs in general as part of this.
Thanks for the feedback. Better search is definitely planned.
Thanks for the feedback. We are working on a better way of switching main files. The tip you mentioned should be working. If not, please send us the link to your project on writeLaTeX via www.writelatex.com/contact, and we’ll have a look.
Yes, I agree that dropdown is a good option.
To make that example work, you just need to switch which file the \input is in: you need
in shouldbemain.tex (not the other way around).
If there's anything else we can help with in the mean time, just let us know.
@EM Thanks for taking the time to provide feedback -- that's very helpful.
I'm afraid that iPad support is a moving target, and some things that worked in the past may not be working so well now, such as Puffin, which worked great last time I tried it! We'll review this internally and try to improve again.
I'm sorry for the inconvenience that this is causing.
@Joe Thanks for the feedback. This is still on our list, and we have made some improvements on iOS, but I'm afraid we've not found any way around the problem with the arrow keys. It may work a bit better if you switch to a different mobile browser, such as Puffin (http://www.puffinbrowser.com), which behaves a bit more like a desktop browser. Let us know if it helps!
Thank you very much for looking into this and for the link to editarea. We are working on a more mobile-friendly version of writeLaTeX, and we'll try out editarea to see whether it does what we need. I expect the main challenge will be getting the collaborative editing features to work in the new editor; we've got them working with other editors in the past, so we know it's possible, but it will take some time.
Thanks again, and stay tuned!
Thanks for the feedback. We are still planning to do this; it's just a question of priorities and resources.
There are several open issues on CodeMirror related to this; there's a recent summary at
and if anyone would like to contribute high quality bug reports and patches, I'm sure that the whole CM community would appreciate it.
Thanks for reporting this! It seems to be an issue with the code editor that we use. We're looking into how we can fix it, now. :)
Update: we now support linking your Zotero and Citeulike bibliographies with your projects on writeLaTeX
-see www.writelatex.com/blog/174 for info. Google Scholar support is still planned!
@Fernan Yes, we're also looking at how we can pull directly from PubMed.
Mendeley support is definitely planned, but we're currently waiting on them to add BibTeX support to their API. You can help us by voting up this idea on their feedback forum:
We are working on a way of giving you more control over the build process now. Thanks for the feedback!
@Daniel Thanks for the feedback -- we are indeed looking at an arara option.
@Anonymous -- thanks for the feedback. We don't currently accept donations, but we support Worldreader (http://www.worldreader.org/), and we'd be very pleased if you made a donation on our behalf.
For tables, there is an online editor here that's pretty good http://truben.no/latex/table/
Hopefully we'll integrate something like this one day.
I think 'kickstarter for features' is a good idea, but I've never found anyone doing it; if you find a service that provides this functionality, do let us know!
We're very glad to hear that. We're still looking at our options, and donations are one. Thanks for the feedback! :)
Update: We now have the building blocks in place for this, and we’ll try to get it installed and tested soon.
We are hoping to add features to the back end that will make it easier to support this, but it may take us a while. Thanks for the feedback!
We are making progress on this: the building blocks are there, so now we just have to install it and test it. Stay tuned!
We’ve seen several issues that cause cause the cursor to appear to be in the wrong place. If you hit one of these, can you please be sure to tell us:
1. Which browser and operating system are you using.
2. The text on the line that this problem occurs on.
This information makes it much easier for us to track down the causes of these problems. Thanks!
We've now upgraded the editor to the latest version, which is supposed to fix several potential problems with cursor positioning. If you still encounter this problem, can you please:
1. Tell us which browser and operating system versions you are using, and
2. Send a screen shot showing the paragraph that exhibits the problem, so we can see how it has wrapped.
Some possible workarounds for this issue are to resize the editor by dragging the separator bar between the editor and the preview, or to try using a different browser --- recent versions of Firefox and Chrome do not seem to be affected. We apologise for the inconvenience.
Thanks for reporting the issue with IE11. We're looking into it, and we'll try to get a fix as soon as possible. Until then, the best workaround is to use Chrome or Firefox. We'll keep you posted on progress. :)
Thanks for the feedback. I've reopened this issue.
We are looking at workarounds, but unfortunately the latest instance of this issue appears to be due to a browser bug breaking a library that we rely on, so it's a hard one. Watch this space...
Can you confirm which version of Chrome you've seen the problem with?
Thanks for reporting that Safari is also an option -- I haven't seen any issues in Safari as yet.
Thanks for reporting this. It looks like recent occurrences of this may be due to a bug introduced in Chromium. You can keep track of this here:
It would help if you can tell us exactly which versions of Chrome/Chromium you are using, by going to the About Google Chrome option in the three-bar menu, so we can narrow this down.
It looks like FireFox is not affected, so that's the best workaround we have at the moment (short of going back to an earlier version of Chrome/Chromium).
Sorry for the inconvenience and thanks for any help you can provide.
@Ben Thanks for reporting this. I think I can reproduce the problem, and it seems to map onto some open issues in CodeMirror, which is the code editing component that we use:
To help us resolve this, it would help if you could tell us:
1. The content of the line(s) that show the problem (or send us the link to the document, if you can) via https://www.writelatex.com/contact
2. Whether the problem goes away if you reload the page.
@Jigsaw I haven't found any other cursor movement gremlins since we upgraded, but if you can answer the above questions, that might help us narrow the search space.
Sorry for the inconvenience caused, and thanks again for continuing to report these issues.
7 votesAdminJohn Lees-Miller (Admin, writeLaTeX) shared this idea ·
Thanks for reporting this. We’re just in the process of upgrading our editing component to the latest version; I’ll check whether that fixes it.
Update: Upgrading has not helped. I will have to look into this further.
Thanks for getting in touch. We run TeX Live 2012 on the renderers, but I don’t know of any complete list of versions for all packages in TL 2012. I can tell you that we’re running tabu 2011/02/26 v2.8.
It might also be useful to note that you can upload .sty files to writeLaTeX to test other versions of packages.
Hope that helps :)
Thanks for the tip, Kolya -- that's very helpful!
Great idea! Thanks :)
Sorry for the delay. There isn't currently an option to change the tool chain on writeLaTeX, but this is something we're working on. We'll have a look at plates. Thanks for the feedback! :)
We’re looking into how we can support Markdown — would definitely be a good thing to have.
Great idea! Thanks for the link!
Thanks for the suggestion - we've focused initially on creating a low-barrier-to-entry front-end for LaTeX, but which still worked in the native language. We're still gathering feedback on writelatex,in order to help point us in future directions, and this is an interesting one.
Thanks — that’s a good idea. We’re looking into keyboard shortcuts for controlling the preview.
Thanks for reporting this, Isaiah. It seems to work in Chrome and Safari but not Firefox. I will try to fix this soon. :)
We’re part way there now: you can now import multiple files at once directly from your Google Drive into WriteLaTeX. Full sync coming soon. :)
Thanks for the suggestion! Integration with Google Drive would be very useful. :)
writeLaTeX works pretty well on iPad now, but there’s still room for improvement. :) Thanks for the feedback!
Great idea! WriteLaTeX does sort of work on mobile devices, but I agree that the experience could be much better.