public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Renaming files with those pesky picture type characters.
Date: Tue, 29 Oct 2024 13:05:21 -0500	[thread overview]
Message-ID: <0c892dd0-a1d1-4372-ad62-a64cd751e270@gmail.com> (raw)
In-Reply-To: <2973073.e9J7NaK4W3@rogueboard>

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

Michael wrote:
> On Tuesday 29 October 2024 16:18:21 GMT Dale wrote:
>> Michael wrote:
>>> In a terminal running bash you can try:
>>>
>>> mv ./-ne.avi newname.avi
>>>
>>> or use a double dash to indicate end of options for the preceding command:
>>>
>>> mv -- -ne.avi newname.avi
>>>
>>> For a GUI-fied application, you can use 'kde-misc/krename'.
>> Now that is awesome.  The first one works great.  Haven't had the need
>> to try others yet but figure they would work too.  Finally, I can rename
>> these files with weird characters.  I never knew a -- meant end of
>> options before.  Been using Linux for a couple decades and never saw
>> that info. 
> I've seen it in the man pages of revdep-rebuild, perl-cleaner, et al. and have 
> been using it for a long time.  For example with revdep-rebuild I use it to 
> pass additional options to the emerge command, which is called from within 
> revdep-rebuild:
>
> revdep-rebuild -v -- -a
>
> This gives me a list and waits for my acknowledgement before it starts re-
> emerging any packages. 
>


I saw that but never understood what it did.  I thought it was something
that worked just with revdep-rebuild or something.  So it is a bash
thing.  Interesting.  That could open a can of worms. 

By the way, for giggles, I had a directory with several files with those
weird characters so I tried Krename.  I highlighted the files, opened
with Krename, no files detected.  For some reason, likely the same as
Frank's checksum tool, it can't process those files with weird
characters.  Could be a bug or just no way around it.  I'm not sure
Frank has found a workaround for his script yet either. 

I did add your command line methods to my cheat sheet tho.  Now if only
I can remember what I added them as so I can find it later.  o_O 

Dale

:-)  :-) 

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

  reply	other threads:[~2024-10-29 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 15:18 [gentoo-user] Renaming files with those pesky picture type characters Dale
2024-10-29 15:47 ` Michael
2024-10-29 16:18   ` Dale
2024-10-29 16:40     ` Michael
2024-10-29 18:05       ` Dale [this message]
2024-10-30  3:05         ` Eli Schwartz
2024-10-30 17:25           ` Dale
2024-11-01  2:25 ` Andrew Lowe
2024-11-01 14:16   ` Jack Ostroff
2024-11-01 16:02     ` Dale
2024-11-03 23:52 ` Wol

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=0c892dd0-a1d1-4372-ad62-a64cd751e270@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox