|
Re: TextEdit won't open a plain text file after writing to it with write cmd
OK, so those characters you see are what you need to use in «class utf8». When I change my system and keyboard to Russian, they are option-shift-+ and option-+.
--
Shane Stanley
OK, so those characters you see are what you need to use in «class utf8». When I change my system and keyboard to Russian, they are option-shift-+ and option-+.
--
Shane Stanley
|
By
Shane Stanley
·
#236
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
actually should've been «event misccurd» (auto-correction in action stood in the way)
18.06.2018, в 8:33, Shane Stanley написал(а):
actually should've been «event misccurd» (auto-correction in action stood in the way)
18.06.2018, в 8:33, Shane Stanley написал(а):
|
By
Ilya Shebalin
·
#235
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
current date compiles into «event miscued» in SD and my Mac is set to Russian as default language.
18.06.2018, в 8:33, Shane Stanley написал(а):
current date compiles into «event miscued» in SD and my Mac is set to Russian as default language.
18.06.2018, в 8:33, Shane Stanley написал(а):
|
By
Ilya Shebalin
·
#234
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
Type this into a Script Debugger window:
current date
Compile, then go to the View Menu and choose Show Raw (Chevron) Syntax, and compile again. What do you see now?
Also, what language is your
Type this into a Script Debugger window:
current date
Compile, then go to the View Menu and choose Show Raw (Chevron) Syntax, and compile again. What do you see now?
Also, what language is your
|
By
Shane Stanley
·
#233
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
Hello again, Shane
That's how the as "class utf8" compiles in ScriptDebugger:
«class as »:"class utf8"
18.06.2018, в 2:50, Shane Stanley написал(а):
Hello again, Shane
That's how the as "class utf8" compiles in ScriptDebugger:
«class as »:"class utf8"
18.06.2018, в 2:50, Shane Stanley написал(а):
|
By
Ilya Shebalin
·
#232
·
|
|
Re: drafting/prototyping code ?
HI Jean-Christophe,
I’d recommend yEd Graph Editor by yWorks <https://www.yworks.com/>.
It’s Java based and it’s free.
See the Gallery <https://www.yworks.com/products/yfiles/gallery> for
HI Jean-Christophe,
I’d recommend yEd Graph Editor by yWorks <https://www.yworks.com/>.
It’s Java based and it’s free.
See the Gallery <https://www.yworks.com/products/yfiles/gallery> for
|
By
Maik Waschfeld
·
#231
·
|
|
Re: Automator find and replace text string
Escaping/quoting is only required for the shell, so there's no reason for it to appear anywhere other than Terminal, bash scripts, and do shell script.
--
Shane Stanley
Escaping/quoting is only required for the shell, so there's no reason for it to appear anywhere other than Terminal, bash scripts, and do shell script.
--
Shane Stanley
|
By
Shane Stanley
·
#230
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
Go here and download a copy of Script Debugger: <https://latenightsw.com/sd7/download/>. Open one of your working scripts, then go to the View Menu and choose Show Raw (Chevron) Syntax. That should
Go here and download a copy of Script Debugger: <https://latenightsw.com/sd7/download/>. Open one of your working scripts, then go to the View Menu and choose Show Raw (Chevron) Syntax. That should
|
By
Shane Stanley
·
#229
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
I see the difference. I just have to figure out how to make quotes into as chevrons in precompiled AS code because my default locale is not en_EN. Maybe that's the cause of the error.
17.06.2018, в
I see the difference. I just have to figure out how to make quotes into as chevrons in precompiled AS code because my default locale is not en_EN. Maybe that's the cause of the error.
17.06.2018, в
|
By
Ilya Shebalin
·
#228
·
|
|
Re: Automator find and replace text string
Much obliged, Shane. Thx.
Much obliged, Shane. Thx.
|
By
Alastair Leith
·
#227
·
|
|
Re: Automator find and replace text string
That appeared in El Capitan.
FWIW, aside from the keyboard shortcut and the Edit view menu already mentioned, it is also available in a Finder window if you invoke the contextual menu on a selected
That appeared in El Capitan.
FWIW, aside from the keyboard shortcut and the Edit view menu already mentioned, it is also available in a Finder window if you invoke the contextual menu on a selected
|
By
2551phil
·
#226
·
|
|
Re: Automator find and replace text string
Thanks Steve! So cool, no escape chars either.
Thanks Steve! So cool, no escape chars either.
|
By
Alastair Leith
·
#225
·
|
|
Re: Automator find and replace text string
Seems like a bit of overkill for a simple literal replace.
tell application "Finder" to set finderSelectionList to selection as alias list
if length of finderSelectionList = 0 then error "No files
Seems like a bit of overkill for a simple literal replace.
tell application "Finder" to set finderSelectionList to selection as alias list
if length of finderSelectionList = 0 then error "No files
|
By
Shane Stanley
·
#224
·
|
|
Automator find and replace text string
Is there a basic find and replace text function in Automator? I can only find one for file name strings to use in the Finder (And I don’t want to change any file names, just copy their paths and
Is there a basic find and replace text function in Automator? I can only find one for file name strings to use in the Finder (And I don’t want to change any file names, just copy their paths and
|
By
Alastair Leith
·
#223
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
You're still using quote marks instead of chevrons -- they are not the same things.
write theText to FileID as «class utf8»
Can you see the difference?
--
Shane Stanley
You're still using quote marks instead of chevrons -- they are not the same things.
write theText to FileID as «class utf8»
Can you see the difference?
--
Shane Stanley
|
By
Shane Stanley
·
#222
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
Here's slightly modified the original 1st script:
#########The script No.1. I got the coercion error number -1700 ("couldn't coerce the_text to "class salc"")
property theText : ""
property theFile :
Here's slightly modified the original 1st script:
#########The script No.1. I got the coercion error number -1700 ("couldn't coerce the_text to "class salc"")
property theText : ""
property theFile :
|
By
Ilya Shebalin
·
#221
·
|
|
Re: drafting/prototyping code ?
Keynote is great for drawing programming flow type diagrams, there dedicated tools for this also, like Balsamiq, but I don't know of one other than Keynote that is free. Here's an example file from a
Keynote is great for drawing programming flow type diagrams, there dedicated tools for this also, like Balsamiq, but I don't know of one other than Keynote that is free. Here's an example file from a
|
By
Alastair Leith
·
#220
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
It seems you don't own me apology, Shane. My 1st script was butchered at some point missing some lines previously present perhaps because of numerous copy pastes between ScriptEditor and Mail messages
It seems you don't own me apology, Shane. My 1st script was butchered at some point missing some lines previously present perhaps because of numerous copy pastes between ScriptEditor and Mail messages
|
By
Ilya Shebalin
·
#219
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
My apologies -- I misread your code.
I'm still not sure what the problem was with «class utf8».
--
Shane Stanley <sstanley@...>
<www.macosxautomation.com/applescript/apps/>,
My apologies -- I misread your code.
I'm still not sure what the problem was with «class utf8».
--
Shane Stanley <sstanley@...>
<www.macosxautomation.com/applescript/apps/>,
|
By
Shane Stanley
·
#218
·
|
|
Re: TextEdit won't open a plain text file after writing to it with write cmd
I'm not sure I can interpret your response correctly. The second script is a tad modified version of the 1st one. On the very 1st run it creates a new text doc, on every consecutive one it offers 2
I'm not sure I can interpret your response correctly. The second script is a tad modified version of the 1st one. On the very 1st run it creates a new text doc, on every consecutive one it offers 2
|
By
Ilya Shebalin
·
#217
·
|