Groups > comp.sys.mac.apps > #28976 > unrolled thread

How do mac users create a blank text file where you want it?

Started by	"Adam H. Kerman" <ahk@chinet.com>
First post	2015-04-20 00:40 +0000
Last post	2015-04-22 09:45 -0400
Articles	20 on this page of 393 — 26 participants

Back to article view | Back to comp.sys.mac.apps

Page 19 of 20 — ← Prev page 1 … 17 18 [19] 20 Next page →

#29380

From	Alan Baker <email@domain.com>
Date	2015-04-22 12:12 -0700
Message-ID	<mh8rr2$4l4$2@news.datemas.de>
In reply to	#29142

On 2015-04-20 07:04:40 +0000, Adam H. Kerman said:

> nospam <nospam@nospam.invalid> wrote in message
> 190420152338587793nospamospam@nospam.invalid
> 
>> *one* app doesn't have it in the save panel.
>> 
>> what other apps do is likely to be different.
> 
> I do agree that every app can be different.
> I'm *only* speaking about the default text editor in this thread.

There really isn't a default text editor on the Mac. There is a text 
editor it happens to have included.

> Certainly, I had *expected* a default text editor to be able to "save as"
> plain text, so it was a shocker that you have to find the plain text
> option in a different menu sequence.

[toc] | [prev] | [next] | [standalone]

#29117

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-20 04:10 +0000
Message-ID	<cpjci6F7dq8U2@mid.individual.net>
In reply to	#29033

On 2015-04-20, Adam H. Kerman <ahk@chinet.com> wrote:
> Jolly Roger <jollyroger@pobox.com> wrote in message
> cpj6g3F5p92U5@mid.individual.net
>
>> 1. Open TextEdit.
>> 2. Change Preferences > New Document > Format: Plain text.
>
> Thanks. 
>
> Only nospam, up to your post above, had actually explained *how* 
> to unhide the hidden option for the default text editor to save as 
> portable ASCII text files.

Bullshit. You ignored other responses that told you how to do it.

> Now everything is fine.

Not really. You changed preferences on a machine that is not yours. I
told you a simpler and better way but you ignored it.

> What I learned was two important things about Macintosh protocols.

You haven't learned anything at all.

> 1. In most operating system, you have a variety of options of how you 
>    want to create your ASCII text files but on the Macintosh, one of
>    those options doesn't exist.

Bullshit. 

> 2. In most default text editors (on other operating systems), you can
>    immediately save the file as ASCII text but on the Macintosh, you
>    have to know to first unhide the hidden option to save ASCII text
>    as ASCII text (because the default text editor defaults to RTL).

That's a lie.

> Thanks for helping me understand how mac users create text files.

You understand nothing, troll.

-- 
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]

#28996

From	nospam <nospam@nospam.invalid>
Date	2015-04-19 22:28 -0400
Message-ID	<190420152228173386%nospam@nospam.invalid>
In reply to	#28982

In article <mh1nul$3dm$6@news.albasani.net>, Adam H. Kerman
<ahk@chinet.com> wrote:

> Which of these TextEdit "Save As" options is the ASCII text option 

its not in save as. pay attention. you set the app to plain text in the
app and then it will save plain text.

and don't even waste your time with text edit. get text wrangler. 

<http://www.barebones.com/products/textwrangler/>

[toc] | [prev] | [next] | [standalone]

#29034

From	"Adam H. Kerman" <ahk@chinet.com>
Date	2015-04-20 03:25 +0000
Message-ID	<mh1ris$i5o$3@news.albasani.net>
In reply to	#28996

nospam <nospam@nospam.invalid> wrote in message
190420152228173386nospamospam@nospam.invalid

> its not in save as. pay attention. you set the app to plain text in the
> app and then it will save plain text.

I don't have the Macintosh in front of me now, as the person who was 
asking for help went home, but I will need to check tomorrow if unhiding
the hidden option for the default text editor to save ASCII text actually
disabled the Save As dialog by mistake.

Thanks for that warning. I'll have to check tomorrow to see if there is
still the option to Save As, or if that option now disappears.

[toc] | [prev] | [next] | [standalone]

#29000

From	"Adam H. Kerman" <ahk@chinet.com>
Date	2015-04-20 02:23 +0000
Message-ID	<mh1nul$3dm$6@news.albasani.net>
In reply to	#28982

Jolly Roger <jollyroger@pobox.com> wrote in message
cpj4o2F5p92U1@mid.individual.net
 
> 1. Open TextEdit (or any text editor).
> 2. Save the file wherever you want it.
> 3. There is no step 3.

Which of these TextEdit "Save As" options is the ASCII text option 
(so that I can save the file as a portable filename.txt)?
http://i.imgur.com/FDYa45h.png

[toc] | [prev] | [next] | [standalone]

#29035

From	David Ritz <dritz@mindspring.com>
Date	2015-04-19 22:10 -0500
Message-ID	<alpine.OSX.2.20.1504192135570.57809@mako.ath.cx>
In reply to	#28976

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Monday, 20 April 2015 00:40 -0000, 
 in article <mh1htc$3dm$2@news.albasani.net>, 
 Adam H. Kerman <ahk@chinet.com> wrote:

> Since the Mac is different from what I am used to, I am sure I am 
> doing something very wrong since it can't be this complex to do 
> something as simple as create an empty text file where you want it 
> to exist with a file name that indicates it's a text file.

It's quite easy, actually.

> Given the simple goal of 
> a) Creating a blank text file
> b) In a desired location
> c) With some indication that it's a text file
> How would a Mac user have done this task?

The easiest way I can come up with, to create a new text file, in the 
directory of your choice, is via Terminal application, found in 
/Applications/Utilities/.  To create the file, type

    touch /full/path/to/file.txt

 $ touch ~/Desktop/file.txt

 $ ls -alF ~/Desktop/file.txt
 -rw-r--r--+ 1 dritz  staff  0 Apr 19 21:42 /Users/dritz/Desktop/file.txt

 $ file /Users/dritz/Desktop/file.txt
 /Users/dritz/Desktop/file.txt: empty

Is that empty enough for you, Adam?

Optionally, a Mac user might launch whatever text editor they're 
using, create a new document within the application and save it to 
disk, wherever you want it to exist, within the Save dialog.  Common 
GUI Mac text editors include TextWrangler (free) and BBEdit (paid), 
both from Bare Bones Software.  Common CLI text editors, found in a 
default Mac installation include ed, vi (asiased to vim), nano and 
emacs, all of which are quite common on Unix and Unix-like platforms.

/Applications/TextEdit.app is even usable for the creation of an empty 
text file, although I find it extremely limited for actual text 
editing and formatting.

-- 
David Ritz <dritz@mindspring.com>
 Be kind to animals; kiss a shark.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlU0biwACgkQUrwpmRoS3uu+vACeLnMnDNjyr43N534e7/Tdz3vq
rF0AoMeKdZqnwADfc42gW/stpTxXK7Jf
=gnE9
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#29049

From	dorayme <do_ray_me@bigpond.com>
Date	2015-04-20 13:52 +1000
Message-ID	<do_ray_me-0B0122.13525720042015@aioe.org>
In reply to	#29035

In article <alpine.OSX.2.20.1504192135570.57809@mako.ath.cx>,
 David Ritz <dritz@mindspring.com> wrote:

> The easiest way I can come up with, to create a new text file, in the 
> directory of your choice, is via Terminal application, found in 
> /Applications/Utilities/.  To create the file, type
> 
>     touch /full/path/to/file.txt
> 
>  $ touch ~/Desktop/file.txt
> 
>  $ ls -alF ~/Desktop/file.txt
>  -rw-r--r--+ 1 dritz  staff  0 Apr 19 21:42 /Users/dritz/Desktop/file.txt
> 
>  $ file /Users/dritz/Desktop/file.txt
>  /Users/dritz/Desktop/file.txt: empty

That's the easiest way eh on a Mac? Did you have a common-sense bypass 
at some stage?

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#29070

From	David Ritz <dritz@mindspring.com>
Date	2015-04-19 23:35 -0500
Message-ID	<alpine.OSX.2.20.1504192302500.57809@mako.ath.cx>
In reply to	#29049

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Monday, 20 April 2015 13:52 +1000, 
 in article <do_ray_me-0B0122.13525720042015@aioe.org>, 
 dorayme <do_ray_me@bigpond.com> wrote:

> In article <alpine.OSX.2.20.1504192135570.57809@mako.ath.cx>,
>  David Ritz <dritz@mindspring.com> wrote:

>> The easiest way I can come up with, to create a new text file, in 
>> the directory of your choice, is via Terminal application, found in 
>> /Applications/Utilities/.  To create the file, type

>>     touch /full/path/to/file.txt

> That's the easiest way eh on a Mac? Did you have a common-sense 
> bypass at some stage?

Criticize all you like, but I've yet to see anyone else offer a one 
step, or even two step solution.  ;)

The solution Adam appears to have ended up using, TextEdit.app, 
required many, not necessarily intuitive steps.  IIRC, I'm the only 
person to point out that his specific request for ASCII encoding 
required changing yet another default, as TextEdit defaults to UTF-8 
(good), but ASCII isn't even among the default choices available, in 
the application's Save as dialog.

Of course, I understand that he should have been asking about plain 
text, rather than a quite specific ASCII text encoding, as these are 
different concepts.

Do you have a problem with a simple, quite straight forward way of 
creating an empty text file, as requested.  After it's been created, 
double-clicking on that file will, by default, open as a plain text 
file, in TextEdit, for editing.

(Here, it will open in BBEdit 11.0.3, as it is configured as _my_ 
default GUI text editor.  Rich text files still open in TextEdit, by 
default.)

-- 
David Ritz <dritz@mindspring.com>
 Be kind to animals; kiss a shark.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlU0gh8ACgkQUrwpmRoS3usvfgCg61IshQT4obGZ4uqJWTjnes9J
iBYAnRnzWPm4YQkPHhzgiGOH/Ihkz9bm
=EbU0
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#29076

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-20 04:43 +0000
Message-ID	<cpjeg9F7dq8U11@mid.individual.net>
In reply to	#29070

On 2015-04-20, David Ritz <dritz@mindspring.com> wrote:
>
> On Monday, 20 April 2015 13:52 +1000, 
>  in article <do_ray_me-0B0122.13525720042015@aioe.org>, 
>  dorayme <do_ray_me@bigpond.com> wrote:
>
>> In article <alpine.OSX.2.20.1504192135570.57809@mako.ath.cx>,
>>  David Ritz <dritz@mindspring.com> wrote:
>
>>> The easiest way I can come up with, to create a new text file, in 
>>> the directory of your choice, is via Terminal application, found in 
>>> /Applications/Utilities/.  To create the file, type
>
>>>     touch /full/path/to/file.txt
>
>> That's the easiest way eh on a Mac? Did you have a common-sense 
>> bypass at some stage?
>
> Criticize all you like, but I've yet to see anyone else offer a one 
> step, or even two step solution.  ;)

In TextEdit:

1. Choose Format > Make Plain Text.
2. Save.

Good enough for me.

> The solution Adam appears to have ended up using, TextEdit.app, 
> required many, not necessarily intuitive steps.

No, he just chose the most complicated one, as usual.

> IIRC, I'm the only 
> person to point out that his specific request for ASCII encoding 
> required changing yet another default, as TextEdit defaults to UTF-8 
> (good), but ASCII isn't even among the default choices available, in 
> the application's Save as dialog.

Bull. All he needed to do was choose Format > Make Plain Text *before*
saving the document. No preferences needed to be changed.

-- 
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]

#29085

From	Michelle Steiner <michelle@michelle.org>
Date	2015-04-19 21:55 -0700
Message-ID	<190420152155298082%michelle@michelle.org>
In reply to	#29070

In article <alpine.OSX.2.20.1504192302500.57809@mako.ath.cx>, David
Ritz <dritz@mindspring.com> wrote:

> Criticize all you like, but I've yet to see anyone else offer a one 
> step, or even two step solution.  ;)

You haven't been paying attention.

[toc] | [prev] | [next] | [standalone]

#29151

From	David Ritz <dritz@mindspring.com>
Date	2015-04-20 02:07 -0500
Message-ID	<alpine.OSX.2.20.1504200200150.57809@mako.ath.cx>
In reply to	#29085

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Sunday, 19 April 2015 21:55 -0700, 
 in article <190420152155298082%michelle@michelle.org>, 
 Michelle Steiner <michelle@michelle.org> wrote:

> In article <alpine.OSX.2.20.1504192302500.57809@mako.ath.cx>, David
> Ritz <dritz@mindspring.com> wrote:

>> Criticize all you like, but I've yet to see anyone else offer a one 
>> step, or even two step solution.  ;)

> You haven't been paying attention.

Oh, but I have.  JF mentioned the use of touch, later in the thread.

Only a few of the TextEdit instruction sets have mentioned creating a 
new file; none have mentioned navigating the Save dialog box to the 
directory where the file is to be saved.  You may not count these as 
steps, but I do.

-- 
David Ritz <dritz@mindspring.com>
 Be kind to animals; kiss a shark.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlU0pagACgkQUrwpmRoS3usFZQCg8+XlL+rBxUwVNX+UDlKDP+k6
TkEAniVJAS4/wyb/b2R0l/zL3kfIdXrD
=wQOR
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#29165

From	"Adam H. Kerman" <ahk@chinet.com>
Date	2015-04-20 07:34 +0000
Message-ID	<mh2a5r$i5o$58@news.albasani.net>
In reply to	#29151

David Ritz <dritz@mindspring.com> wrote in message
alpine.OSX.2.20.1504200200150.57809@mako.ath.cx

> Only a few of the TextEdit instruction sets have mentioned creating a
> new file; none have mentioned navigating the Save dialog box to the
> directory where the file is to be saved.  You may not count these as
> steps, but I do.

You, of all those who have posted, understand the concept of steps!
Thank you!

[toc] | [prev] | [next] | [standalone]

#29242

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-20 14:57 +0000
Message-ID	<cpkiehFg4haU23@mid.individual.net>
In reply to	#29165

On 2015-04-20, Adam H. Kerman <ahk@chinet.com> wrote:
> David Ritz <dritz@mindspring.com> wrote in message
> alpine.OSX.2.20.1504200200150.57809@mako.ath.cx
>
>> Only a few of the TextEdit instruction sets have mentioned creating a
>> new file; none have mentioned navigating the Save dialog box to the
>> directory where the file is to be saved.  You may not count these as
>> steps, but I do.
>
> You, of all those who have posted, understand the concept of steps!
> Thank you!

Having been employed as a professional technical writer, I completely
understand the concept of steps, possibly better than you. 

-- 
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]

#29170

From	dorayme <do_ray_me@bigpond.com>
Date	2015-04-20 18:08 +1000
Message-ID	<do_ray_me-60842F.18084620042015@aioe.org>
In reply to	#29070

In article <alpine.OSX.2.20.1504192302500.57809@mako.ath.cx>,
 David Ritz <dritz@mindspring.com> wrote:

Just btw mind you, your posts have always reminded me of flashing neon 
signs in glitzy metro areas, all the extra irrelevant signage that 
appears in my newsreader! 

> On Monday, 20 April 2015 13:52 +1000, 
>  in article <do_ray_me-0B0122.13525720042015@aioe.org>, 
>  dorayme <do_ray_me@bigpond.com> wrote:
> 
> > In article <alpine.OSX.2.20.1504192135570.57809@mako.ath.cx>,
> >  David Ritz <dritz@mindspring.com> wrote:
> 
> >> The easiest way I can come up with, to create a new text file, in 
> >> the directory of your choice, is via Terminal application, found in 
> >> /Applications/Utilities/.  To create the file, type
> 
> >>     touch /full/path/to/file.txt
> 
> > That's the easiest way eh on a Mac? Did you have a common-sense 
> > bypass at some stage?
> 
> Criticize all you like, but I've yet to see anyone else offer a one 
> step, or even two step solution.  ;)
>

It's a one or two step solution in my Text-Edit. Just click the 
dropdown item in the format menu when beginning.

> The solution Adam appears to have ended up using, TextEdit.app, 
> required many, not necessarily intuitive steps.  IIRC, I'm the only 
> person to point out that his specific request for ASCII encoding 
> required changing yet another default, as TextEdit defaults to UTF-8 
> (good), but ASCII isn't even among the default choices available, in 
> the application's Save as dialog.
> 
> Of course, I understand that he should have been asking about plain 
> text, rather than a quite specific ASCII text encoding, as these are 
> different concepts.
>

OK. 

> Do you have a problem with a simple, quite straight forward way of 
> creating an empty text file, as requested.  

No, I don't have a problem but it feels complicated to ask a windoze 
bloke who in turn is helping to show a Mac user (who ipso facto is 
likely a bit of a novice) to create a text file... 

> After it's been created, 
> double-clicking on that file will, by default, open as a plain text 
> file, in TextEdit, for editing.
> 
> (Here, it will open in BBEdit 11.0.3, as it is configured as _my_ 
> default GUI text editor.  Rich text files still open in TextEdit, by 
> default.)

Your way is interesting and beautiful and I am sending you two 
kangaroos for you to kill and eat, the meat is very healthy and lean. 
You need to skill up to cook it right, it's a big mistake to overcook 
it as steak.

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#29249

From	David Ritz <dritz@mindspring.com>
Date	2015-04-20 10:33 -0500
Message-ID	<alpine.OSX.2.20.1504201014400.57809@mako.ath.cx>
In reply to	#29170

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Monday, 20 April 2015 18:08 +1000, 
 in article <do_ray_me-60842F.18084620042015@aioe.org>, 
 dorayme <do_ray_me@bigpond.com> wrote:

> In article <alpine.OSX.2.20.1504192302500.57809@mako.ath.cx>,
>  David Ritz <dritz@mindspring.com> wrote:

>> On Monday, 20 April 2015 13:52 +1000, 
>>  in article <do_ray_me-0B0122.13525720042015@aioe.org>, 
>>  dorayme <do_ray_me@bigpond.com> wrote:

>>> In article <alpine.OSX.2.20.1504192135570.57809@mako.ath.cx>,
>>>  David Ritz <dritz@mindspring.com> wrote:

>>>> The easiest way I can come up with, to create a new text file, in 
>>>> the directory of your choice, is via Terminal application, found 
>>>> in /Applications/Utilities/.  To create the file, type

>>>>     touch /full/path/to/file.txt

>>> That's the easiest way eh on a Mac? Did you have a common-sense 
>>> bypass at some stage?

>> Criticize all you like, but I've yet to see anyone else offer a one 
>> step, or even two step solution.  ;)

> It's a one or two step solution in my Text-Edit. Just click the 
> dropdown item in the format menu when beginning.

You left out one or two steps, one of which is navigating to the 
correct directory in the Save dialog.

>> Do you have a problem with a simple, quite straight forward way of 
>> creating an empty text file, as requested.

> No, I don't have a problem but it feels complicated to ask a windoze 
> bloke who in turn is helping to show a Mac user (who ipso facto is 
> likely a bit of a novice) to create a text file...

Adam may be a Mac novice, but he's no novice to Usenet and computing.  
I'm semi-familiar with him, as he's a regular in alt.config and a few 
other Usenet specific newsgroups.

Adam may be best served by thinking of OS X as a slick GUI shell, 
running on Unix (Darwin, a BSD variant).  Chances are he is familiar 
with editing text files from the command line.  I pointed him to the 
command line and mentioned a few CLI editors, at least one of which 
he's used previously.

While suggesting ...

    vim /full/path/to/file.txt

... might have worked for him, I'm quite certain it would have left 
his friend baffled and befuddled.

-- 
David Ritz <dritz@mindspring.com>
 Be kind to animals; kiss a shark.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlU1HFoACgkQUrwpmRoS3usSbACgtucnvA88wUWFvyIjtwtTa7iZ
wXQAniWa3RP6oKyHYnKYoSbKUzFzU7FT
=dWYg
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#29258

From	Warren Oates <warren.oates@gmail.com>
Date	2015-04-20 12:13 -0400
Message-ID	<5535258c$0$19438$c3e8da3$b1356c67@news.astraweb.com>
In reply to	#29049

In article <do_ray_me-0B0122.13525720042015@aioe.org>,
 dorayme <do_ray_me@bigpond.com> wrote:

> That's the easiest way eh on a Mac? Did you have a common-sense bypass 
> at some stage?

Actually, I agree with him. It is in fact the easiest way to create an 
empty file that the system will recognize as a plain-text file. I always 
have a terminal open anyway. I create files that way sometimes.
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#29260

From	Jolly Roger <jollyroger@pobox.com>
Date	2015-04-20 16:42 +0000
Message-ID	<cpkoj4Fig8hU1@mid.individual.net>
In reply to	#29258

On 2015-04-20, Warren Oates <warren.oates@gmail.com> wrote:
> In article <do_ray_me-0B0122.13525720042015@aioe.org>,
>  dorayme <do_ray_me@bigpond.com> wrote:
>
>> That's the easiest way eh on a Mac? Did you have a common-sense bypass 
>> at some stage?
>
> Actually, I agree with him. It is in fact the easiest way to create an 
> empty file that the system will recognize as a plain-text file. I always 
> have a terminal open anyway. I create files that way sometimes.

I use touch to create files all the time too - when I am already on the
command line. I definitely don't open a terminal window *just* to create
files, since there are much faster / better ways to do that from the
GUI.

-- 
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]

#29279

From	dorayme <do_ray_me@bigpond.com>
Date	2015-04-21 11:21 +1000
Message-ID	<do_ray_me-FECBF4.11213621042015@aioe.org>
In reply to	#29258

In article <5535258c$0$19438$c3e8da3$b1356c67@news.astraweb.com>,
 Warren Oates <warren.oates@gmail.com> wrote:

> In article <do_ray_me-0B0122.13525720042015@aioe.org>,
>  dorayme <do_ray_me@bigpond.com> wrote:
> 
> > That's the easiest way eh on a Mac? Did you have a common-sense bypass 
> > at some stage?
> 
> Actually, I agree with him. It is in fact the easiest way to create an 
> empty file that the system will recognize as a plain-text file. I always 
> have a terminal open anyway. I create files that way sometimes.

I am convinced about it being an easy way. Just that I baulked at a 
non-Mac teacher teaching a novice Mac user via Terminal. Seemed 
bizarre. 

--
You can kiss a duck's bum, but you have to be quick.

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#29053

From	Savageduck <savageduck1@{REMOVESPAM}me.com>
Date	2015-04-19 20:59 -0700
Message-ID	<2015041920590119679-savageduck1@REMOVESPAMme.com>
In reply to	#28976

On 2015-04-20 00:40:12 +0000, Adam H. Kerman said:

> I tried to help a friend create a simple text file on
> Macintosh OSX 10.9.5 and it was very difficult.
> 
> Right clicking didn't have any option to create a text file.
> http://i.imgur.com/RkrcG3M.png
> 
> So I had to find an existing text file because I couldn't
> just create an empty text file.
> 
> Once I dug around and found a text file, I then found the
> "duplicate" menu, and I duplicated it to "filename copy",
> but was unable to just cut and paste it without duplicating
> it first.
> 
> After duplicating it, I was able to cut and paste it so
> that I could put it in the folder where I wanted it to be.
> 
> But when I changed the name to a reasonable name to indicate
> it was a text file, the file simply disappeared! (I had named
> it something like filename.txt).
> 
> Having no idea what happened to the file I had just named
> filename.txt, I tried again by duplicating and then cutting
> and pasting without a filename extension, to just a file name
> of "save_text".
> http://i.imgur.com/Vp0LkB4.png
> 
> Only then (after far too many steps), was I able to have a
> text file in the location I wanted it.
> 
> Since the Mac is different from what I am used to, I am sure
> I am doing something very wrong since it can't be this complex
> to do something as simple as create an empty text file where
> you want it to exist with a file name that indicates it's
> a text file.
> 
> Given the simple goal of
> a) Creating a blank text file
> b) In a desired location
> c) With some indication that it's a text file
> How would a Mac user have done this task?

Open *TextEdit* go to the menu *File*->*New* and there it is a new, 
blank, virgin text doc.
Now without typing a single character return to the menu and 
*File*(while holding down the alt/option key)->*Save As*. You will see 
the save dialog which will let you name this file whatever you choose, 
and locate it wherever you want on that computer, in one of several 
text formats.

When you open that file it will be what you wanted, a blank text file.

-- 
Regards,

Savageduck

[toc] | [prev] | [next] | [standalone]

#29310

From	M-M <nospam@ny.more>
Date	2015-04-21 15:07 -0400
Message-ID	<210420151507213691%nospam@ny.more>
In reply to	#29053

In article <2015041920590119679-savageduck1@REMOVESPAMme.com>,
Savageduck <savageduck1@{REMOVESPAM}me.com> wrote:

> Open *TextEdit* go to the menu *File*->*New* and there it is a new, 
> blank, virgin text doc.
> Now without typing a single character return to the menu and 
> *File*(while holding down the alt/option key)->*Save As*.

Just "Save". While "Save As..." still works (although not in the menu),
it makes a copy and you still have to deal with the original.

-- 
m-m
http://www.mhmyers.com

[toc] | [prev] | [next] | [standalone]

Page 19 of 20 — ← Prev page 1 … 17 18 [19] 20 Next page →

csiph-web

How do mac users create a blank text file where you want it?

Contents

#29380

#29117

#28996

#29034

#29000

#29035

#29049

#29070

#29076

#29085

#29151

#29165

#29242

#29170

#29249

#29258

#29260

#29279

#29053

#29310