Timeline for Prevent Emacs from asking "kill anyway" when only text properties have changed
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 6, 2015 at 19:34 | answer | added | glucas | timeline score: 2 | |
| Dec 4, 2014 at 2:20 | comment | added | Gilles 'SO- stop being evil' | If you're setting text properties which aren't meant to be saved in a file or copied and yanked, you should probably use overlays instead of text properties. See also What are overlays for, and how do they differ from text properties? | |
| Dec 2, 2014 at 21:36 | comment | added | zck |
@HåkonHægland You might want to save value of calling buffer-modified-p at the beginning of the function. That way, if something else modifies the buffer, you will still be prompted about it.
|
|
| Dec 2, 2014 at 20:15 | vote | accept | Håkon Hægland | ||
| Dec 2, 2014 at 20:07 | answer | added | ChrisR | timeline score: 5 | |
| Dec 2, 2014 at 20:05 | comment | added | Dan♦ | @ChrisR: I didn't see your comment before posting. Could you post your comment as an answer so that it could be accepted? | |
| Dec 2, 2014 at 20:03 | answer | added | Dan♦ | timeline score: 2 | |
| Dec 2, 2014 at 20:02 | comment | added | Håkon Hægland |
Thanks it works perfectly! I just put (set-buffer-modified-p nil) after I changed the property..
|
|
| Dec 2, 2014 at 19:59 | comment | added | ChrisR |
If you only care about changes that occur in this function, you can probably use buffer-modified-p and set-buffer-modified-p to store the modified state and restore it after changing the properties.
|
|
| Dec 2, 2014 at 19:55 | history | asked | Håkon Hægland | CC BY-SA 3.0 |