unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54084@debbugs.gnu.org
Subject: bug#54084: 28.0.91; Regression: can't create empty image buffer
Date: Mon, 21 Feb 2022 08:16:11 -0600	[thread overview]
Message-ID: <CAJf-WoQ27ccKyD-68eHQuWvDc3LZOHoNqXoYs1qnroqkYGA-Fg@mail.gmail.com> (raw)
In-Reply-To: <83mtikuxoz.fsf@gnu.org>

On Mon, Feb 21, 2022 at 8:00 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> [Please use Reply All, so that the bug tracker remains on the CC.]

Sorry about that.

> > From: Corwin Brust <corwin@bru.st>
> > Date: Mon, 21 Feb 2022 07:41:36 -0600
> >
> > Is there a way to disable this feature?
>
> Why is that needed?  Turning on image-mode in an empty buffer is a
> pretty strange thing to do, or at least a rare thing.

Noted, thanks.  FTR, for dungeon I have several modes that are derived
from image-mode, e.g. for displaying graphical character sheets,
combat status information, and maps.  I also have a point-and-click
drawing mode for creating/editing "tile-sets" and composing (e.g.)
maps for dungeon levels using these "named SVG fragments".

>
> Can't you use ignore-errors?
>
> How about delaying the mode switch until the user inserted something?

I will look into these options. (So far, the change you made seems to
have all my stuff working again per the release branch.)





      reply	other threads:[~2022-02-21 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21  8:21 bug#54084: 28.0.91; Regression: can't create empty image buffer Corwin Brust
2022-02-21 12:57 ` Eli Zaretskii
2022-02-21 13:58   ` Corwin Brust
2022-02-21 14:03     ` Eli Zaretskii
     [not found]   ` <CAJf-WoSU0e4dEmVTH=wxX5=UywqP0Vy7emhXqv4vXaKtVmPMFg@mail.gmail.com>
2022-02-21 14:00     ` Eli Zaretskii
2022-02-21 14:16       ` Corwin Brust [this message]

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=CAJf-WoQ27ccKyD-68eHQuWvDc3LZOHoNqXoYs1qnroqkYGA-Fg@mail.gmail.com \
    --to=corwin@bru.st \
    --cc=54084@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).