Hello,
I ended up having to go back to emacspeak version 56.0 for it to start working again normally. There is something in version 57.0 that is causing issues with either the mac or version 28.2 of emacs itself. Thank you for these instructions. They helped me get my emacspeak back to a working state.
Greg Wocher
> On Dec 11, 2022, at 6:43 PM, Tim Cross <theophilusx@xxxxxxxxxxx> wrote:
>
>
> OK, given you have installed from the git repository, you are most
> likely running the latest development sources. The last stable release
> was emacspeak 57.0, which was released 13 days ago.
>
> When Raman releases a new version, the repository is tagged with a
> version tag for that version. This means you can always checkout the
> version corresponding to s specific release by doing
>
> git checkout <tag>
>
> where <tag> is the release version number i.e. to get the last stable release,
> do
>
> git checkout 57.0
>
> You will then want to do
>
> make clean
> make config
> make
>
> Later, if you want to checkout the latest code and try it again, you can do a
>
> git checkout master
>
> At any time to return to the tip of the version tree. You can also do a
>
> git log
>
> to see a log of commits which have been made. Each entry in the log has
> a commit hash which can be used to identify a specific commit. The hash
> is quite long, but you don't need the whole hash, just enough of it to
> identify the commit you are after (usually the first 6 to 10 characters
> will work). You can use the has as the target to a git checkout to
> checkout the code as it was when that commit was made.
>
> The most common mistake people make when working with the git repository
> is forgetting to do a make clean and make config after checking out new
> sources . It is crucial that you do make clean and make config after any
> update to the code base. These commands are quick and easy to run and
> will ensure your build is consistent. Failure to do this can result in a
> mixed version, leading to unstable results.
>
> Using git checkout, you can move between different versions. As running
> master means your running code which Raman is actively working on, it
> will break from time to time. Often, you can get back to working code by
> just checking out an earlier commit or you can just wait a day or so and
> things will usually stabilise. Make sure you do a git pull on a regular
> basis to ensure you have the latest code base.
>
> Most people really only need to upgrade when they update to a later
> version of Emacs or when Raman does a stable release (usually twice a
> year). If you run the latest development version of Emacs, you typically
> want to update more frequently as Emacspeak is usually kept pretty
> up-to-date with new features in the development version.
>
> If you really want to be cautious, you can use git log *before* you do a
> git pull to see what version/commit your currently on and note down the
> commit hash number. Then do a git pull to get the latest sources,
> followed by the make clean, make config and make to build. If you find
> problems with th elatest build, you can use git checkout and the commit
> hash you noted at the start to return to the same version you were
> running, do a make clean, make config and make and your back to the same
> code you had before doing the update. This is one of the great benefits
> of using the git repository rather than a tar ball - you can easily move
> between versions or restore a previous version if the current head
> version doesn't work correctly etc.
>
> Greg Wocher <gtwocher@xxxxxxxxxxx> writes:
>
>> Hello,
>> I upgraded to the latest version in the git repo. How do I check which version it is? I am running emacs version 28.2.
>>
>> Thanks,
>> Greg Wocher
>>
>>
>>> On Dec 11, 2022, at 4:08 PM, Tim Cross via Emacspeak <emacspeak@xxxxxxxxxxx> wrote:
>>>
>>>
>>> When you say you upgraded to the latest version, do you mean you
>>> upgraded to Emacspeak 57.0 or you upgraded to the head of the git
>>> repository?
>>>
>>> Ask as I know that Raman has been working on updates to handle changes
>>> in Org mode which will be in Emacs 29 when it is released. If your
>>> running Emacs 28 or earlier, you are probably better off just running
>>> Emacspeak 57 (the last stable release).
>>>
>>> If you are running Emacspeak 57, then more investigation will be
>>> necessary to find out what the issue may be.
>>>
>>> Greg Wocher via Emacspeak <emacspeak@xxxxxxxxxxx> writes:
>>>
>>>> Hello all,
>>>> I am having some strange issues since I updated emacs and emacspeak to the latest versions
>>>> on my mac. Whenever I try to exit out using c-x c-c I get a strange error about there
>>>> being an undefined character in the mini buffer. Also when I use c-g to quit a partial
>>>> command it just says back to top level. I also get back to top level when I try to
>>>> activate the menu using esc then tilda. Does anyone know what I might be able to do to try
>>>> and fix this issue?
>>>>
>>>> Thanks,
>>>> Greg Wocher
>>>> _______________________________________________
>>>> Emacspeak mailing list -- emacspeak@xxxxxxxxxxx
>>>> To unsubscribe send an email to emacspeak-leave@xxxxxxxxxxx
>>> _______________________________________________
>>> Emacspeak mailing list -- emacspeak@xxxxxxxxxxx
>>> To unsubscribe send an email to emacspeak-leave@xxxxxxxxxxx
>
_______________________________________________
Emacspeak mailing list -- emacspeak@xxxxxxxxxxx
To unsubscribe send an email to emacspeak-leave@xxxxxxxxxxx
|May 1995 - Last Year|Current Year|
If you have questions about this archive or had problems using it, please contact us.