Version: 3.5.5-r1 (using KDE KDE 3.5.5) Installed from: Gentoo Packages OS: Linux It would be useful to be able to define different behaviours to different autocompletions. A) Autocomplete should recognize case. I for one don't type my html tags in capital letters and often end with things like the following when using autocomplete: <taBLE><tbODY><TR><br><TD></TR></TABLE> Notice the funky casing, the lowercase is my typing, uppercase is autocomplete. 'table' and 'tbody' are autocompleted for me after the first two letters, 'br' doesn't have a closing tag and is too short to be recognized before I get to '<br' anyway, and once I do get that far, it doesn't give me the option to autocomple, so I have to type out '/>' myself. I really do like having all my tags uppercase, I am just too lazy to do it. Ideally, rather than autocomplete match my tags case, there would be an option to just have all tag autocompletions go strait to uppercase, including the portions input by the user. So '<ta' would complete to '<TABLE>' rather than '<taBLE>', and '<br' would autocomplete to '<BR/>'. B)This may already be a feature that I couldn't find, but it would be useful if there was an option to always close tags. Some times when you are going quickly, you don't even think to press <enter> on autocompletions. This means you end up with: <table><tr><td> And none of the closing tags were automatically inserted so you are left manually inserting them. It would be nice if they would automatically: 1) Change the user typed code to uppercase (see above) 2) add the closing tag. So typing, '<table><tr><td>' would result in '<TABLE><TR><TD></TD></TR></TABLE>'. C) Lastly, it would also be nice if the closing tags on block level elements were automatically put on a new line... '<table>' would autocomplete as ... <TABLE>| </TABLE> Or, typing '<table>[enter]<tr>' would autocomplete as... <TABLE> <TR>| </TR> </TABLE> ('|' denotes cursor position) Thanks for reading all of this, regardless of whether these requests get implemented or not :)
Dear user, this wish list item is now closed, as it wasn't touched in the last two years and no contributor stepped up to implement it. The Kate/KTextEditor team is very small and we can just try to keep up with fixing bugs. Therefore wishs that show no activity for two years or more will be closed from now on to keep at least a bit overview about 'current' wishs of the users. If you want your feature to be implemented, please step up to provide some patch for it. If you think it is really needed, you can reopen your request, but keep in mind, if no new good arguments are made and no people get attracted to help out to implement it, it will expire in two years again. We have a nice website kate-editor.org that provides all the information needed to contribute, please make use of it. For highlighting improvements our user manual shows how to write syntax definition files. Greetings Christoph