unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 74364@debbugs.gnu.org, tatsu.takamaro@gmail.com
Subject: bug#74364: Bug?
Date: Tue, 26 Nov 2024 14:51:14 +0200	[thread overview]
Message-ID: <86seregnul.fsf@gnu.org> (raw)
In-Reply-To: <87iksb6see.fsf@ledu-giraud.fr> (bug-gnu-emacs@gnu.org)

> Cc: 74364@debbugs.gnu.org
> Date: Mon, 25 Nov 2024 20:10:49 +0100
> From:  Manuel Giraud via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Tatsu Takamaro <tatsu.takamaro@gmail.com> writes:
> 
> [...]
> 
> Ok, now your recipe is more precise and I can reproduce it.
> 
> > 3. Put some changes into the Tutorial. Say, just add a new line.
> >
> > 4. Press C-x-s to save. Emacs asks me to write a filename, I write
> > TUTORIAL, because the full path is alredy shown. Then Emacs asks me
> > whether I want to overwrite the file. I anser Yes (type y).
> 
> After this 'C-x C-s', you have saved the content of the (modified)
> TUTORIAL into a file named "TUTORIAL" somewhere on your hard drive.
> Now, in this buffer, `tutorial--lang' is set to nil (which cause the
> error you saw) and Emacs still wants to save your progression in the
> tutorial and that's why it asks the question when you tried to quit.
> 
> This is indeed a bug but maybe saving the TUTORIAL buffer is not
> supported.  Or we should remap `save-buffer' to save tutorial
> progression here?

Saving TUTORIAL is a strange thing to do.  What is the purpose?  The
file produced that way cannot be used as a tutorial, AFAIU, because
Emacs doesn't let users specify the tutorial's file name.

Users are supposed to save tutorial by killing the buffer or exiting
Emacs, in which case Emacs saves the tutorial state as it should be.

So my suggestion would be to modify tutorial--save-tutorial and
tutorial--save-on-kill such that of tutorial--lang is nil, they will
do nothing.  Because there's no point of trying to save the tutorial
in that case.





  reply	other threads:[~2024-11-26 12:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15  4:53 bug#74364: Bug? Tatsu Takamaro
2024-11-15  7:18 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <3ffa9049-44a1-8a88-69aa-6a7b1d5dabee@gmail.com>
2024-11-18  9:10     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19  8:50       ` Tatsu Takamaro
2024-11-19 14:23         ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23  6:44           ` Tatsu Takamaro
2024-11-23 10:50             ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-25  8:21               ` Tatsu Takamaro
2024-11-25 19:10                 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-26 12:51                   ` Eli Zaretskii [this message]
2024-11-26 18:43                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-27 14:16                       ` Tatsu Takamaro
2024-11-27 14:18                       ` Eli Zaretskii
2024-11-29 15:46                         ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 11:05                           ` Eli Zaretskii
     [not found]                   ` <ab77c50d-6db1-b143-78cf-191c19585280@gmail.com>
2024-11-26 13:11                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86seregnul.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74364@debbugs.gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=tatsu.takamaro@gmail.com \
    /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).