Locked temporary files
Bug #1540280 reported by
Andreas Roehler
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-mode.el |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
<email address hidden>, >> On 31.01.2016 07:02, Rusi wrote:
> Hi Andreas
>
> For many years Ive been a python-mode user. You will even find recommendations
> from me for this here and on the python list.
> Of late however its been a source of increasing glitches.
> Dont remember all... The last one was when a number of students were using the
> same VM and found that only one could use python-mode
Hmm, that's a bad thing indeed. Assume it's related to the locking done by Emacs. Seems we need a instance-related naming there, so every Emacs get its files.
Any ideas, how to write this, are welcome. Will open a ticket at https:/
| Changed in python-mode: | |
| assignee: | nobody → Andreas Roehler (a-roehler) |
| importance: | Undecided → High |
Revision history for this message
| Andreas Roehler (a-roehler) wrote | #1 |
| Changed in python-mode: | |
| importance: | High → Undecided |
| status: | New → Incomplete |
Revision history for this message
| Andreas Roehler (a-roehler) wrote | #2 |
| Changed in python-mode: | |
| assignee: | Andreas Roehler (a-roehler) → nobody |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in python-mode: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
As for not unique setup-files in /tmp read-access is sufficient, this bug should not exist anymore. Other opinions?