From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: tml <tarantool-patches@freelists.org>,
tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 3/7] box/console: Add explicit output EOS mapping
Date: Fri, 25 Oct 2019 12:53:12 +0300 [thread overview]
Message-ID: <20191025095311.onkz36woc2bbzc5u@tkn_work_nb> (raw)
In-Reply-To: <20191025074012.GC2511@uranus.lan>
On Fri, Oct 25, 2019 at 10:40:12AM +0300, Cyrill Gorcunov wrote:
> On Fri, Oct 25, 2019 at 03:00:22AM +0300, Alexander Turenko wrote:
> >
> > Should not we wait for ';\n'?
>
> Strictly speaking ; is only eos, the newline is needed for terminal
> driver. But currently what we have might confuse a user, so I think
> you are probably right. Need to think and revisit this moment. Thanks!
We use this approach for reading of a client input on a remote server:
see client_read() in src/box/lua/console.lua ('\r' here to handle telnet
connections, see fa1aa01e49f323557fc981f7a76d85f99a9c7990).
Those delimiter was introduced before implementing local_check_lua(),
which works on a client side (both for local console and a client for a
remote console): when a delimiter is not set, we read input line by line
and try to parse it as a Lua statement using loadstring().
There are some flaws however:
https://github.com/tarantool/tarantool/issues/4082
I suspect the latter approach is not usable for cases where we have no
Lua interpreter on a client side (say, for test-run); I mentioned it to
provide more broad information.
next parent reply other threads:[~2019-10-25 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191004074926.17329-1-gorcunov@gmail.com>
[not found] ` <20191004074926.17329-4-gorcunov@gmail.com>
[not found] ` <20191025000022.msnkmuyh3mydxxim@tkn_work_nb>
[not found] ` <20191025074012.GC2511@uranus.lan>
2019-10-25 9:53 ` Alexander Turenko [this message]
2019-10-25 10:15 ` Cyrill Gorcunov
2019-11-01 12:49 ` Alexander Turenko
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=20191025095311.onkz36woc2bbzc5u@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [Tarantool-patches] [PATCH 3/7] box/console: Add explicit output EOS mapping' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox