From: Yi Wang <tririverwangyi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13059@debbugs.gnu.org
Subject: bug#13059: frame-title does not update modified toggle on tmpfs
Date: Mon, 3 Dec 2012 07:59:38 +0900 [thread overview]
Message-ID: <CAJferG84FsRpeEQ2YOYDmxgxYSm0uQfqg90fWAsSE9JP9j3MqQ@mail.gmail.com> (raw)
In-Reply-To: <83txs4s3u6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
It sounds strange.
For me, this problem never happened on obscure then re-expose windows.
On the other hand, tmpfs should not be the reason either. The modified mark
fail to update at everywhere *except* for files in the home directory or
subdirectories of $HOME. For example, I tried /tmp, /var/tmp, a file
outside $HOME (while have edit permission), and use root to edit a file at
/. At all those positions I had this problem.
Best wishes,
Yi
On Mon, Dec 3, 2012 at 3:31 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 2 Dec 2012 17:51:26 +0900
> > From: Yi Wang <tririverwangyi@gmail.com>
> > Cc: Yi Wang <tririverwangyi@gmail.com>
> >
> > If I set frame-title as:
> >
> > (setq frame-title-format "%b %* ")
> >
> > The modified mark * will display correctly for normal files. But for
> files
> > in /tmp (where tmpfs is enabled), the modified mark almost never appears
> > (though actually buffer is modified).
>
> Does this happen only for tmpfs volumes?
>
> If you obscure the frame with some other window of another
> application, and then re-expose it again, does the modification
> indication gets updated?
>
[-- Attachment #2: Type: text/html, Size: 1685 bytes --]
next prev parent reply other threads:[~2012-12-02 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 8:51 bug#13059: frame-title does not update modified toggle on tmpfs Yi Wang
2012-12-02 18:31 ` Eli Zaretskii
2012-12-02 22:59 ` Yi Wang [this message]
2021-07-15 17:17 ` Lars Ingebrigtsen
2021-07-15 23:35 ` Yi Wang
2021-07-16 8:47 ` Lars Ingebrigtsen
2021-08-13 12:37 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJferG84FsRpeEQ2YOYDmxgxYSm0uQfqg90fWAsSE9JP9j3MqQ@mail.gmail.com \
--to=tririverwangyi@gmail.com \
--cc=13059@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).