public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Libor Ukropec <ace@seznam.cz>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] picocom 3.1
Date: Sat, 7 Jan 2023 19:59:51 +0100	[thread overview]
Message-ID: <e8c0ce89-a810-8412-11d1-3b8e2f367203@seznam.cz> (raw)
In-Reply-To: <d83b1bb6-9bec-108a-5d52-f5e36dac0491@dronecode.org.uk>

Dne 07.01.2023 v 18:58 Jon Turney via Cygwin-apps napsal(a):
> On 07/01/2023 13:26, Jon Turney via Cygwin-apps wrote:
>> On 03/01/2023 23:02, Libor Ukropec via Cygwin-apps wrote:
> 
>>> DESCRIPTION="picocom was designed to serve as a simple, manual, modem
>>>   configuration, testing, and debugging tool. It has also served (quite
>>>   well) as a low-tech \"terminal-window\" to allow operator intervention
>>>   in PPP connection scripts (something like the ms-windows \"open
>>>   terminal window before / after dialing\" feature). It could also prove
>>>   useful in many other similar tasks. It is ideal for embedded systems
>>>   since its memory footprint is minimal."
> Ah, I should have spotted: there is no quote character defined for these strings, so this 
> is invalid. Probably you should use embedded single quotes instead here.
Yes, I changed them to apostrophes. Then I noticed your email.
During writing I received info that it was accepted :)
> 
> This could do with fixing, but I suspect that it's not totally straightforward (I think 
> the lexer in setup would need to be taught how to handle them, and then we'd need to 
> ensure these escapes pass through cygport and calm)
I don't think it worth for the effort, if I'm one in the whole history

> 
> 


      reply	other threads:[~2023-01-07 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 23:02 Libor Ukropec
2023-01-07 13:26 ` Jon Turney
2023-01-07 17:03   ` Libor Ukropec
2023-01-07 17:58   ` Jon Turney
2023-01-07 18:59     ` Libor Ukropec [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8c0ce89-a810-8412-11d1-3b8e2f367203@seznam.cz \
    --to=ace@seznam.cz \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).