2016-08-26 4:06 GMT+09:00 Tony Mechelynck <[email protected]>:
> On Thu, Aug 25, 2016 at 3:13 PM, Kazunobu Kuriyama > <[email protected]> wrote: > > 2016-08-25 3:09 GMT+09:00 Tony Mechelynck <[email protected]> > : > >> > >> On Wed, Aug 24, 2016 at 8:03 PM, Tony Mechelynck > >> <[email protected]> wrote: > >> > On Wed, Aug 24, 2016 at 7:17 PM, Kazunobu Kuriyama > >> > <[email protected]> wrote: > >> >> Beep ((sound) bell) is implemented in both GTK+ 2 and GTK +3 using > >> >> gdk_display_bell() (gui_gtk_x11.c:6222, gui_mch_beep()), and there's > no > >> >> interdependency between beep and visual bell. Accordingly, visual > bell > >> >> setting is irrelevant to the audibility of beep at all. > >> >> > >> >> And, on X11, gdk_display_bell() is implemented using either XkbBell() > >> >> or > >> >> XBell(), which tells us that the beep sound comes from X11. > >> >> > >> >> You probably need to check if X11 bell (beep) is enabled or not, by > >> >> using, > >> >> say 'xset -q'. > >> > > >> > One of the lines there says: > >> > bell percent: 50 bell pitch: 400 bell duration: 100 > >> > > >> > which mean IIRC 50% intensity, about a quarter-tone above the G a > >> > perfect fourth below middle C (as close as I can make it at 440 Hz > >> > diapason), and one-tenth of a second. I'll try raising the level and > >> > see if it comes through my speakers. > > > > > > Hmm...I happen to know a little about music (well, I can tell Vim from > VIm), > > so I understand what you are talking about here...but, I'm still > wondering > > if those details are relevant to the current issue. > > > >> > > >> > > >> > Best regards, > >> > Tony. > >> > >> With 80 523 125 I still don't hear anything. > > > > > > Judging from the fact that 'xset b volume pitch duration' works, it > appears > > that X11 bell is still alive on your system. > > > > I suspect your desktop environment (I don't know what it is) prevents X11 > > bell from working. > > > > On my Mac, I have pulseaudio (but don't make it active. I need it in > order > > to build other libraries that depend on it). > > > > Looking at what were installed with it, I see there are two executables > > called 'start-pulseaudio-x11' and 'pax11publish', and there is the config > > file /etc/pulse/default.pa in which I see > > > > ### Load X11 bell module > > #load-module module-x11-bell sample=x11-bell > > > > I don't know if you are using pulseaudio on you system, but I think the > > facts above indicate that, in order to enable X11 bell, one needs to > tweak > > settings of a subsystem which plays the same role as pulseaudio does on > your > > system. And that's not an issue of our GTK GUI. > > > > Just my 2 cents. > > > >> > >> IOW, no audible bell I don't know why, no visual bell because GTK3 > >> gvim doesn't support it, ergo, no bell. > >> > >> > >> Best regards, > >> Tony. > > pulseaudio is installed here, along with several additional modules > for it. start-pulseaudio-x11 is installed as part of the > pulseaudio-module-x11 package, and pax11publish as part of the > pulseaudio-utils package. > > There is an /etc/pulse/default.pa of 164 lines. Its lines 146 to 150 are: > 146> # X11 modules should not be started from default.pa so that one > daemon > 147> # can be shared by multiple sessions. > 148> > 149> ### Load X11 bell module > 150> #load-module module-x11-bell sample=x11-bell > > i.e. commented-out, just as on your system. Looks you misunderstood me:) I didn't comment that out. > Do you think I should > uncomment line 150 (and make it different from yours)? Lines 146-147 > seem to say I shouldn't. > As the comment of default.pa indicates, if you know you'll have multiple X11 sessions, it's better in view of efficient resource usage to load module-x11-bell after the session management system starts, not when pulseaudio is initialized. So, it depends on your usage of X11. In addition, before loading the module, pulseaudio has to know about what audio file is designated as x11-bell and cache it (IOW, pulseaudio has no idea about the term x11-bell in the assignment 'sample=x11-bell' unless there happens to be an audio file called x11-bell.<ext>). (Note that, in this context, x11-bell is not the beep we hear when a computer starts booting. That no longer stands for something existing in the hardware. Instead, that's an abstraction of an audio file out of which pulseaudio makes sound when it receives a certain kind of X11 events.) So, a safer way to fulfill those is to call $ pactl upload-sample <path to an audio file you want to use as x11 bell> x11-bell $ pactl load-module module-x11-bell sample=x11-bell display=$DISPLAY in this order at an appropriate point (probably, after start-pulseaudio-x11 is invoked). As I'm not on Linux, I'm not sure if that helps you, though. > > Best regards, > Tony. > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
