search

vermiculus / sx.el

Stack Exchange for Emacs
http://stackapps.com/q/3950
709 stars 40 forks source link

Remove read-only flag from compose buffer headlines. #360

Closed ghost closed 3 years ago

ghost commented 5 years ago

This partly closes #341. Drawback: The input lines headers can be edited now.

vermiculus commented 5 years ago

Drawback: The input lines headers can be edited now.

That's a pretty serious drawback – I'd like to avoid it if possible. We parse the buffer's content using those headers, so we could get into a state where the question/answer could not be posted and the user wouldn't know why (or worse, we could post with the wrong content!).

I would look at modifying the other properties to see how they behave – possibly reading (elisp) Special Properties and (elisp) Sticky Properties. I'm suspicious of the intangible property given the warnings in the info manual and its noted deprecation.

ghost commented 5 years ago

I completely agree that the drawback is serious. On the other hand, it's more serious if the component can't be used at all.

That being said: I'm very much an elisp rookie. So more elaborate fixes are beyond my abilities. More or less, I hoped to wake up people who know much more than me to have a look at this very fine package...

I would however be very interested in learning more elisp and this might be a fine opportunity. Could you give me some hints how I could play around with that issue and test/try out my code? Any hints welcome, maybe via PM.

ghost commented 5 years ago

Improved things somewhat: The keywords are r/o while you can enter text ;)

matthuszagh commented 4 years ago

Is there any status update on getting this merged? This is a great package and I'd really like to use it but unfortunately the inability to ask questions cuts out a large portion of the use case. Thanks for all the hard work you've already put into this!