[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: apparently valid recutils file created when saved with comma

From: Charles Millar
Subject: Re: apparently valid recutils file created when saved with comma
Date: Wed, 1 Jul 2020 21:11:20 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

On 7/1/20 9:09 PM, Charles Millar wrote:
On 6/30/20 8:06 AM, Jose E. Marchesi wrote:

          Hi Charles.
              Recutils version 1.9
              I inadvertently saved a recutils file as something,rec (something-comma-rec)
              After a few attempts to print the records using recsel on
              something-dot-rec, I realized that the file name contained a comma not
              a dot.
              So I called recsel on something-comma-rec and the records in the file               were printed out. I tried a couple of other operations such as  recfix
              , and no errors.
              I would expect an error message such as "Invalid recutils file."               This a bug or is there some deep dark secret concerning naming               conventions? After all, the manual uses "dot"rec (or "period"rec, if
              you prefer.)
          The name of the file is irrelevant to recutils.
          The utilities will just read and process the file you provide, without
          looking at the file extension...
     I think Charles is complaining about the lack of a warning message when
     recfix is passed the name of a non-existent file.
     I think you fixed this bug a few days ago.
Oh I see :)

My post contained two questions and I was not clear. Each of you answered one part of it.

Over the years I have grown accustomed to the construct that an application must have one and only one associated extension or conform to some other standard (for lack of better word.) Or at least that is the way it appears.

Should have been "each file" has an entecnsion or defined extensions for an application.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]