bug#52926: closed (dired-copy-filename-as-kill should beep if not on a file line)

[GNU bug Tracking System]

Your message dated Sat, 01 Jan 2022 09:17:13 +0200
with message-id <83r19sexhi.fsf@gnu.org>
and subject line Re: bug#52926: dired-copy-filename-as-kill should beep if not 
on a file line
has caused the debbugs.gnu.org bug report #52926,
regarding dired-copy-filename-as-kill should beep if not on a file line
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
52926: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52926
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> dired-copy-filename-as-kill should beep if not on a file line
>
>
>
>
> Date: 
>
> Sat, 01 Jan 2022 11:24:25 +0800
>
>
>
>
> w runs the command dired-copy-filename-as-kill.
> But if it is not on a filename, e.g., on the "total" line,
> or on the line at the end of the buffer with no file on it,
> it should beep.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#52926: dired-copy-filename-as-kill should beep if not on a file line
>
>
>
>
> Date: 
>
> Sat, 01 Jan 2022 09:17:13 +0200
>
>
>
>
> > From: 積丹尼 Dan Jacobson
> >  <jidanni@jidanni.org>
> > Date: Sat, 01 Jan 2022 11:24:25 +0800
> > 
> > w runs the command dired-copy-filename-as-kill.
> > But if it is not on a filename, e.g., on the "total" line,
> > or on the line at the end of the buffer with no file on it,
> > it should beep.
>
> Why beep?  It does a useful job in that case as well.
>
> Closing.
>
>
> --- End Message ---