all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: emacs-devel@gnu.org
Subject: Re: emacs/etc/images/gud record-start.xpm record-st...	[EMACS_23_1_RC]
Date: Sat, 08 Aug 2009 15:35:03 +0300	[thread overview]
Message-ID: <833a82mqko.fsf@gnu.org> (raw)
In-Reply-To: <19069.21090.619045.22938@totara.tehura.co.nz>

> Date: Sat, 8 Aug 2009 22:24:34 +1200
> Cc: rgm@gnu.org, emacs-devel@gnu.org
> From: nickrob@snap.net.nz (Nick Roberts)
> 
>  > Can we please rename them to something that doesn't have this problem,
>  > like recstart.xpm, recstop.xpm, rev-continue.xpm, etc.?
> 
> Does rev-continue.xpm work with 8+3 DOS file names?  I thought it meant the
> basename had only 8 characters (rev-continue has 12?).

No, the requirement is to have them _unique_ in the 8+3 characters.
Thus, rev-continue.xpm gets truncated to rev-cont.xpm, and if no other
file gets truncated to the same 8+3 name, it's fine.

The DOS port of Emacs does not support images, so these files won't be
used there, we just need to avoid problems when unpacking the tarball.
But even if Emacs did use these files on DOS, the filesystem calls
transparently truncate the file names to 8+3 limits, and will happily
resolve rev-continue.xpm to an existing rev-cont.xpm.

> I'm willing to do it and I would probably use the names in gud.el:
> recstart, recstop, rnext, rnexti, rstep, rstepi, rfinish, rcont.
> Are these okay?

Yes, they are okay.

Thanks.




      reply	other threads:[~2009-08-08 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1MYxnw-0000z2-Lk@cvs.savannah.gnu.org>
2009-08-07 19:09 ` emacs/etc/images/gud record-start.xpm record-st... [EMACS_23_1_RC] Glenn Morris
2009-08-08  5:00   ` Nick Roberts
2009-08-08  8:34     ` Eli Zaretskii
2009-08-08 10:24       ` Nick Roberts
2009-08-08 12:35         ` Eli Zaretskii [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=833a82mqko.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.