Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Re: illegible mp4 files (David W. Hodgins)
   2. Re: Colons in timestamp (Dave Howorth)


----------------------------------------------------------------------

Message: 1
Date: Mon, 25 Jan 2021 01:30:45 -0500
From: "David W. Hodgins" <davidwhodg...@gmail.com>
To: "Motion discussion list" <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] illegible mp4 files
Message-ID: <op.0xri1j0in7m...@hodgins.homeip.net>
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes

On Mon, 25 Jan 2021 01:08:22 -0500, tosiara <tosi...@gmail.com> wrote:
>> picture_filename %v-%Y%m%d%H%M%S-%q

What is the output of the locale command?

Regards, Dave Hodgins



------------------------------

Message: 2
Date: Mon, 25 Jan 2021 11:47:59 +0000
From: Dave Howorth <d...@howorth.org.uk>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] Colons in timestamp
Message-ID: <20210125114759.3aa24...@acer-suse.lan>
Content-Type: text/plain; charset=US-ASCII

On Sun, 24 Jan 2021 18:11:29 -0800
Tony Ross <ynots...@hotmail.com> wrote:

> On 1/24/21 5:35 PM, Steve wrote:
> > I'm very surprised I found nothing on this in the archives. The
> > colons in the filenames created by Motion are a no-no on Linux
> > systems and cause much grief. I haven't found anything in the docs
> > to address this either.
> >
> > I want the timestamp just w/o the colons. Is this possible?  
> 
> A colon is not a filename problem in Linux. One can certainly
> configure whatever filename one desires, but I think you are
> confusing colons and semicolons:
> 
> $ touch /tmp/time:stamp:00; file /tmp/time*
> /tmp/time:stamp:00: empty

Semicolons are not a problem either. You can use any character except a
forward-slash. You do need to quote filenames or escape characters
correctly though to avoid them being misinterpreted in some situations.

$ touch 'a file with:colons&and;semicolons'
$ file a\ *
a file with:colons&and;semicolons: empty



------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 175, Issue 20
********************************************

Reply via email to