Timeline for Painfully slow encoding popup with "temp file" when creating new file
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 1, 2019 at 7:59 | vote | accept | tenpn | ||
| Sep 30, 2019 at 22:20 | answer | added | phils | timeline score: 0 | |
| Sep 30, 2019 at 21:21 | answer | added | tenpn | timeline score: 0 | |
| S Feb 27, 2018 at 11:44 | history | bounty ended | CommunityBot | ||
| S Feb 27, 2018 at 11:44 | history | notice removed | CommunityBot | ||
| Feb 23, 2018 at 17:07 | comment | added | tenpn |
recursive edit did nothing for me - helm-get-nth-action: No such action
|
|
| Feb 22, 2018 at 2:29 | comment | added | Tobias |
I don't have helm. But maybe M-: (global-set-key (kbd "<f5>") #'recursive-edit) and M-: (setq enable-recursive-minibuffers t) helps. Hopefully you can escape helm by entering recursive edit via function key f5. Go to the temp buffer and investigate it. When you are done input M-x exit-recursive-edit.
|
|
| Feb 20, 2018 at 18:29 | comment | added | tenpn | I can't break out of the helm pop-up to get into the displayed temp window. It only appears during file opens, then goes away. | |
| Feb 19, 2018 at 22:00 | comment | added | Tobias |
Try M-: default-directory in buffer <*temp file*> to see where emacs wants to save that file. The directory name may even give a clue on the source of that buffer.
|
|
| Feb 19, 2018 at 14:06 | comment | added | stsquad | Running M-x describe-mode while in the temp buffer may give you a clue as to what is messing with it. | |
| Feb 19, 2018 at 12:26 | comment | added | tenpn | yeah, they're definition files from my projects. I have no solid repro so I've messed around with -Q and not seen it, but that isn't a strong endorsement and I'm not using -Q all day. I guess I'm going to have start chopping stuff out of my config, aren't I? | |
| Feb 19, 2018 at 12:23 | comment | added | stsquad | do you recognise any of the stuff in the temp buffer? Could it be flycheck/flymake results being triggered by a change to the file you are opening? Can you trigger the problem with emacs -Q? | |
| Feb 19, 2018 at 11:31 | comment | added | tenpn | also it doesn't seem consistent - the incident I had this morning was opening a file I've opened swiftly multiple times in the last few weeks, and has no non-ascii chars. | |
| Feb 19, 2018 at 11:30 | comment | added | tenpn | it previews the temp file in the top-right of my screenshot, and that's not what I'm opening. I'm just opening a regular code file, not a huge list of other files. | |
| Feb 19, 2018 at 11:05 | comment | added | stsquad | I'm assuming the temp file is an interim buffer that emacs creates to encode the file you just opened. Is there any reason to think it is unrelated to the file you just opened? | |
| Feb 19, 2018 at 10:32 | comment | added | tenpn | this file that can't be encoded is the *temp* file, and I can't find anything on where that lives (if it's even an on-disk file) | |
| Feb 19, 2018 at 10:29 | comment | added | stsquad | The first thing to check is if this happens in an emacs -Q environment. Does the "file" utility report the encoding for these files? | |
| S Feb 19, 2018 at 9:55 | history | bounty started | tenpn | ||
| S Feb 19, 2018 at 9:55 | history | notice added | tenpn | Draw attention | |
| Feb 16, 2018 at 15:24 | history | asked | tenpn | CC BY-SA 3.0 |