Hi T. V. and Tim, Thanks a lot for the tips, I'll definitely use these. How can I check where variables are being set during Emacspeak start-up, without losing speech? One of the issues that made me stuck was that using debug-watch in my init file meant I didn't have speech to read the debugger output. Thanks! Sent from my iPhone > On Jan 13, 2024, at 03:58, T.V Raman <raman@xxxxxxxxxx> wrote: > > > and never forget M-. for cross-references. You can start with grep, > but grep lie any search will land you in the middle of things; but to > undrstand something --- anything? --- starting at the beginning is a > better idea. > > > > Tim Cross writes: >> >> Just wanted to re-iterate Raman's suggestion, especially reading >> emaspeak sources. >> >> I would also add that experimenting using both the scratch buffer and >> ielm mode are extremely useful. As you read through the code, when you >> come across code or documentation explanations you are having trouble >> grasping, experimenting inside the ielm repl or the scratch buffer can >> be extremely enlightening. In fact, I often find a few minutes playhing >> with a command or function and/or setting different variable values in >> ielm or the scratch buffer is far more productive than lots of google >> searching. Problem with google is it cannot tell you which results are >> bad advice or just plain wrong. In recent times, I find the rapid >> increase in 'noise' has drastically reduced the reliability of google >> results. >> >> >> >> >> "\"T.V Raman\"" (via emacspeak Mailing List) <emacspeak@xxxxxxxxxxxxx> writes: >> >>> Ack. The best resource I can point you at are: >>> >>> 1. Emacspeak sources and docs, >>> 2. Emacs docs >>> >>> >>> >>> Parham Doustdar writes: >>>> Hi Raman, >>>> Thanks for the explanation and the changes. >>>> You made me realise that I have no clue what goes on in the Makefile. I’ll learn from >>>> the syntax and look deeper into that, thanks. >>>> I also wanted to reassure you that I know everyone is busy, and sending an email is not >>>> my first reaction to encountering an issue. That is what I hope to illustrate by always >>>> including the steps that I took to debug or resolve it. When I send an email asking >>>> something, it’s because either (1) I wonder if I’m understanding the intention >>>> correctly or (2) my skills and Google haven’t turned up a solution, likely because I’m >>>> encountering an “unknown unknown”. >>>> I’m always very open to learning, so if you or anyone else on the list has concrete >>>> steps I could take, or resources I could learn from, feel free to share – I commit to >>>> taking action on getting better at solving my own problems. >>>> Thanks. >>>> >>>>> On 11 Jan 2024, at 18:26, T.V Raman <raman@xxxxxxxxxx> wrote: >>>>> >>>>> I've changed the default to nil, had it set to nil in my .custom file >>>>> which was shadowing the default. >>>>> >>>>> 1. defcustom declares the variable with its default >>>>> 2. make config puts the default into loaddefs.el >>>>> 3. Before jumping off to send email, take some time to understand >>>>> things, experiment etc. >>>>> 4. Just sending me email will likely mean I'll stop responding since >>>>> like you I too am busy. >>>>> 5. >>>>> -- > > --
|Full archive May 1995 - present by Year|Search the archive|
If you have questions about this archive or had problems using it, please contact us.