-
Notifications
You must be signed in to change notification settings - Fork 40
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
(sx-ask) funcall-interactively: Text is read-only #341
Comments
Can you provide the backtrace given when debug-on-error is on? ( |
None is issued by Emacs, I toggle it and then reproduce the bug but no trace back is reported, just another message |
Funky. I'll see what I can find out. This project has seen something of a renewed interest from the community, so I'm hoping to revive the codebase soon with the practices I've learned from my work on magithub. I need to be careful though to not bite off more than I can chew :-) |
I got same issue too. When I |
But I typing text in the body area. |
@vermiculus The problem seems to exist with the definition of (defconst sx-compose--question-headers
(concat
#("Title: " 0 7 (intangible t read-only t rear-nonsticky t))
"%s"
#("\n" 0 1 (read-only t))
#("Tags : " 0 7 (read-only t intangible t rear-nonsticky t))
"%s"
#("\n" 0 1 (read-only t rear-nonsticky t))
#("________________________________________\n"
0 41 (read-only t rear-nonsticky t intangible t
sx-compose-separator t))
"\n")
"Headers inserted when composing a new question.
Used by `sx-compose-create'.") It seems that all of the headers have everything marked as read-only. So nothing can be typed anywhere, except in the body area. This should be fairly easy to fix by more carefully placing the read-only property. |
hi, just discovered your package and it looks great but this bug is kind of a shame is there any fix local correction? |
Hello, quite astonishing that this bug still isn't fixed. What's the use of the package if you can't ask questions? Anyway, I changed all
|
@Osram-Gru You might want to make this into a PR. |
The 'astonishing' thing is that I haven't had much use for the SE network in the past few years and thus have not been using this package. I bet this regression has something to do with the altered text property implementation in a recent major version break of Emacs. TBH, I don't think I've used this since Emacs 24.x. Please open a PR and I'll review/merge as appropriate. |
Pull request created right now. |
I'm still running into this bug. Reinstalled sx from latest on MELPA. IT looks like that pull never got merged. |
I sadly have not had as much time for extra-curriculars as I once had. If someone would like to revamp the PR such that it passes tests (with the understanding that it's not unlikely the tests themselves are broken), I can look at merging whatever changes make sense to folks. |
I still see this bug today. This never made it into the branch?;) There's no way to ask questions on SX with this package? Just asking;) |
you can use this (defconst sx-compose--question-headers
(concat
#("Title: " 0 7 (intangible t read-only t rear-nonsticky t))
"%s"
#("\n" 0 1 (read-only t))
#("Tags : " 0 7 (read-only t intangible t rear-nonsticky t))
"%s"
#("\n" 0 1 (read-only t rear-nonsticky t))
#("________________________________________\n"
0 41 (read-only t rear-nonsticky t intangible t
sx-compose-separator t))
"\n")
"Headers inserted when composing a new question.
Used by `sx-compose-create'.") just added a space as a work around in Tags and Title, works for me so far. |
When trying to write a question (sx-ask), I cannot type nor insert tags to the question due to an unknown issue when writing anywhere in the buffer, in the *Messages* buffer I get:
But whatever is going on is beyond me. This is my
sx
configuration:Basically nothing.
The text was updated successfully, but these errors were encountered: