unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tatsu Takamaro <tatsu.takamaro@gmail.com>
To: Manuel Giraud <manuel@ledu-giraud.fr>, Eli Zaretskii <eliz@gnu.org>
Cc: 74364@debbugs.gnu.org
Subject: bug#74364: Bug?
Date: Wed, 27 Nov 2024 17:16:03 +0300	[thread overview]
Message-ID: <06bfdebc-1dfb-bde2-f898-dc8f5cc36f87@gmail.com> (raw)
In-Reply-To: <87mshl4z0n.fsf@ledu-giraud.fr>

[-- Attachment #1: Type: text/plain, Size: 2615 bytes --]

I never use (in other situations and letters) the Reply to all button, 
so I may sometimes forget to press it instead of a usual answer. Sorry. 
But I'm trying ^_^

 >>Saving TUTORIAL is a strange thing to do. What is the purpose?

I suppose there are two main reasons:

1. Correcting mistakes. Eg. I saw "vv" on a new line where it was not 
supposed to be. Or there was a mistake in a "homework" section in the 
command, I don't remember where exectly.

2. Making notes for oneself. To explain something better (more clear to 
an exact learner).

*3. Or maybe even to argue. If I see some information which I completely 
disagree with, but I don't want to disturb the support team or waste 
time, I could just write a couple of sentences right in the Tutorial, 
kindof a comment, - and feel better ^_^


вт, 26.11.2024 21:43, Manuel Giraud пишет:
> Eli Zaretskii<eliz@gnu.org>  writes:
>
>>> 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.
> It seems that at some point of the tutorial, the user is expected to do
> it.
>
> [...]
>
>> 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.
> I could try to come up with a patch like this.

[-- Attachment #2: Type: text/html, Size: 4247 bytes --]

  reply	other threads:[~2024-11-27 14:16 UTC|newest]

Thread overview: 18+ 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
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 [this message]
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
2024-11-30 14:44                             ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 15:37                               ` 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=06bfdebc-1dfb-bde2-f898-dc8f5cc36f87@gmail.com \
    --to=tatsu.takamaro@gmail.com \
    --cc=74364@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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).