Sébastien Hinderer, le mar. 26 mars 2024 13:40:48 +0100, a ecrit:
> I think what mislead me is that, although the braille rendering isdone
> by BRLTTY, there continues to be a speech rendering which, I think, _is_
> done by Orca.
That's entirely possible, since Orca doesn't even know that brltty
Hello,
Sébastien Hinderer, le mar. 26 mars 2024 12:00:58 +0100, a ecrit:
> I think my graphical Mate terminals are rendered by Orca, whereas I do
> see a graphical BRLTTY process, run with the command
>
> /bin/brltty -b ba -s no -x a2 -N
>
> I assume there is a priroity issue between two BrlAPI
Hello,
Sebastian Humenda, le mar. 27 févr. 2024 13:16:10 +0100, a ecrit:
> I wonder whether someone else knows more details?
At the time, I had a quick look at the standard, and all I could see was
just definitions for keys, i.e. nothing for the actual output...
Samuel
Hello,
John Covici, le mer. 21 févr. 2024 16:19:51 -0500, a ecrit:
> Hi. Using orca either from git or the gnome 45 branch, I am not
> getting any Braille. I have traced this to the following when trying
> to import brlapi
>
> Traceback (most recent call last):
> File "", line 1, in
>
HEllo,
Mike Gorse, le jeu. 22 févr. 2024 11:33:49 -0600, a ecrit:
> I'm trying to upgrade speech-dispatcher in openSUSE, since someone needs the
> socket activation. Anyway, brltty now fails to build:
>
> ./speech.c: In function ‘speechdAction’:
> ./speech.c:76:26: error: ‘SPDConnection’ has no
Hello,
Jason J.G. White, le ven. 15 déc. 2023 11:09:41 -0500, a ecrit:
> On 15/12/23 10:23, John wrote:
> > Secondly, disabling the service ought to have been sufficient to prevent
> > the software from disrupting the operation of the system, but it wasn't.
> > It had to be completely removed. Is
Hello,
matthias.gerst...@suse.de, le mer. 13 déc. 2023 15:06:16 +0100, a ecrit:
> - root:
> - for USB I/O via USBFS (using the devices in /dev/bus/usb/).
> - for creating virtual devices via the uinput device.
> - cap_sys_admin: For injecting input characters typed on a braille
Hello,
Sebastian Humenda, le ven. 20 oct. 2023 15:02:04 +0200, a ecrit:
> I do rely a lot on scren navigation using the keyboard, for instance,
> RightShift + Up mapped to LNUP, etc. This is not available by default
> in X, as keyboard sniffing doesn't work the same way on X as on the
> console.
Dave Mielke, le lun. 16 oct. 2023 11:56:12 -0400, a ecrit:
> [quoted lines by Leonard de Ruijter on 2023/10/16 at 17:29 +0200]
>
> >Hmm, that's an interesting issue with building for Python. Aren't you getting
> >that error without the patch from PR 432?
>
> Yes, PR 432 has no impact on the
Hello,
Leonard de Ruijter, le lun. 09 oct. 2023 19:50:39 +0200, a ecrit:
> Unfortunately, I can't get the thing to load on Python 3.11-32.
>
> I'm getting the error: `ImportError: DLL load failed while importing brlapi:
> The specified module could not be found.`
Probably you need to add to
Dave Mielke, le lun. 09 oct. 2023 01:00:16 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2023/10/08 at 21:43 +0200]
>
> >In the generated usb-generic.rules file, we can read
> >
> >ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Hedo Reha Technik Gm
Hello,
In the generated usb-generic.rules file, we can read
ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Hedo Reha Technik GmbH",
ENV{BRLTTY_BRAILLE_DRIVER}="hd", GOTO="brltty_usb_run"
ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Tivomatic Oy",
ENV{BRLTTY_BRAILLE_DRIVER}="at",
Hello,
Samuel Thibault, le jeu. 28 sept. 2023 01:28:01 +0200, a ecrit:
> Samuel Thibault, le jeu. 28 sept. 2023 01:26:57 +0200, a ecrit:
> > Apparently cython3 introduced some support for it, so it will be worth
> > trying it indeed.
>
> (namely: CYTHON_LIMITED_API,
Samuel Thibault, le jeu. 28 sept. 2023 01:26:57 +0200, a ecrit:
> Leonard de Ruijter, le mer. 27 sept. 2023 19:51:10 +0200, a ecrit:
> > Python has something like the stable application binary Interface (ABI), see
> > https://docs.python.org/3.11/c-api/stable.html . T
Hello,
Leonard de Ruijter, le mer. 27 sept. 2023 19:51:10 +0200, a ecrit:
> Python has something like the stable application binary Interface (ABI), see
> https://docs.python.org/3.11/c-api/stable.html . This can be used by
> enabling the limited API.
>
> I wonder, has this ever been considered?
Hello,
Halim Sahin, le mar. 19 sept. 2023 11:48:24 +0200, a ecrit:
> Now I have a working debian bookworm setup which performs well :-).
>
> The only thing which is not perfect is the speed of the routing when
> using EG xfce4-terminal.
> It would be great if this can be speeded up a bit.
Hello,
payman shaykhmehdi, le mer. 23 août 2023 10:24:11 +0330, a ecrit:
> > I have reverted the change in [1]https://github.com/brltty/brltty/pull/426
>
> Yes, this solves the problem.
Dave, this also very well could argue in favor of a 6.6.1 fix release,
since with this bug, keys essentially
payman shaykhmehdi, le mar. 22 août 2023 07:41:44 +0330, a ecrit:
> What do you actually observe? Do you see warnings from xbrlapi?
>
> Running xblapi in verbose mode, it doesn't log any error or warnings. And also
> there no (braille)keypress event log.
Oops.
I indeed erroneously rewrote
payman shaykhmehdi, le lun. 21 août 2023 15:46:04 +0330, a ecrit:
> I've compiled brltty 6.6 in ubuntu 20.04.6 LTS. Braille output in X windows
> and
> graphical apps works great.
> But the problem is with braille input. It seems that xbrlapi can not read
> keys
> from brlapi connection.
What
Chevelle, le mar. 15 août 2023 15:06:05 -0400, a ecrit:
> configure: WARNING: Libbraille package not found: /usr /usr/local
> /usr/local/Libbraille /usr/local/libbraille /opt/Libbraille /opt/libbraille
> /mingw /mingw/Libbraille /mingw/libbraille
> configure: WARNING: Mikropuhe package not found:
Chevelle, le mar. 15 août 2023 14:35:55 -0400, a ecrit:
> In the documentation at https://brltty.app/download.html#current
>
> it says there are Debian packages at
> ftp://ftp.debian.org/debian/pool/main/b/brltty/
>
> This link seems to be broken.
Indeed, this should be
Dave Mielke, le mar. 15 août 2023 10:41:28 -0400, a ecrit:
> [quoted lines by Lukáš Tyrychtr on 2023/08/15 at 14:46 +0200]
> >I've successfully tracked the reason for the brlapi crash under Cython 3.0,
>
> Excellent!
>
> All: How urgently should a new brltty release show up?
I don't know if
Hello,
Lukáš Tyrychtr, le mar. 15 août 2023 14:46:10 +0200, a ecrit:
> I've successfully tracked the reason for the brlapi crash under Cython 3.0,
> or at least it is the only one.
Thanks for tracking!
> Cython 3.0 started using the new Python object finalization APIs from PEP
> 442, and it
Alexander Epaneshnikov, le mar. 15 août 2023 00:28:36 +0300, a ecrit:
> On Mon, Aug 14, 2023 at 11:05:22PM +0200, Samuel Thibault wrote:
> > Alexander Epaneshnikov, le lun. 14 août 2023 23:34:30 +0300, a ecrit:
> > > On Mon, Aug 14, 2023 at 09:46:00PM +0200, Samuel Thibault wrot
Alexander Epaneshnikov, le lun. 14 août 2023 23:34:30 +0300, a ecrit:
> On Mon, Aug 14, 2023 at 09:46:00PM +0200, Samuel Thibault wrote:
> > J.G, le lun. 14 août 2023 21:28:56 +0200, a ecrit:
> > > I'm forwarding it in case brltty developers don't know about this bug.
> &g
J.G, le lun. 14 août 2023 21:28:56 +0200, a ecrit:
> I'm forwarding it in case brltty developers don't know about this bug.
We are not aware at all...
Samuel
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to:
Didier Spaier, le jeu. 03 août 2023 12:16:49 +0200, a ecrit:
> Le 03/08/2023 à 11:49, Samuel Thibault a écrit :
> > Samuel Thibault, le mer. 02 août 2023 22:30:21 +0200, a ecrit:
> >> Samuel Thibault, le jeu. 20 juil. 2023 19:28:37 +0200, a ecrit:
> >>> Samuel Thibaul
Elias Oltmanns, le jeu. 03 août 2023 12:05:15 +0200, a ecrit:
> Just out of curiosity: Would it not make sense for the kernel to clear
> the input buffer whenever it switches to a context with increased
> privileges?
The problem is that it's quite tricky to know when the switch happens.
And the
Samuel Thibault, le mer. 02 août 2023 22:30:21 +0200, a ecrit:
> Samuel Thibault, le jeu. 20 juil. 2023 19:28:37 +0200, a ecrit:
> > Samuel Thibault, le dim. 16 juil. 2023 23:33:02 +0200, a ecrit:
> > > Dave Mielke, le dim. 16 juil. 2023 12:10:39 -0400, a ecrit:
> > >
Hello,
Samuel Thibault, le jeu. 20 juil. 2023 19:28:37 +0200, a ecrit:
> Samuel Thibault, le dim. 16 juil. 2023 23:33:02 +0200, a ecrit:
> > Dave Mielke, le dim. 16 juil. 2023 12:10:39 -0400, a ecrit:
> > > [quoted lines by Nicolas Pitre on 2023/07/16 at 00:33 -0400]
> &
Samuel Thibault, le dim. 16 juil. 2023 23:33:02 +0200, a ecrit:
> Dave Mielke, le dim. 16 juil. 2023 12:10:39 -0400, a ecrit:
> > [quoted lines by Nicolas Pitre on 2023/07/16 at 00:33 -0400]
> >
> > >Best would be to fix the kernel.
> >
> > That's happening.
Dave Mielke, le dim. 16 juil. 2023 12:10:39 -0400, a ecrit:
> [quoted lines by Nicolas Pitre on 2023/07/16 at 00:33 -0400]
>
> >Best would be to fix the kernel.
>
> That's happening. My understanding is that, in the 6.4 kernel, Samuel
> has an accepted patch which ignores the sysctl setting if
Halim Sahin, le dim. 09 juil. 2023 09:48:15 +0200, a ecrit:
> Current situation on my machines is that brltty also tries to give some
> braille output for non-Terminal apps like gedit or mousepad etc.
Yes, but in that a case, isn't priority given to your other screen
reader such as orca?
Samuel
Dave Mielke, le lun. 26 juin 2023 12:49:05 -0400, a ecrit:
> TIOCSTI injects input. Of course one could argue that that poses a security
> risk, but how is that different from creating a uinput device and injecting
> key events? What am I missing?
Basically, TIOCSTI is not privileged and
Hello,
Crystal Kolipe, le dim. 25 juin 2023 13:02:49 -0300, a ecrit:
> it wouldn't make much sense for my kernel patch to necessarily emulate the
> data format of the linux vcsa device at all, we might as well send the data
> out as the raw unicode codepoints from the wscons display buffer.
Hello,
Christian Schoepplein, le ven. 23 juin 2023 16:37:45 +0200, a ecrit:
> Is this a known issue with kernel 6.3?
Unfortunately, yes: TIOCSTI poses security problems so it got
disabled by default. I had warned at that time that it was needed for
accessibility and proposed solutions, but
Jason White, le mar. 06 juin 2023 10:05:21 -0400, a ecrit:
> (Minor qualification: cursor routing with braille display routing keys isn't
> supported, but my recollection is that this is a Wayland limitation which
> presumably hasn't been solved yet - you can't inject simulated keystrokes.)
Yes,
Jason White, le lun. 05 juin 2023 18:13:05 -0400, a ecrit:
>
> On 5/6/23 17:31, Samuel Thibault wrote:
> > ? It does work in my tests. How do you run it?
> > At-spi is actually mostly independent from the differences between x11
> > and wayland.
>
> Intere
Hello,
Jason White, le lun. 05 juin 2023 10:05:26 -0400, a ecrit:
> At the moment, the BRLTTY At-spi support doesn't function in Wayland
> sessions - it works under X11 sessions only.
? It does work in my tests. How do you run it?
At-spi is actually mostly independent from the differences
Hello,
Halim Sahin, le ven. 31 mars 2023 06:19:22 +0200, a ecrit:
> cursor routing no longer works in current brltty when using
> screen-driver a2 in Terminal (gnome-terminal and xfce4-terminal) tested.
>
> The only thing i see is invalid async handle in debug log and a segfault
> in dmesg.
It
Halim Sahin, le ven. 31 mars 2023 04:57:24 +0200, a ecrit:
> 835 | return handleGetDriver(c, type, size, disp ? disp->keyBinding : "");
> | ^~
> | keyBindings
Oops,
Hello,
Stefan Moisei, le sam. 28 janv. 2023 19:42:39 +, a ecrit:
> 1. I made it work in brltty, it works in the windows console.
> 2. I tried the brlapi from NVDA (I think it is 0.8) after net start brlapi
> and
> got this:
>
> brlapi.OperationError:
> for get display size, get driver
Sébastien Hinderer, le mer. 25 janv. 2023 13:33:45 +0100, a ecrit:
> Samuel Thibault (2023/01/23 11:38 +0100):
> > Sébastien Hinderer, le sam. 21 janv. 2023 19:15:38 +0100, a ecrit:
> > > Dr. Volker Jaenisch (2023/01/21 18:25 +0100):
> > > >This may be due
Hello,
Sébastien Hinderer, le sam. 21 janv. 2023 19:15:38 +0100, a ecrit:
> Dr. Volker Jaenisch (2023/01/21 18:25 +0100):
> >This may be due to tmux but the real terminal is 700km away and I
> >cannot look upon it.
>
> Thinking about it twice it seems likely, yes.
Yes, tmux won't know
Dr. Volker Jaenisch, le jeu. 29 déc. 2022 21:57:23 +0100, a ecrit:
> What are the benefits/risks to let brltty run from the kernel?
That option doesn't mean running it from the kernel. It means copyin it
into the initramfs, so it can be started before the root filesystem is
mounted. E.g. for
Hello,
Sébastien Hinderer, le lun. 14 nov. 2022 09:13:28 +0100, a ecrit:
> 2. As suggested by Samuel privately, it may be suitable to have the
> support for embedding BRLTTY in initramfs upstreamed so that this
> feature becomes available in all distributions, especially in the
> context of being
Hello,
Finn Pedersen, le sam. 12 nov. 2022 16:33:00 +0100, a ecrit:
> [brltty] Braille Driver: ba [BrlAPI]
> [brltty] BrlAPI Braille Driver: version 0.1, 2005
This is the log for the brltty daemon running in your X session to
support atspi2 through brlapi. This is not the log of the brltty
Finn Pedersen, le jeu. 10 nov. 2022 14:50:02 +0100, a ecrit:
> When no device is connected I get this
>
> File Descriptor: 5
> Server Host: b':0'
> Authorization Schemes: b'none'
> Driver Name: b'NoBraille'
>
> When the Focus Blue 40 (4th gen) is connected I get this
>
> File Descriptor: 3
>
Hello,
Chevelle, le mer. 12 oct. 2022 16:45:33 -0400, a ecrit:
> Where would I find the python source code used to create the Windows
> driver?
It's within the brltty source code, ./Build/mk-windows, which calls
./Windows/mkwin.
Samuel
___
This
Hello,
Dietmar Segbert, le mar. 11 oct. 2022 18:39:00 +0200, a ecrit:
> I have now installed python 32bit version 3.8.10 installer for windows,
> which is the last installerpackage.
>
> But there is no success. I become the same error, that there is no entry
> in the registry for the python
Hello,
Sebastian Humenda, le lun. 10 oct. 2022 19:36:42 +0200, a ecrit:
> I use NVDA regularly, but have installed JAWS too.
I assume JAWS is not running?
> Now, running debug-brltty.bat from an administrator CMD results in the
> attached log file.
We didn't receive a log file in your mail.
Julian, le mar. 11 oct. 2022 18:08:45 +0200, a ecrit:
> Attached are the logs, copied from /tmp/brltty.log (I enabled the
> corresponding config first). I hope this brings us any further.
We'd need
log-level debug
to be uncommented, to have much more information. Also, is your log from
the udev
Hello,
Dietmar Segbert, le sam. 08 oct. 2022 15:40:00 +0200, a ecrit:
> In teh readme stood, if i want to use nvda, i shall do
>
> Brlapi-0.8.4.win32.exe
>
> which i found in the python directory.
Yes.
> I have instaled pytho 3.10 32bit from the installer from python.org.
IIRC one has to
Hello,
Please keep the list in Cc, so the discussion can be archived and useful
for everybody.
Julian, le sam. 08 oct. 2022 19:32:17 +0200, a ecrit:
> Well no, I didn't install the OS myself. The VM pool is on a server, and I'm
> connecting to it using my laptop and a dedicated VMware client
Hello,
Julian, le jeu. 06 oct. 2022 12:10:38 +0200, a ecrit:
> While I already reported the bug to VMware, does anyone of you maybe
> know a workaround for this and would be willing to share it with me?
I would doubt that it'd be a vmware-specific issue, since there
shouldn't be anything really
Dave Mielke, le lun. 19 sept. 2022 18:37:55 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2022/09/20 at 00:22 +0200]
>
> >It seems we have another generic identifier issue, see below and
> >attached lsusb.
>
> 1A86:7523 is, as it should be, defined within th
Hello,
It seems we have another generic identifier issue, see below and
attached lsusb.
Samuel
- Forwarded message from beattie <1990...@bugs.launchpad.net> -
From: beattie <1990...@bugs.launchpad.net>
Subject: [Bug 1990189] [NEW] brlttty claiming CH341 usbtty device blocking
access
Vsevolod Popov, le ven. 02 sept. 2022 21:26:55 +0300, a ecrit:
> On 9/2/22 19:19, Samuel Thibault wrote:
> > The question is maybe: where would you have looked for it? That's
> > probably where it should belong :)
> I looked here):
> https://qemu-project.gitlab.io/qemu/system
Hello,
Vsevolod Popov, le ven. 02 sept. 2022 19:08:25 +0300, a ecrit:
> Is it documented somewhere?
It is documented in the -usbdevice option documentation
> I didn't find this short way in qemu's usb emulation section of
> documentation.
Yes, qemu people tend to think that the interface
Hello,
Vsevolod Popov, le ven. 02 sept. 2022 14:00:44 +0300, a ecrit:
> -device qemu-xhci \
> usb-braille,chardev=id-of-braille-display
You only have to pass
-usbdevice braille
and that will automatically configure both the frontend (the virtual
device) and the backend (that connects to brltty
Alan Zhang, le jeu. 23 juin 2022 20:07:58 +0800, a ecrit:
> Your judgment is correct. After installing the package libxaw7-dev, I saw a 40
> ×1 braille display appear on the screen. However,
> Judging from the printed logs, there are still problems:
>
> $sudo brltty -n -ldebug -b xw -x as -A
Hello,
张钦楠, le jeu. 23 juin 2022 16:37:05 +0800, a ecrit:
> 2) compile and install
> ./autogen
> ./configure
Please send us the resulting config.log file, probably you are missing
some X11 headers for the XWindow driver to be built.
Samuel
___
This
Dave Mielke, le ven. 10 juin 2022 10:11:53 -0400, a ecrit:
>brltty-clip now has better long options.
>brltty-hid has been added.
>brltty-ttysize has been added.
Could such tools have a summary of what they are doing?
Usage: brltty-hid [option ...]
-u --match-usb-devices
Dave Mielke, le mer. 18 mai 2022 19:55:38 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2022/05/19 at 00:50 +0200]
>
> >I was wondering about it indeed. When I looked at the 1a40:0101 vendor
> >it looked quite generic to me: Terminus Technology Hub. Are we really
Dave Mielke, le mer. 18 mai 2022 18:36:14 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2022/05/18 at 17:59 +0200]
>
> >ENV{PRODUCT}=="403/6001/*", ATTR{manufacturer}=="Hedo Reha Technik GmbH",
> >ENV{BRLTTY_BRAILLE_DRIVER}="hd", GOTO=&quo
Dave Mielke, le mer. 18 mai 2022 11:48:15 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2022/05/16 at 18:29 +0200]
> >Yes but we'd also want a -genericonly option too, so distributors also
> >have a file they can install for the people who do want udev rules for
>
Hello,
Dave Mielke, le mar. 17 mai 2022 15:53:56 -0400, a ecrit:
> [quoted lines by Samuel Thibault on 2022/05/16 at 18:29 +0200]
>
> >Yes but we'd also want a -genericonly option too, so distributors also
> >have a file they can install for the people who do want udev rules
Mario Lang, le lun. 16 mai 2022 18:26:25 +0200, a ecrit:
> Samuel Thibault writes:
>
> > Mario Lang, le ven. 13 mai 2022 07:12:54 +0200, a ecrit:
> >> Samuel Thibault writes:
> >>
> >> > As reported on Ubuntu which happens to install brltty by defa
Mario Lang, le ven. 13 mai 2022 07:12:54 +0200, a ecrit:
> Samuel Thibault writes:
>
> > As reported on Ubuntu which happens to install brltty by default in its
> > latest release, the udev rules for braille devices with generic USB IDs
> > are hurting people that have ha
Hello,
As reported on Ubuntu which happens to install brltty by default in its
latest release, the udev rules for braille devices with generic USB IDs
are hurting people that have hardware that use the same usb-serial chip.
Dave, could you split the udev rules file in two pieces, one with only
Hello,
About such crashes, I'm wondering: would running brltty-ctb be enough
to exercise them? We've been doing some fuzzing work on espeak-ng and
liblouis, possibly that could be applied as is on brltty as well.
Samuel
高生旺, le ven. 06 mai 2022 23:40:15 +0800, a ecrit:
> First please enable
Joakim Nordell, le ven. 29 avril 2022 14:24:42 +0200, a ecrit:
> Yes, the visual output on the screen is also really slow.
Ok so it's most probably related to the use of the VESA driver instead
of the hardware-accelerated driver, and not to be looked at in brltty
itself.
Samuel
Hello,
Joakim Nordell, le ven. 29 avril 2022 08:42:01 +0200, a ecrit:
> I am running linux in console mode, 1920x1080, so there is room for
> about 240 characters on a single line and about 66 lines per page.
> I have noticed some differences in the output from fbset -i:
> The machine at work
John J. Boyer, le jeu. 28 avril 2022 06:02:11 -0500, a ecrit:
> If making a new package from the current brltty repository is too much work,
> what can I do to solve these problems?
The problem is not making a new package, but identifying what should be
included in it. Please discuss with
Adrian van Bloois, le lun. 11 avril 2022 13:40:00 +0200, a ecrit:
> On Mon, Apr 11, 2022 at 06:30:50AM -0500, John J. Boyer wrote:
> > Sometimes a message in mutt stops brltty. When I go to a console with root
> > already logged in and do something brltty restarts.
> > have others had this
Aura Kelloniemi, le lun. 04 avril 2022 08:53:27 +0300, a ecrit:
> It may even be possible to make it so that
> it does not need BRLTTY's braille key translation, but can input straight to
> the Linux console (if that is where you want to run this).
I'd rather say to emit braille key events to
Christian Schoepplein, le lun. 28 mars 2022 12:48:02 +0200, a ecrit:
> On Sun, May 09, 2021 at 10:18:23PM +0200, Samuel Thibault wrote:
> >Christian Schoepplein, le dim. 09 mai 2021 21:29:27 +0200, a ecrit:
> >> There are also other issues and problems with the output of brltty
Dave Mielke, le jeu. 17 mars 2022 10:57:03 -0400, a ecrit:
> As far as I know, when using BrlAPI (which Orca does), only brltty's text
> table would be used. Thus, if Orca can be set to contracted (literary)
> braille, then I assume it's doing its own translation and sending dot
> patterns to
Hello,
Mario Lang, le ven. 11 févr. 2022 02:30:16 +0100, a ecrit:
> Working on a Haskell binding for BrlAPI.
Nice :D
> The following example works:
\o/
> I think it would be better to have a
> different type of handle for ttyMode operations. IOW, return some
> handle from enterTtyMode and
Halim Sahin, le mar. 01 févr. 2022 08:48:06 +0100, a ecrit:
> On Mon, Jan 31, 2022 at 01:13:31PM +0100, Samuel Thibault wrote:
> > Halim Sahin, le lun. 31 janv. 2022 12:56:42 +0100, a ecrit:
> > > Example:
> > > copy the string with brltty in to clipboard and paste
Samuel Thibault, le mer. 26 janv. 2022 00:26:49 +0100, a ecrit:
> Samuel Thibault, le mar. 25 janv. 2022 23:59:37 +0100, a ecrit:
> > Alexander Epaneshnikov, le mer. 26 janv. 2022 00:24:18 +0300, a ecrit:
> > > On Tue, Jan 25, 2022 at 10:06:57PM +0100, Samuel Thibault wrote:
>
Hello,
Halim Sahin, le mar. 01 févr. 2022 10:13:51 +0100, a ecrit:
> yes it is ctrl+shift+v and xbrlapi is running as well.
Ok.
> I thought, that brltty is using its own clipboard
Yes it is.
> so that never worked here.
Before the 6.4 release that wouldn't work indeed. But xbrlapi in version
Samuel Thibault, le mar. 01 févr. 2022 09:19:43 +0100, a ecrit:
> Halim Sahin, le mar. 01 févr. 2022 08:48:06 +0100, a ecrit:
> > > That being said, for pasting you should be able to just use
> > > control-shift-V, which will directly paste from the brltty cutbuffer
>
Halim Sahin, le mar. 01 févr. 2022 08:48:06 +0100, a ecrit:
> > That being said, for pasting you should be able to just use
> > control-shift-V, which will directly paste from the brltty cutbuffer
> > into the application, without having to go through keypresses
> > simulation, thus much more
Halim Sahin, le lun. 31 janv. 2022 12:56:42 +0100, a ecrit:
> Example:
> copy the string with brltty in to clipboard and paste the contents.
> /abcd/
>
> Result:
> /
>
> Brltty changes the first slash with &.
>
> This only happens when using a2 screendriver.
> Tested in xfce4-terminal.
Hello,
Frans-Willem Post, le sam. 29 janv. 2022 22:08:49 +0100, a ecrit:
> Is there a possibility to use the Braille input keys of my Freedom
> Scientific Focus 40 Blue under Wayland?
Not with the current status of keyboard support under Wayland. That
needs some more work.
Samuel
Samuel Thibault, le mar. 25 janv. 2022 23:59:37 +0100, a ecrit:
> Alexander Epaneshnikov, le mer. 26 janv. 2022 00:24:18 +0300, a ecrit:
> > On Tue, Jan 25, 2022 at 10:06:57PM +0100, Samuel Thibault wrote:
> > > That won't fix
> > > the keyboard synthesis, however:
Alexander Epaneshnikov, le mer. 26 janv. 2022 00:24:18 +0300, a ecrit:
> On Tue, Jan 25, 2022 at 10:06:57PM +0100, Samuel Thibault wrote:
> > That won't fix
> > the keyboard synthesis, however: that's probably to be fixed in the X
> > server.
>
> if you have more info
Dave Mielke, le ven. 21 janv. 2022 14:37:01 -0500, a ecrit:
> [quoted lines by Alexander Epaneshnikov on 2022/01/21 at 21:36 +0300]
> >I think xbrlapi needs to be fixed.
> >Samuel asked me to debug it in gdb. but so far I have not been able to
> >figure out gdb and do it.
>
> Do you think it can
Hello,
Alexander Epaneshnikov, le jeu. 30 déc. 2021 00:24:05 +0300, a ecrit:
> On Wed, Dec 29, 2021 at 10:10:25PM +0100, Samuel Thibault wrote:
> > Alexander Epaneshnikov, le jeu. 30 déc. 2021 00:05:41 +0300, a ecrit:
> > > On Wed, Dec 29, 2021 at 09:45:18PM +0100, Sam
Hello,
Halim Sahin, le lun. 17 janv. 2022 15:20:30 +0100, a ecrit:
> I don't know if was intended behaviour :-(.
>
> If a user has some text copied in to brltty's clipboard and accidentaly
> hits cupslock, brltty pastes the copied text in uppercase as well.
>
> In my opinion brltty should
Dave Mielke, le mar. 18 janv. 2022 12:26:15 -0500, a ecrit:
> Perhaps someone could explain what the actual problem is so that a proper
> resolution can be implemented.
AIUI the problem is being able to specify which ld/strip/ranlib to use,
i.e.:
./configure LD=lld STRIP=llstrip RANLIB=llranlib
Alexander Epaneshnikov, le mar. 18 janv. 2022 03:18:37 +0300, a ecrit:
> > Orca actually already supports that, you can enable it in
> > its preference dialog.
>
> this is exactly what does not work for me, nor for Vsevolod.
Then that should be fixed.
> and this problem is now bypassed by
Alexander Epaneshnikov, le lun. 17 janv. 2022 00:12:37 +0300, a ecrit:
> On Sun, Jan 16, 2022 at 03:09:04PM -0500, Dave Mielke wrote:
> > [quoted lines by Alexander Epaneshnikov on 2022/01/16 at 22:45 +0300]
> >
> > >I think Dave, please correct me if this isn't the case - brltty doesn't
> > >use
Dave Mielke, le mar. 11 janv. 2022 12:41:01 -0500, a ecrit:
> [quoted lines by Samuel Thibault on 2022/01/11 at 15:00 +0100]
>
> >It's the /etc/X11/Xsession.d/90xbrlapi script that runs
> >
> >brltty -b ba -s no -x a2 -N
> >
> >you can add a -n option there.
&g
Vsevolod Popov, le mar. 11 janv. 2022 15:17:10 +0300, a ecrit:
> 11.01.2022 14:23, Dave Mielke пишет:
> > Since you don't have direct control over the instancers that are started by
> > Systemd+udev, you could try adding the -f /path/to/brltty.conf option to
> > the invocation of the AtSpi2
Alexander Epaneshnikov, le sam. 08 janv. 2022 18:26:04 +0300, a ecrit:
> On Sat, Jan 08, 2022 at 03:22:01PM +0100, Samuel Thibault wrote:
> > Alexander Epaneshnikov, le ven. 07 janv. 2022 17:23:10 +0300, a ecrit:
> > > vm at[1] can't use brltty however attached script works.
Alexander Epaneshnikov, le ven. 07 janv. 2022 17:23:10 +0300, a ecrit:
> vm at[1] can't use brltty however attached script works.
The script from the arch-vm tarball is missing the -display sdl option.
Samuel
___
This message was sent via the BRLTTY
Alexander Epaneshnikov, le jeu. 30 déc. 2021 00:05:41 +0300, a ecrit:
> On Wed, Dec 29, 2021 at 09:45:18PM +0100, Samuel Thibault wrote:
> > Ideally you'd run xbrlapi inside gdb with a breakpoint on the exit
> > function to get a backtrace of what actually in X11 raises the error.
Alexander Epaneshnikov, le mer. 29 déc. 2021 23:42:10 +0300, a ecrit:
> On Wed, Dec 29, 2021 at 09:27:29PM +0100, Samuel Thibault wrote:
> > Alexander Epaneshnikov, le mer. 29 déc. 2021 23:02:44 +0300, a ecrit:
> > > Remapped keycode 248 to keysym 01002801
> >
1 - 100 of 350 matches
Mail list logo
