Bug 318497

Summary: Auto brackets not working inside $$
Product: [Applications] kile Reporter: Gandalf Lechner <gandalflechner>
Component: editorAssignee: Michel Ludwig <michel.ludwig>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: 2.1.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Gandalf Lechner 2013-04-17 10:40:09 UTC
The auto bracket extension (automatically add the closing bracket when entering the opening bracket) is not always working. A prominent example is: You enter a $, and have kile configured such that it writes $$ and puts the cursor between the two $ signs (math mode). Then you start typing an equation, for example $f($ , and the closing bracket is not written - apparantly because there is the second $ sign right of the opening bracket. The same happens with other brackets [, {, but _not_ when you type the opening bracket with no letter right of it, i.e. typing f( would result in f() with the cursor between the brackets, as expected.

It also seems to me that some exceptions to the rule "don't add closing bracket when there is a character right next to the opening bracket" are implemented. For example, if you type a ( inside two straight brackets [ ], you would get [()], as expected. I would like to ask if precisely this behaviour could also be implemented when having $$ signs instead of [] signs, as it would make writing math formulas in kile so much easier.

Reproducible: Always

Steps to Reproduce:
see above
Actual Results:  
no closing bracket added

Expected Results:  
closing bracket added
Comment 1 Andrew Crouthamel 2018-11-10 03:15:22 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-20 04:10:29 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-02 02:04:10 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-17 05:15:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-02-01 05:05:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!