Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Dec 2004 00:28:51 +0100
From:      Pav Lucistnik <pav@FreeBSD.org>
To:        Maksim Yevmenkin <maksim.yevmenkin@savvis.net>
Cc:        freebsd-bluetooth@FreeBSD.org
Subject:   Re: obexapp-1.4
Message-ID:  <1102634931.90683.9.camel@hood.oook.cz>
In-Reply-To: <41B8D6D5.6090801@savvis.net>
References:  <41B8D6D5.6090801@savvis.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-OMnFJx3pva6gquD39lT/
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Maksim Yevmenkin p=C3=AD=C5=A1e v =C4=8Dt 09. 12. 2004 v 14:51 -0800:
> Hello,
>=20
> please help me with testing of obexapp v1.4. it can be downloaded from
>=20
> http://www.geocities.com/m_evmenkin/obexapp-1.4.tar.gz
>=20
> the main feature is readline(3) support. it is now possible to repeat=20
> and edit commands in interactive mode. the command parser also has been=20
> changed. it is now possible to enter command parameters together with=20
> commands (for example "cd /" or "get foo bar").

obex> get Soul.mp3 Soul.mp3
Success, response: OK, Success (0x20)

obex> get Wazzup.mp3
Failure, response: Unautorized (0x41)

When I write get with single argument, could obexapp assume it as both
remote and local filename?

----------

There's some odity with line breaks, it seems, on my terminal:

+--------------------------------------------------------------------------=
---------------------------------------------------------------------------=
---------------------------------------------------------------------------=
---------+
| obex> get Soul.mp3 Soul.mp3                                              =
                                                                           =
                                              Success, response: OK, Succes=
s (0x20) |
| obex> get Wazzup.mp3
| Failure, response: Unautorized (0x41)
+-------------------------------------

Should there be so many spaces and shouldn't there be line break before
"Success" ?

----------

What about autocompletion, like in shell?

----------

What about unicode characters? My cell phones have czech localisation
and name of directories visible over OBEX are with czech characters,
coded in Unicode. Accessible for me with obexapp but in latin2 charset:

obex> ls
Access    Owner    Group    Size       Modified         Name
          n/a      n/a      n/a        n/a              Obr=C3=83=C2=A1zky/
          n/a      n/a      n/a        n/a              Zvuky/
          n/a      n/a      n/a        n/a              Sch=C3=83=C2=A9mata=
/
          n/a      n/a      n/a        n/a              Videosoubory/
          n/a      n/a      n/a        n/a              Jin=C3=83=C2=A9/
Success, response: OK, Success (0x20)
obex> cd Jin=C3=83=C2=A9
Failure, response: Not found (0x44)
obex> cd Jin=C3=A9
Success, response: OK, Success (0x20)

----------

It wanted to pair my cell phone on connect, obexapp-1.3 does not wanted
to pair.

----------

Otherwise it works very nice, big step forward in usability.

--=20
Pav Lucistnik <pav@oook.cz>
              <pav@FreeBSD.org>

On real UNIX, /usr/bin/more prints -More-.

--=-OMnFJx3pva6gquD39lT/
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?=
	=?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?=
	=?ISO-8859-1?Q?_zpr=E1vy?=

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQBBuN+zntdYP8FOsoIRAqkuAKCg0JT86U9DNeuOo3f2TjKJyizt3ACgqzh2
KwrowBH4RKaKOcWSv9+ZjMw=
=qagx
-----END PGP SIGNATURE-----

--=-OMnFJx3pva6gquD39lT/--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1102634931.90683.9.camel>