Talk:Take notes on the command line: Difference between revisions

From Rosetta Code
Content added Content deleted
m (→‎use of newline: added note about the use of periods in a filename. -- ~~~~)
m (→‎use of newline: minor fix. -- ~~~~)
 
(2 intermediate revisions by the same user not shown)
Line 8: Line 8:
The same is true of a ''tab'' character.   How a tab character is treated can be changed (or nullified) in some operating systems, and also application programs. -- [[User:Gerard Schildberger|Gerard Schildberger]] 19:01, 2 March 2013 (UTC)
The same is true of a ''tab'' character.   How a tab character is treated can be changed (or nullified) in some operating systems, and also application programs. -- [[User:Gerard Schildberger|Gerard Schildberger]] 19:01, 2 March 2013 (UTC)


This task seems to be ASCII-centric.
This task seems to be ASCII-centric.   Tab characters are different in an ASCII system vs. an EBCDIC system. -- [[User:Gerard Schildberger|Gerard Schildberger]] 19:04, 2 March 2013 (UTC)
* IBM mainframes (CMS & TSO mostly) don't use ''newline'' symbols within a file.
* Tab characters are different in an ASCII system vs. an EBCDIC system.
* CMS systems rarely use periods in the fileIDs   (they use ''filename filetype filemode'').
-- [[User:Gerard Schildberger|Gerard Schildberger]] 19:04, 2 March 2013 (UTC)


Not all file systems support the use of a period (dot) in the filename.   CMS for one, the file would be named:   '''NOTES   TXT'''.
Not all file systems support the use of a period (dot) in the filename.   CMS for one, the file would be normally be named:   '''NOTES   TXT'''   with an appended ''filemode''   (most often,   '''A1''').
<br>Lower case is supported, but it's not recommended for ease-of-use. -- [[User:Gerard Schildberger|Gerard Schildberger]] 19:09, 2 March 2013 (UTC)
<br>Lower case is supported, but it's not recommended for ease-of-use. -- [[User:Gerard Schildberger|Gerard Schildberger]] 19:09, 2 March 2013 (UTC)

Latest revision as of 19:19, 2 March 2013

Clarify task

I think the task description implicitly suggests that if a local NOTES.TXT file does not currently exist, and NOTES is called with arguments, then a new NOTES.TXT file should be created with the current time and those arguments. If that is the intention it would be useful to make this explicit in the task description.--Tikkanz 00:10, 21 May 2010 (UTC)

Your guess is correct. Feel free to correct it if you so desire or else wait till I've got time --Axtens 03:32, 21 May 2010 (UTC)

use of newline

Not all operating system's file structure use an imbedded newline.   Some use a metastructure.   Are programs (solutions) supposed to insert a bogus character at the end-of-line for those cases? -- Gerard Schildberger 19:04, 2 March 2013 (UTC)

The same is true of a tab character.   How a tab character is treated can be changed (or nullified) in some operating systems, and also application programs. -- Gerard Schildberger 19:01, 2 March 2013 (UTC)

This task seems to be ASCII-centric.

  • IBM mainframes (CMS & TSO mostly) don't use newline symbols within a file.
  • Tab characters are different in an ASCII system vs. an EBCDIC system.
  • CMS systems rarely use periods in the fileIDs   (they use filename filetype filemode).

-- Gerard Schildberger 19:04, 2 March 2013 (UTC)

Not all file systems support the use of a period (dot) in the filename.   CMS for one, the file would be normally be named:   NOTES   TXT   with an appended filemode   (most often,   A1).
Lower case is supported, but it's not recommended for ease-of-use. -- Gerard Schildberger 19:09, 2 March 2013 (UTC)