tcross | 1 Jan 09:10 2010
Picon

SLIME mode


thought I'd start 2010 with a question.....

Is anyone out there using emacspeak and SLIME (Superior Lisp Interaction Mode
for Emacs)?

Out of the box, SLIME is not very emacspeak friendly. I've spent the morning
adding some advice and updating some hooks to make it a little easier to use.
However, it struck me that perhaps others have also done similar. Rather than
re-inventing the wheel, I thought I'd ask first. 

To get a fully functional speech interface for SLIME, it will take some work.
SLIME has a few add on modules and the imteraction is quite complex. I'm
starting with a very basic SLIME setup and have got some basic speech working,
but things need refinement. I figure the best way to do this is to just refine
my setup as I work with SLIME. Part of the issue is that SLIME comes with its
own slime repl, whihc has been done to improve the integration with emacs and
the inferior lisp process. This means that the normal emacspeak support for
comint mode doesn't really work and partly explains why the speech feedback is
a bit weak and why it will probably require a fair amount of work. SLIME can
be used with basic comint mode, but you loose a fair amount of the advanced
SLIME functionality doing it that way. 

So, I'm interested in working with anyone else who has been adressing the same
issue and I'm interested in anyone else who does a bit of common lisp hacking
who might be interested in being a guinea pig for what I'm working on. Of
course, once it reaches minimal maturity, I will contribute it to emacspeak!

Tim

(Continue reading)

T.V. Raman | 1 Jan 18:48 2010
Picon

SLIME mode

I've not used slime, which explains why there is no
emacspeak-slime.el

Tips on getting started based on creating other emcspeak modules:

Start simple, but step 0 create emacspeak-slime.el by following
the basic template as seen in other similar extensions.

For added credit, use folding-mode

Add relevant lines to the Makefile and to the place in
emacspeak.el where extensions are configured to load.

Then, advice things as you go --- and in a few weeks you'll have
code that is useful to more than just you.

What you dont want to do:

Create a rag-bag of hooks and such somewhere in your private
emacs setup -- it'l be twice as much work to turn that into a
useful contribution.

--

-- 
Best Regards,
--raman

Email			:  raman <at> users.sf.net :〒
WWW			:    http://emacspeak.sf.net/raman/ : ♁
       GTalk		: tv.raman.tv <at> gmail.com : ☏
PGP			:    http://emacspeak.sf.net/raman/raman-almaden.asc : ⌨
(Continue reading)

William Hubbs | 2 Jan 23:42 2010
Picon

[patch] espeak server should not install .so file in /usr/share/emacs

Hello Raman,

because of the way the makefiles are set up now for emacspeak, it is
possible for us on gentoo to automatically build the tclespeak.so module
if the user requests that when they install emacspeak.  However, the
default location where the .so is installed is not correct according to
bug http://bugs.gentoo.org/298012.

The same issue will also apply to the dtk-soft and outloud servers.

I have patches for the dtk-soft and espeak servers below.  But I haven't
written one for the outloud server yet since it uses the $tclTTS
variable not only for the .so path, but for the path to eci.ini as well.

These patches install the .so files in /usr/lib/emacspeak.  What do you
think about putting them there?  Also, where should we put eci.ini?
Maybe /etc/emacspeak?

William

Index: servers/dtk-soft
===================================================================
--- servers/dtk-soft	(revision 6424)
+++ servers/dtk-soft	(working copy)
 <at>  <at>  -292,7 +292,7  <at>  <at> 
 set tts(speech_rate)  225
 set tts(say_rate) [round \
                            [expr $tts(speech_rate) * $tts(char_factor)]]
(Continue reading)

T.V. Raman | 4 Jan 17:30 2010
Picon

[patch] espeak server should not install .so file in /usr/share/emacs

I  am not yet comfortable in putting files from emacspeak across
diferent parts of the file system -- it   makes cleaning up after
a mess. I dont like /usr/lib/emacspeak for that reason; I also
dislike the /etc/ hacks out there in some of the de debian packages.
-- 

-- 

On 1/2/10, William Hubbs <w.d.hubbs <at> gmail.com> wrote:
> Hello Raman,
>
> because of the way the makefiles are set up now for emacspeak, it is
> possible for us on gentoo to automatically build the tclespeak.so module
> if the user requests that when they install emacspeak.  However, the
> default location where the .so is installed is not correct according to
> bug http://bugs.gentoo.org/298012.
>
> The same issue will also apply to the dtk-soft and outloud servers.
>
> I have patches for the dtk-soft and espeak servers below.  But I haven't
> written one for the outloud server yet since it uses the $tclTTS
> variable not only for the .so path, but for the path to eci.ini as well.
>
> These patches install the .so files in /usr/lib/emacspeak.  What do you
> think about putting them there?  Also, where should we put eci.ini?
> Maybe /etc/emacspeak?
>
> William
>
>
(Continue reading)

Jason White | 5 Jan 06:02 2010
Picon

Re: [patch] espeak server should not install .so file in /usr/share/emacs

T.V. Raman <tv.raman.tv <at> gmail.com> wrote:
> I  am not yet comfortable in putting files from emacspeak across
> diferent parts of the file system -- it   makes cleaning up after
> a mess. 

I don't want to start a debate here, but I would like to express my agreement
with Raman on this point.

The major exception is where a package management system is tracking all of
those files and holds the responsibility for their subsequent removal, but in
that case, deciding where files belong in the hierarchy is the task of the
package maintainer, guided by the policies of the operating system
distribution.

I've wasted too much time cleaning up the results of "make install", and these
days I install from packages as a matter of preference. Emacspeak is under
$HOME anyway, in my case.

Tim Cross | 5 Jan 07:20 2010
Picon

Re: [patch] espeak server should not install .so file in /usr/share/emacs


jason, you beat me to it! I also agree. The main point I was going to make is
that I think in the case of a distro specific package i.e. rpm, deb, etc, it
is the responsability of the package maintainer to decide where the files
belong. While there has been considerable standardisation in this area,
different distributions still have their own preferences. If we were to
change the layout for one, we could be incompatible for another. 

Possibly the only thing we really need to do is make sure there are no hard
coded location dependencies in the sources and maybe support a way, such as
via environment variables or emacs custom variables, which would make it easy
for package maintainers to put things in their own preferred location. As far
as I'm aware, I think this is largely already the case.

Of course the downside of this position is that it may result in fewer distros
having packaged versions of emacspeak. I'm a little divided on whether this is
a real issue or not. Emacspeak is a relatively small and easy to install
application which can run from any installation location. Having to install it
from svn or a tar snapshot is easy and there is an argument that doing so
helps users understand how it all fits together and puts them in a better
position to troubleshoot problems. I also think that the rate at which Raman
enhances the system is far too high for any packaged versions to keep up, so
the packaged versions tend to be a fair bit older than the latest stable
release and a lot older than the current svn version. On the downside, it does
mean that anyone wanting to use emacspeak will need to be prepared to deal
with the installation and while not difficult, there are many who are just put
off by such requirements. Personally, I don't see this as a major issue.

Tim

(Continue reading)

T.V. Raman | 12 Jan 02:26 2010
Picon

Possible format bug?

I was unable to reproduce the "format" bug ...

On 12/22/09, Robert D. Crawford <robdcraw <at> gmail.com> wrote:
> Sorry, this should have gone to the list.
>
>
> Hi Tim,
>
> tcross <at> rapttech.com.au writes:
>
>> (format nil "~: <at> d" 1000000) ==> "+1,000,000"
>
> Reading this line produces this output:
>
> mode all
> plus 1 comma 0 0 0 comma 0 0 0
>
> mode some
> plus 1 0 0 0 0 0 0
> with a short pause between the third and fourth zeros
>
> mode none reads the same as mode some
>
> Using
> ViaVoice
> emacspeak 30.0 6170M (rather old svn version)
> emacs version GNU Emacs 23.1.50.1 (i686-pc-linux-gnu) of 2009-06-25
> running Ubuntu 9.04, kernel 2.6.28-13-generic
>
> rdc
(Continue reading)

Tim Cross | 13 Jan 07:37 2010
Picon

Re:Possible format bug?

Hi Raman,

are you using outloud or espeak? I've noticed the problem exists in outloud,
but not espeak. From other reports, it seems that it didn't exists prior to a
certain version (still trying to track down when it started). this is based on
some reports I've recieved where it does and does not happen, depending on the
version being used. 

Tim

T.V. Raman writes:
 > I was unable to reproduce the "format" bug ...
 > 
 > On 12/22/09, Robert D. Crawford <robdcraw <at> gmail.com> wrote:
 > > Sorry, this should have gone to the list.
 > >
 > >
 > > Hi Tim,
 > >
 > > tcross <at> rapttech.com.au writes:
 > >
 > >> (format nil "~: <at> d" 1000000) ==> "+1,000,000"
 > >
 > > Reading this line produces this output:
 > >
 > > mode all
 > > plus 1 comma 0 0 0 comma 0 0 0
 > >
 > > mode some
 > > plus 1 0 0 0 0 0 0
(Continue reading)

tcross | 13 Jan 07:47 2010
Picon

Oddity with espeak


I've noticed something a little odd with the espeak speech driver and wanted
to know if others experience the same thing. 

With espeak, if I have split-caps enabled, any capital letters are always
spoken with the prefix word "Capital". It does not matter what I set the
capitalisation mode to or all caps beep.

However, as soon as I disable split caps mode, then I can get the  all caps
beep to make a beep/clic sound when getting a capital. As soon as I re-enable
split caps mode, espeak goes back to speaking the prefix "Capital".

anyone else noticed this and has anyone found a fix? I like split caps mode,
but find the constant repeating of "Capital" very annoying. 

I'm running CVS emacspeak on a debian testing/unstable box with emacs 23 built
from CVS. 

Tim

--

-- 
Tim Cross
tcross <at> rapttech.com.au

There are two types of people in IT - those who do not manage what they 
understand and those who do not understand what they manage.

T.V. Raman | 14 Jan 05:32 2010
Picon

Oddity with espeak

I use Outloud on the laptop, Dectalk at home. I have not been
able to reproduce the problem.

-- 
Best Regards,
--raman

Email			:  raman <at> users.sf.net :〒
WWW			:    http://emacspeak.sf.net/raman/ : ♁
       GTalk		: tv.raman.tv <at> gmail.com : ☏
PGP			:    http://emacspeak.sf.net/raman/raman-almaden.asc : ⌨
Google			: tv+raman  :  ?
IRC			:    irc://irc.freenode.net/#emacs : ☢
BRL:	⠠⠞⠲⠀⠠⠧⠲⠀⠠⠗⠁⠍⠁⠝	: ☠

On 1/12/10, tcross <at> rapttech.com.au <tcross <at> rapttech.com.au> wrote:
>
> I've noticed something a little odd with the espeak speech driver and wanted
> to know if others experience the same thing.
>
> With espeak, if I have split-caps enabled, any capital letters are always
> spoken with the prefix word "Capital". It does not matter what I set the
> capitalisation mode to or all caps beep.
>
> However, as soon as I disable split caps mode, then I can get the  all caps
> beep to make a beep/clic sound when getting a capital. As soon as I
> re-enable
> split caps mode, espeak goes back to speaking the prefix "Capital".
>
> anyone else noticed this and has anyone found a fix? I like split caps mode,
(Continue reading)


Gmane