Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XML Snippets crashes Geany 1.26 on OS X 10.11.1 (El Capitan) #318

Open
jrittenh opened this issue Dec 9, 2015 · 5 comments
Open

XML Snippets crashes Geany 1.26 on OS X 10.11.1 (El Capitan) #318

jrittenh opened this issue Dec 9, 2015 · 5 comments

Comments

@jrittenh
Copy link

jrittenh commented Dec 9, 2015

I don't recall specifically enabling the XML Snippets plugin, but it appears to conflict with the internal XML tag closing mechanism in some way. I recently ran into an issue editing an XSL stylesheet where typing the closing bracket (>) would crash Geany. I disabled the XML Snippets plugin, and Geany didn't crash when typing the closing bracket, while allowing Geany to create the closing tag using the built-in function.

What does XML Snippets do that the XML/HTML tag auto-closing built-in feature doesn't? Should XML Snippets be removed?

@frlan
Copy link
Member

frlan commented Dec 9, 2015

How have you enabled the plugin? IIRC it's not shippied with Geany app.

@jrittenh
Copy link
Author

jrittenh commented Dec 9, 2015

I honestly don't know exactly how it was enabled, I'm assuming I checked the box in the plugin list at some point, but don't recall doing so explicitly.

Plugins are included in the OS X installer, as far as I can tell.

@jrittenh
Copy link
Author

jrittenh commented Dec 9, 2015

I honestly don't know exactly how it was enabled, I'm assuming I checked
the box in the plugin list at some point, but don't recall doing so
explicitly.

Plugins are included in the OS X installer, as far as I can tell.

On Wed, Dec 9, 2015 at 3:19 PM, Frank Lanitz notifications@github.com
wrote:

How have you enabled the plugin? IIRC it's not shippied with Geany app.


Reply to this email directly or view it on GitHub
#318 (comment)
.

@frlan
Copy link
Member

frlan commented Dec 10, 2015

My wrong. I messed it up with some missing plugins

@frlan
Copy link
Member

frlan commented Jan 2, 2019

@jrittenh Have you retried it with some more recent releases?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants