From: Brad Midgley <bmidgley@xmission.com>
To: Florian Echtler <echtler@fs.tum.de>, bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: some btsco hacks
Date: Sun, 08 May 2005 23:16:10 -0600 [thread overview]
Message-ID: <427EF21A.7040908@xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0505062220440.10201@block>
Florian
> I noticed that there was a small bug left in my patch (the value of
> force_sco was overwritten when a reconnect was requested). This small
> additional patch should fix that.
ok, applied.
> Well, my .btscorc currently looks like this:
>
> AT\+CKPD=200
> sco-toggle on off
> AT\+CKPD=200
> system /home/echtler/bin/headset %d &
>
>>do you know what the syntax of 'back references' is in .btscorc?
>
> Back references to what/where?
backrefs are parts of the regexp surrounded by (). the matching
expression is remembered and can be placed in the command string, by \0
\1 etc it turns out.
I figured them out & noted in the docs.
In keeping with \0 \1 for backrefs in the regexp and \p for pid, the
headset state should be \s instead of %d. Would you be willing to make
that change (or I could)?
thanks
Brad
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-09 5:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 18:58 [Bluez-devel] some btsco hacks Florian Echtler
2005-05-05 21:09 ` [Bluez-devel] " Brad Midgley
2005-05-06 20:52 ` Florian Echtler
2005-05-09 5:16 ` Brad Midgley [this message]
2005-05-09 22:14 ` Florian Echtler
2005-05-09 23:11 ` Brad Midgley
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=427EF21A.7040908@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=echtler@fs.tum.de \
/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