On 2021-04-20, Rainer Dorsch wrote:
>
> Other editors (vi, kate) don't report any issue when performain an edit
> operation. Is emacs trying to derive permissions in a different way?
There's this bug, which may or may not be pertinent.
https://gnu.emacs.bug.narkive.com/LoN17xVM/bug-37884-27-0-5
Hi David,
I did some more testing, you can see the effect on bullseye without vboxsf even
on a ext4 filesystem.
Am Mittwoch, 21. April 2021, 20:49:14 CEST schrieb David Wright:
[...deleted a lot of history]
> > -> buster emacs did not care at all about .# on filesystems which do not
> > support
On Tue 20 Apr 2021 at 20:43:46 (+0200), Rainer Dorsch wrote:
> Am Dienstag, 20. April 2021, 17:08:57 CEST schrieb Stefan Monnier:
> > > Because the error says it cannot use LOCKS.
> > > Because you can't do Unix file locking on a non-Unix file system.
> > > The error does NOT say "Permission denied
Am Dienstag, 20. April 2021, 17:08:57 CEST schrieb Stefan Monnier:
> > Because the error says it cannot use LOCKS.
> > Because you can't do Unix file locking on a non-Unix file system.
> > The error does NOT say "Permission denied".
>
> FWIW, the error comes from Emacs's own locking code which doe
Am Dienstag, 20. April 2021, 13:50:14 CEST schrieb to...@tuxteam.de:
> On Tue, Apr 20, 2021 at 07:28:19AM -0400, Greg Wooledge wrote:
> > On Tue, Apr 20, 2021 at 12:39:13PM +0200, to...@tuxteam.de wrote:
> > > On Tue, Apr 20, 2021 at 12:00:05PM +0200, Rainer Dorsch wrote:
> > > > For me the crucial
On Tue 20 Apr 2021 at 15:59:00 (+0200), Rainer Dorsch wrote:
> Am Dienstag, 20. April 2021, 13:50:14 CEST schrieb to...@tuxteam.de:
> > On Tue, Apr 20, 2021 at 07:28:19AM -0400, Greg Wooledge wrote:
> > > On Tue, Apr 20, 2021 at 12:39:13PM +0200, to...@tuxteam.de wrote:
> > > > On Tue, Apr 20, 2021
>> Emacs implements its locking protocol using symlinks with names
>> that look like `.#` and whose content looks like
>> `u...@host.pid:BOOT_TIME`.
>
> Ah, good old dot-locking. Well, perhaps the OP can test whether it's
> possible to create a symlink in that directory.
That's probably part of t
On Tue, Apr 20, 2021 at 11:08:57AM -0400, Stefan Monnier wrote:
> > Because the error says it cannot use LOCKS.
> > Because you can't do Unix file locking on a non-Unix file system.
> > The error does NOT say "Permission denied".
>
> FWIW, the error comes from Emacs's own locking code which doesn'
> Because the error says it cannot use LOCKS.
> Because you can't do Unix file locking on a non-Unix file system.
> The error does NOT say "Permission denied".
FWIW, the error comes from Emacs's own locking code which doesn't seem
to use unix file locking, so the problem comes from elsewhere.
Ema
Just another update which makes emacs behavior even stranger:
Even though emacs reports when saving
basic-save-buffer-2: Unlocking file: Operation not permitted,
/mnt/dor1rt/Local/ Managed/sb.blog
the file gets saved!
I think somehow emacs gets out of sync with the real system.
Rainer
Am Di
On Tue, Apr 20, 2021 at 03:59:00PM +0200, Rainer Dorsch wrote:
> > > > > basic-save-buffer-2: Unlocking file: Operation not permitted,
> > > > > /mnt/dor1rt/Local/ Managed/sb.blog
> Yes, correct, its mounted through virtualbox (vboxsf) and the host is a
> window
> system which uses NTFS (I think
Am Montag, 19. April 2021, 22:25:44 CEST schrieb to...@tuxteam.de:
> On Mon, Apr 19, 2021 at 06:48:41PM +0200, Rainer Dorsch wrote:
> > Hello,
> >
> > I hit a strange emacs issue, which appeared after upgrading to bullseye (I
> > think):
> >
> > I have a virtualbox filesystem mounted using the st
On Tue, Apr 20, 2021 at 07:28:19AM -0400, Greg Wooledge wrote:
> On Tue, Apr 20, 2021 at 12:39:13PM +0200, to...@tuxteam.de wrote:
> > On Tue, Apr 20, 2021 at 12:00:05PM +0200, Rainer Dorsch wrote:
> > > For me the crucial message is
> > >
> > > basic-save-buffer-2: Unlocking file: Operation not p
On Tue, Apr 20, 2021 at 12:39:13PM +0200, to...@tuxteam.de wrote:
> On Tue, Apr 20, 2021 at 12:00:05PM +0200, Rainer Dorsch wrote:
> > For me the crucial message is
> >
> > basic-save-buffer-2: Unlocking file: Operation not permitted,
> > /mnt/dor1rt/Local/
> > Managed/sb.blog
>
> Anyway, this i
On Tue, Apr 20, 2021 at 12:00:05PM +0200, Rainer Dorsch wrote:
> Am Montag, 19. April 2021, 22:25:44 CEST schrieb to...@tuxteam.de:
[...]
> > Perhaps Emacs is trying to write a backup file to the directory.
> > Does it have write access to the containing directory?
[...]
> There is nothing whic
Hello,
I hit a strange emacs issue, which appeared after upgrading to bullseye (I
think):
I have a virtualbox filesystem mounted using the standard virtualbox
mechanisms:
rd@Testing:~$ mount |grep dor1rt
dor1rt on /mnt/dor1rt type vboxsf (rw,nodev,relatime)
rd@Testing:~$
rd@Testing:~$ ls -l /
On Mon, Apr 19, 2021 at 06:48:41PM +0200, Rainer Dorsch wrote:
> Hello,
>
> I hit a strange emacs issue, which appeared after upgrading to bullseye (I
> think):
>
> I have a virtualbox filesystem mounted using the standard virtualbox
> mechanisms:
>
> rd@Testing:~$ mount |grep dor1rt
> dor1rt
17 matches
Mail list logo
