Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #118085 > unrolled thread
| Started by | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| First post | 2018-09-11 13:37 -0400 |
| Last post | 2018-09-12 08:50 +1200 |
| Articles | 20 on this page of 27 — 8 participants |
Back to article view | Back to comp.sys.mac.system
Selective rennaming of extension JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-09-11 13:37 -0400
Re: Selective rennaming of extension nospam <nospam@nospam.invalid> - 2018-09-11 13:50 -0400
Re: Selective rennaming of extension JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-09-11 13:56 -0400
Re: Selective rennaming of extension nospam <nospam@nospam.invalid> - 2018-09-11 14:03 -0400
Re: Selective rennaming of extension Your Name <YourName@YourISP.com> - 2018-09-12 09:02 +1200
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-11 14:10 -0700
Re: Selective rennaming of extension Jolly Roger <jollyroger@pobox.com> - 2018-09-11 22:21 +0000
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-11 15:27 -0700
Re: Selective rennaming of extension Your Name <YourName@YourISP.com> - 2018-09-12 13:51 +1200
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-11 18:58 -0700
Re: Selective rennaming of extension Jolly Roger <jollyroger@pobox.com> - 2018-09-13 15:15 +0000
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-13 08:18 -0700
Re: Selective rennaming of extension JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-09-12 13:42 -0400
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-12 10:43 -0700
Re: Selective rennaming of extension Jolly Roger <jollyroger@pobox.com> - 2018-09-13 15:16 +0000
Re: Selective rennaming of extension Elden <usenet@moondog.org> - 2018-09-11 18:39 -0700
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-11 18:44 -0700
Re: Selective rennaming of extension Your Name <YourName@YourISP.com> - 2018-09-12 18:15 +1200
Re: Selective rennaming of extension nmassello@yahoo.com (Neill Massello) - 2018-09-12 14:14 -0600
Re: Selective rennaming of extension Your Name <YourName@YourISP.com> - 2018-09-12 13:52 +1200
Re: Selective rennaming of extension Jolly Roger <jollyroger@pobox.com> - 2018-09-11 18:17 +0000
Re: Selective rennaming of extension JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-09-11 15:32 -0400
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-11 12:36 -0700
Re: Selective rennaming of extension Jolly Roger <jollyroger@pobox.com> - 2018-09-11 22:18 +0000
Re: Selective rennaming of extension Lewis <g.kreme@gmail.com.dontsendmecopies> - 2018-09-12 08:23 +0000
Re: Selective rennaming of extension Alan Baker <nunya@ness.biz> - 2018-09-12 08:45 -0700
Re: Selective rennaming of extension Your Name <YourName@YourISP.com> - 2018-09-12 08:50 +1200
Page 1 of 2 [1] 2 Next page →
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2018-09-11 13:37 -0400 |
| Subject | Selective rennaming of extension |
| Message-ID | <e3TlD.36496$cL2.3015@fx43.iad> |
I get a folder (from a .zip) full of files such as: > DM#3206078 - Réponse-Response - 180910-Bell Mobility-CRTC-20Jul18-307 TNC 2018-98.doc or > DM#3206146 - Réponse-Response - TELUS(CRTC)20July18-205.pdf There are about a hundred files At the gui level, is there a way to select all the Bell Mobility files and changing then from .doc to .docx so the Mac can quicklook or "Preview" of "Pages" can open them ? At Command line: With VMS, I could have done rename *Bell*.doc .docx is there a simple bash way to achieve this? Last time I tried it required I loop through each file, remove everything after the last dot, and rename it with the filename part just extracted and hardcoding the "docx" at end. Alternatively, is there a way to configure the mac to treat ".doc" documents as ".docx" so the same application (Preview, Pages) will accept them ?
[toc] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2018-09-11 13:50 -0400 |
| Message-ID | <110920181350372112%nospam@nospam.invalid> |
| In reply to | #118085 |
In article <e3TlD.36496$cL2.3015@fx43.iad>, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > At the gui level, is there a way to select all the Bell Mobility files > and changing then from .doc to .docx so the Mac can quicklook or > "Preview" of "Pages" can open them ? that's a bad idea, since doc and docx are different formats, and it should be able to quicklook it without doing anything. > > Alternatively, is there a way to configure the mac to treat ".doc" > documents as ".docx" so the same application (Preview, Pages) will > accept them ? select one file, get info in finder, then choose the desired app in the open with panel and click the change all... button.
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2018-09-11 13:56 -0400 |
| Message-ID | <7lTlD.29011$nH2.17815@fx26.iad> |
| In reply to | #118086 |
On 2018-09-11 13:50, nospam wrote: > that's a bad idea, since doc and docx are different formats, and it > should be able to quicklook it without doing anything. Incumbent telcos and/or the CRTC feed us .docx file formats as .doc files. > select one file, get info in finder, then choose the desired app in the > open with panel and click the change all... button. the .doc and .docx are opened by the right apps. It is the app itself which complains about not being able to parse .doc file, but when you rename file to .docx, the same app pens it nicely. So this isn't a question of associating a different app to a file expension, it is a question of telling apps such as Preview and Pages to treat .doc as .docx if .doc parsing fails.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2018-09-11 14:03 -0400 |
| Message-ID | <110920181403137514%nospam@nospam.invalid> |
| In reply to | #118087 |
In article <7lTlD.29011$nH2.17815@fx26.iad>, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > > that's a bad idea, since doc and docx are different formats, and it > > should be able to quicklook it without doing anything. > > Incumbent telcos and/or the CRTC feed us .docx file formats as .doc files. they're incompetent. > > select one file, get info in finder, then choose the desired app in the > > open with panel and click the change all... button. > > the .doc and .docx are opened by the right apps. It is the app itself > which complains about not being able to parse .doc file, but when you > rename file to .docx, the same app pens it nicely. > > So this isn't a question of associating a different app to a file > expension, it is a question of telling apps such as Preview and Pages to > treat .doc as .docx if .doc parsing fails. no, it's a question of getting them to send you valid files.
[toc] | [prev] | [next] | [standalone]
| From | Your Name <YourName@YourISP.com> |
|---|---|
| Date | 2018-09-12 09:02 +1200 |
| Message-ID | <pn9ahl$2te$1@gioia.aioe.org> |
| In reply to | #118087 |
On 2018-09-11 17:56:18 +0000, JF Mezei said: > On 2018-09-11 13:50, nospam wrote: >> >> that's a bad idea, since doc and docx are different formats, and it >> should be able to quicklook it without doing anything. > > Incumbent telcos and/or the CRTC feed us .docx file formats as .doc files. You need a better service provider with software isn't still stuck in the 1980s thinking files only have three letter filename extensions. >> select one file, get info in finder, then choose the desired app in the >> open with panel and click the change all... button. > > the .doc and .docx are opened by the right apps. It is the app itself > which complains about not being able to parse .doc file, but when you > rename file to .docx, the same app pens it nicely. > > So this isn't a question of associating a different app to a file > expension, it is a question of telling apps such as Preview and Pages to > treat .doc as .docx if .doc parsing fails. You might be able to do it using A Better Finder Rename. <http://www.publicspace.net/ABetterFinderRename/> Automator should be able to do it. Via Folder Actions you could set it up to "watch" a folder and automatically change the .doc to .docx. There are also a couple of 'butler' apps which will also do watch folder changes, but I can't recall the names at the moment. *BUT* the problem with any automated method will be files that truly are .doc format which you don't want to be changed. You would need something that can look inside the file to check which format it actually is before renaming the ones that do need to be done.
[toc] | [prev] | [next] | [standalone]
| From | Alan Baker <nunya@ness.biz> |
|---|---|
| Date | 2018-09-11 14:10 -0700 |
| Message-ID | <pn9b08$3pe$1@gioia.aioe.org> |
| In reply to | #118095 |
On 2018-09-11 2:02 PM, Your Name wrote: > On 2018-09-11 17:56:18 +0000, JF Mezei said: >> On 2018-09-11 13:50, nospam wrote: >>> >>> that's a bad idea, since doc and docx are different formats, and it >>> should be able to quicklook it without doing anything. >> >> Incumbent telcos and/or the CRTC feed us .docx file formats as .doc >> files. > > You need a better service provider with software isn't still stuck in > the 1980s thinking files only have three letter filename extensions. > > > >>> select one file, get info in finder, then choose the desired app in the >>> open with panel and click the change all... button. >> >> the .doc and .docx are opened by the right apps. It is the app itself >> which complains about not being able to parse .doc file, but when you >> rename file to .docx, the same app pens it nicely. >> >> So this isn't a question of associating a different app to a file >> expension, it is a question of telling apps such as Preview and Pages to >> treat .doc as .docx if .doc parsing fails. > > You might be able to do it using A Better Finder Rename. > <http://www.publicspace.net/ABetterFinderRename/> > > Automator should be able to do it. Via Folder Actions you could set it > up to "watch" a folder and automatically change the .doc to .docx. > > There are also a couple of 'butler' apps which will also do watch folder > changes, but I can't recall the names at the moment. > > *BUT* > the problem with any automated method will be files that truly are .doc > format which you don't want to be changed. You would need something that > can look inside the file to check which format it actually is before > renaming the ones that do need to be done. > > I think you'll find you're completely wrong about the idea that changing the extension of any file will bother the originating software in the least. As you point out, you need something that looks inside the file to see what format is really being used, and there already is something: The application that opens the file. I just took a file I KNEW to be in the newer, ".docx" format and switched it's extension to ".doc". Word opened it just fine. So the only issue is for him in this case is that when a file has the ".doc" extension, the QuickLook system fails to display its contents.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2018-09-11 22:21 +0000 |
| Message-ID | <fvqtetFu48vU2@mid.individual.net> |
| In reply to | #118096 |
On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: > > So the only issue is for him in this case is that when a file has the > ".doc" extension, the QuickLook system fails to display its contents. That's a problem he seemingly created by renaming XML format Word documents with the incorrect ".doc" extension though. I just checked and QuickLook will display XML format Word documents with the correct ".docx" filename extension without issue. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Alan Baker <nunya@ness.biz> |
|---|---|
| Date | 2018-09-11 15:27 -0700 |
| Message-ID | <pn9fgi$apl$1@gioia.aioe.org> |
| In reply to | #118103 |
On 2018-09-11 3:21 PM, Jolly Roger wrote: > On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: >> >> So the only issue is for him in this case is that when a file has the >> ".doc" extension, the QuickLook system fails to display its contents. > > That's a problem he seemingly created by renaming XML format Word > documents with the incorrect ".doc" extension though. I just checked and > QuickLook will display XML format Word documents with the correct > ".docx" filename extension without issue. > But you've got it backwards: 'At the gui level, is there a way to select all the Bell Mobility files and changing then from .doc to .docx so the Mac can quicklook or "Preview" of "Pages" can open them ?' He's receiving Word files with a ".doc" extension that are actually in DOCX format. I've tested this. A file that works perfectly in QuickLook when it has a ".docx" extension fails when you change the extension to ".doc". Hence his desire to a bulk change.
[toc] | [prev] | [next] | [standalone]
| From | Your Name <YourName@YourISP.com> |
|---|---|
| Date | 2018-09-12 13:51 +1200 |
| Message-ID | <pn9rfl$qah$1@gioia.aioe.org> |
| In reply to | #118104 |
On 2018-09-11 22:27:31 +0000, Alan Baker said: > On 2018-09-11 3:21 PM, Jolly Roger wrote: >> On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: >>> >>> So the only issue is for him in this case is that when a file has the >>> ".doc" extension, the QuickLook system fails to display its contents. >> >> That's a problem he seemingly created by renaming XML format Word >> documents with the incorrect ".doc" extension though. I just checked and >> QuickLook will display XML format Word documents with the correct >> ".docx" filename extension without issue. > > But you've got it backwards: > > 'At the gui level, is there a way to select all the Bell Mobility files > and changing then from .doc to .docx so the Mac can quicklook or > "Preview" of "Pages" can open them ?' > > He's receiving Word files with a ".doc" extension that are actually in > DOCX format. > > I've tested this. A file that works perfectly in QuickLook when it has > a ".docx" extension fails when you change the extension to ".doc". > > Hence his desire to a bulk change. QuickLook also fails the other way around ... renaming a .doc to .docx So batch renaming all .doc to .docx isn't really a solution unless you know exactly what type of file it really is.
[toc] | [prev] | [next] | [standalone]
| From | Alan Baker <nunya@ness.biz> |
|---|---|
| Date | 2018-09-11 18:58 -0700 |
| Message-ID | <pn9rs3$qn6$1@gioia.aioe.org> |
| In reply to | #118112 |
On 2018-09-11 6:51 PM, Your Name wrote: > On 2018-09-11 22:27:31 +0000, Alan Baker said: >> On 2018-09-11 3:21 PM, Jolly Roger wrote: >>> On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: >>>> >>>> So the only issue is for him in this case is that when a file has the >>>> ".doc" extension, the QuickLook system fails to display its contents. >>> >>> That's a problem he seemingly created by renaming XML format Word >>> documents with the incorrect ".doc" extension though. I just checked and >>> QuickLook will display XML format Word documents with the correct >>> ".docx" filename extension without issue. >> >> But you've got it backwards: >> >> 'At the gui level, is there a way to select all the Bell Mobility files >> and changing then from .doc to .docx so the Mac can quicklook or >> "Preview" of "Pages" can open them ?' >> >> He's receiving Word files with a ".doc" extension that are actually in >> DOCX format. >> >> I've tested this. A file that works perfectly in QuickLook when it has >> a ".docx" extension fails when you change the extension to ".doc". >> >> Hence his desire to a bulk change. > > QuickLook also fails the other way around ... renaming a .doc to .docx > > So batch renaming all .doc to .docx isn't really a solution unless you > know exactly what type of file it really is. > That's true, but if he knows his source is sending him docx format files only, then he doesn't need to check until QuickLook gives him a problem.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2018-09-13 15:15 +0000 |
| Message-ID | <fvvd83FrlhbU2@mid.individual.net> |
| In reply to | #118104 |
On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: > On 2018-09-11 3:21 PM, Jolly Roger wrote: >> On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: >>> >>> So the only issue is for him in this case is that when a file has the >>> ".doc" extension, the QuickLook system fails to display its contents. >> >> That's a problem he seemingly created by renaming XML format Word >> documents with the incorrect ".doc" extension though. I just checked and >> QuickLook will display XML format Word documents with the correct >> ".docx" filename extension without issue. > > But you've got it backwards: > > 'At the gui level, is there a way to select all the Bell Mobility files > and changing then from .doc to .docx so the Mac can quicklook or > "Preview" of "Pages" can open them ?' > > He's receiving Word files with a ".doc" extension that are actually in > DOCX format. > > I've tested this. A file that works perfectly in QuickLook when it has a > ".docx" extension fails when you change the extension to ".doc". > > Hence his desire to a bulk change. Then correcting the filenames should fix the problem. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Alan Baker <nunya@ness.biz> |
|---|---|
| Date | 2018-09-13 08:18 -0700 |
| Message-ID | <pndv3o$1mqi$1@gioia.aioe.org> |
| In reply to | #118133 |
On 2018-09-13 8:15 AM, Jolly Roger wrote: > On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: >> On 2018-09-11 3:21 PM, Jolly Roger wrote: >>> On 2018-09-11, Alan Baker <nunya@ness.biz> wrote: >>>> >>>> So the only issue is for him in this case is that when a file has the >>>> ".doc" extension, the QuickLook system fails to display its contents. >>> >>> That's a problem he seemingly created by renaming XML format Word >>> documents with the incorrect ".doc" extension though. I just checked and >>> QuickLook will display XML format Word documents with the correct >>> ".docx" filename extension without issue. >> >> But you've got it backwards: >> >> 'At the gui level, is there a way to select all the Bell Mobility files >> and changing then from .doc to .docx so the Mac can quicklook or >> "Preview" of "Pages" can open them ?' >> >> He's receiving Word files with a ".doc" extension that are actually in >> DOCX format. >> >> I've tested this. A file that works perfectly in QuickLook when it has a >> ".docx" extension fails when you change the extension to ".doc". >> >> Hence his desire to a bulk change. > > Then correcting the filenames should fix the problem. > Yes. It should. :-)
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2018-09-12 13:42 -0400 |
| Message-ID | <AecmD.19637$ZJ2.15026@fx33.iad> |
| In reply to | #118103 |
On 2018-09-11 18:21, Jolly Roger wrote: > That's a problem he seemingly created by renaming XML format Word > documents with the incorrect ".doc" extension though. I just checked and > QuickLook will display XML format Word documents with the correct > ".docx" filename extension without issue. It appears that in the Microsoft world, the software will open the .doc file whethert its content are legacy word or current .xml and it creates .doc file instead of .docx since it assumes software that opens such files is able to automatically switch between legacy and XML file formats when opening .doc On the mac howeve, Quicklook, Pages and Preview doesn't have this ability and it will only scan for legalcy format in .doc and only scan for XML content in .docx, even when both file extensions point to the same software.
[toc] | [prev] | [next] | [standalone]
| From | Alan Baker <nunya@ness.biz> |
|---|---|
| Date | 2018-09-12 10:43 -0700 |
| Message-ID | <pnbj8p$1nl7$1@gioia.aioe.org> |
| In reply to | #118123 |
On 2018-09-12 10:42 AM, JF Mezei wrote: > On 2018-09-11 18:21, Jolly Roger wrote: > >> That's a problem he seemingly created by renaming XML format Word >> documents with the incorrect ".doc" extension though. I just checked and >> QuickLook will display XML format Word documents with the correct >> ".docx" filename extension without issue. > > It appears that in the Microsoft world, the software will open the .doc > file whethert its content are legacy word or current .xml and it creates > .doc file instead of .docx since it assumes software that opens such > files is able to automatically switch between legacy and XML file > formats when opening .doc You're making some huge assumptions there that really aren't warranted. > > On the mac howeve, Quicklook, Pages and Preview doesn't have this > ability and it will only scan for legalcy format in .doc and only scan > for XML content in .docx, even when both file extensions point to the > same software. >
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2018-09-13 15:16 +0000 |
| Message-ID | <fvvd9gFrlhbU3@mid.individual.net> |
| In reply to | #118123 |
On 2018-09-12, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > On 2018-09-11 18:21, Jolly Roger wrote: > >> That's a problem he seemingly created by renaming XML format Word >> documents with the incorrect ".doc" extension though. I just checked and >> QuickLook will display XML format Word documents with the correct >> ".docx" filename extension without issue. > > It appears that in the Microsoft world, the software will open the .doc > file whethert its content are legacy word or current .xml and it creates > .doc file instead of .docx since it assumes software that opens such > files is able to automatically switch between legacy and XML file > formats when opening .doc > > On the mac howeve, Quicklook, Pages and Preview doesn't have this > ability and it will only scan for legalcy format in .doc and only scan > for XML content in .docx, even when both file extensions point to the > same software. So fix the filenames. Problem solved. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Elden <usenet@moondog.org> |
|---|---|
| Date | 2018-09-11 18:39 -0700 |
| Message-ID | <qgrgpdh3ru3pa5bbdt773tta8kr3s0pb02@4ax.com> |
| In reply to | #118095 |
On Wed, 12 Sep 2018 09:02:47 +1200, Your Name <YourName@YourISP.com> wrote: >There are also a couple of 'butler' apps which will also do watch >folder changes, but I can't recall the names at the moment. Hazel is pretty good. -- -=Elden=-
[toc] | [prev] | [next] | [standalone]
| From | Alan Baker <nunya@ness.biz> |
|---|---|
| Date | 2018-09-11 18:44 -0700 |
| Message-ID | <pn9r2f$pl7$5@gioia.aioe.org> |
| In reply to | #118107 |
On 2018-09-11 6:39 PM, Elden wrote: > On Wed, 12 Sep 2018 09:02:47 +1200, Your Name <YourName@YourISP.com> > wrote: > >> There are also a couple of 'butler' apps which will also do watch >> folder changes, but I can't recall the names at the moment. > > Hazel is pretty good. > It's built in these days, folks.
[toc] | [prev] | [next] | [standalone]
| From | Your Name <YourName@YourISP.com> |
|---|---|
| Date | 2018-09-12 18:15 +1200 |
| Message-ID | <pnaaut$1ekm$1@gioia.aioe.org> |
| In reply to | #118108 |
On 2018-09-12 01:44:49 +0000, Alan Baker said: > On 2018-09-11 6:39 PM, Elden wrote: >> On Wed, 12 Sep 2018 09:02:47 +1200, Your Name <YourName@YourISP.com> >> wrote: >>> >>> There are also a couple of 'butler' apps which will also do watch >>> folder changes, but I can't recall the names at the moment. >> >> Hazel is pretty good. > > It's built in these days, folks. The Finder's built in file renaming options are extremely limited. Apps like 'Hazel' and 'A Better Finder Rename' are massively more flexible (perhaps too much so for some people). Technically you probably could re-create much, if not all, of what these apps can do using AppleScript / Automator, but why bother re-inventing the wheel?
[toc] | [prev] | [next] | [standalone]
| From | nmassello@yahoo.com (Neill Massello) |
|---|---|
| Date | 2018-09-12 14:14 -0600 |
| Message-ID | <1nv0pv3.1obur4q1b5jb3dN%nmassello@yahoo.com> |
| In reply to | #118116 |
Your Name <YourName@YourISP.com> wrote: > The Finder's built in file renaming options are extremely limited. Apps > like 'Hazel' and 'A Better Finder Rename' are massively more flexible > (perhaps too much so for some people). Technically you probably could > re-create much, if not all, of what these apps can do using AppleScript > / Automator, but why bother re-inventing the wheel? Hazel is quite good for automatic renaming. Of the non-automated GUI apps, my favorite is Name Mangler. <https://manytricks.com/namemangler/>
[toc] | [prev] | [next] | [standalone]
| From | Your Name <YourName@YourISP.com> |
|---|---|
| Date | 2018-09-12 13:52 +1200 |
| Message-ID | <pn9rhc$qah$2@gioia.aioe.org> |
| In reply to | #118107 |
On 2018-09-12 01:39:11 +0000, Elden said: > On Wed, 12 Sep 2018 09:02:47 +1200, Your Name <YourName@YourISP.com> > wrote: >> >> There are also a couple of 'butler' apps which will also do watch >> folder changes, but I can't recall the names at the moment. > > Hazel is pretty good. Yep, Hazel is one I was thinking of, thanks.
[toc] | [prev] | [next] | [standalone]
Page 1 of 2 [1] 2 Next page →
Back to top | Article view | comp.sys.mac.system
csiph-web