Menu
▾
▴
alphacocoa-devel — AlphaCocoa Development List
You can subscribe to this list here.
| 2016 |
Jan
|
Feb
|
Mar
(12) |
Apr
(19) |
May
(60) |
Jun
(77) |
Jul
(23) |
Aug
(8) |
Sep
(28) |
Oct
(16) |
Nov
(95) |
Dec
(56) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017 |
Jan
(127) |
Feb
(169) |
Mar
(59) |
Apr
(132) |
May
(27) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
(15) |
Oct
(12) |
Nov
(15) |
Dec
(17) |
| 2018 |
Jan
|
Feb
(2) |
Mar
(25) |
Apr
(19) |
May
(28) |
Jun
(75) |
Jul
(48) |
Aug
|
Sep
(31) |
Oct
(26) |
Nov
(51) |
Dec
(82) |
| 2019 |
Jan
(46) |
Feb
(7) |
Mar
(8) |
Apr
|
May
(9) |
Jun
(8) |
Jul
(21) |
Aug
(30) |
Sep
(9) |
Oct
(16) |
Nov
(14) |
Dec
(23) |
| 2020 |
Jan
|
Feb
(6) |
Mar
|
Apr
(7) |
May
(47) |
Jun
(12) |
Jul
(7) |
Aug
(5) |
Sep
(4) |
Oct
(24) |
Nov
(15) |
Dec
(14) |
| 2021 |
Jan
(6) |
Feb
(5) |
Mar
(20) |
Apr
(6) |
May
(46) |
Jun
(17) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2025 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Chris S. <cs...@us...> - 2021-06-02 10:49:28
|
Not on the machine I am using the most at the moment. I will upgrade. On 2 Jun 2021, at 8:05 pm, Bernard Desgraupes via AlphaCocoa-devel <alp...@li...<mailto:alp...@li...>> wrote: External email: Please exercise caution ________________________________ Hi Chris, are you using the new Alpha 9.2.3 ? ________________________________ [tickets:#251]<https://sourceforge.net/p/alphacocoa/tickets/251> Strange hang Status: open Created: Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels Last Updated: Wed Jun 02, 2021 07:08 AM UTC Owner: nobody Attachments: * Problem Report.txt<https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt> (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. ________________________________ Sent from sourceforge.net<http://sourceforge.net> because alp...@li...<mailto:alp...@li...> is subscribed to https://sourceforge.net/p/alphacocoa/tickets/<https://sourceforge.net/p/alphacocoa/tickets/> To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options.<https://sourceforge.net/p/alphacocoa/admin/tickets/options.> Or, if this is a mailing list, you can unsubscribe from the mailing list. _______________________________________________ AlphaCocoa-devel mailing list Alp...@li...<mailto:Alp...@li...> https://lists.sourceforge.net/lists/listinfo/alphacocoa-devel --- ** [tickets:#251] Strange hang** **Status:** open **Created:** Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels **Last Updated:** Wed Jun 02, 2021 10:05 AM UTC **Owner:** nobody **Attachments:** - [Problem Report.txt](https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt) (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-02 10:05:00
|
Hi Chris, are you using the new Alpha 9.2.3 ? --- ** [tickets:#251] Strange hang** **Status:** open **Created:** Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels **Last Updated:** Wed Jun 02, 2021 07:08 AM UTC **Owner:** nobody **Attachments:** - [Problem Report.txt](https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt) (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Chris S. <cs...@us...> - 2021-06-02 07:36:38
|
Hi Bernard, The % character has certainly been there on occasion, as does the notion of automatic line breaking (which I do have turned on). That said, it is one of those things that was infrequent and not something that I was ever thinking about until it started happening, whereupon it was a bugger to get rid of. Anyway, what you describe has that ring of familiarity to it. I would be happy if my bug was marked as a duplicate of the earlier ones and, if it persists after the next upgrade, it can always be re-opened. Cheers, Chris. On 2 Jun 2021, at 5:08 pm, Bernard Desgraupes <bde...@us...<mailto:bde...@us...>> wrote: External email: Please exercise caution ________________________________ Hi Chris, Bugs #246 and #249 have been explicitly fixed. I don't know if this is the same problem as the one you encounter but here are the circumstances that triggered the apparent freeze: it occurred potentially in any mode provided the current document had Automatic Line Breaking turned on and there was an escaped comment character in the current line. For instance, in TeX mode (where the comment symbol is %), a line like Optimus pretosius corrumperet ossifragi \% catelli... triggered the freeze when the cursor's position reached the maximum line length (usually position 70 on the line) and also during a reflow with cmd-I. A quoted comment character (like "%" in TeX mode) had the same effect. In Tcl mode, \# or "#" would cause the problem etc. Explanation: when deciding to break a line or not, Alpha checks whether the current line is a comment or not, so it looks for a true comment symbol (that would not be escaped or enclosed in quotes). There was unfortunately a mistake in the code: the start position of the search was not properly updated so Alpha kept looking from the same position again, and again, and again... This has been fixed in Alpha 9.2.3. Do you observe the same or similar circumstances ? ________________________________ [tickets:#251]<https://sourceforge.net/p/alphacocoa/tickets/251> Strange hang Status: open Created: Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels Last Updated: Tue Jun 01, 2021 08:37 PM UTC Owner: nobody Attachments: * Problem Report.txt<https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt> (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. ________________________________ Sent from sourceforge.net<http://sourceforge.net> because you indicated interest in https://sourceforge.net/p/alphacocoa/tickets/251/<https://sourceforge.net/p/alphacocoa/tickets/251/> To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/<https://sourceforge.net/auth/subscriptions> --- ** [tickets:#251] Strange hang** **Status:** open **Created:** Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels **Last Updated:** Wed Jun 02, 2021 07:08 AM UTC **Owner:** nobody **Attachments:** - [Problem Report.txt](https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt) (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-02 07:08:51
|
Hi Chris, Bugs #246 and #249 have been explicitly fixed. I don't know if this is the same problem as the one you encounter but here are the circumstances that triggered the apparent freeze: it occurred potentially in any mode provided the current document had *Automatic Line Breaking* turned on and there was an *escaped* comment character in the current line. For instance, in TeX mode (where the comment symbol is `%`), a line like ``` Optimus pretosius corrumperet ossifragi \% catelli... ``` triggered the freeze when the cursor's position reached the maximum line length (usually position 70 on the line) and also during a reflow with cmd-I. A quoted comment character (like "%" in TeX mode) had the same effect. In Tcl mode, `\#` or `"#"` would cause the problem etc. Explanation: when deciding to break a line or not, Alpha checks whether the current line is a comment or not, so it looks for a true comment symbol (that would not be escaped or enclosed in quotes). There was unfortunately a mistake in the code: the start position of the search was not properly updated so Alpha kept looking from the same position again, and again, and again... This has been fixed in Alpha 9.2.3. Do you observe the same or similar circumstances ? --- ** [tickets:#251] Strange hang** **Status:** open **Created:** Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels **Last Updated:** Tue Jun 01, 2021 08:37 PM UTC **Owner:** nobody **Attachments:** - [Problem Report.txt](https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt) (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Chris S. <cs...@us...> - 2021-06-01 20:37:16
|
That previous post should have said TeX mode not text. This, I believe ,is just a repeat of Bug #249, which I notice that you have just closed. Has something happened for it to be resolved? It continues to happen for me, although I am still yet to find the cause. That said, it is a tenacious problem once it occurs. It will continually happen at a particular point in the text, no obvious pattern as to which point, although always towards where a line break should ordinarily occur. Once it happens then simply adding further text to the line, even a carriage return will freeze Alpha, it does not require cmd-I to induce the problem. The same problem will not necessarily occur elsewhere in the file and sometimes you can get around it (adding text to the next line will sometimes enable the paragraph to be re-flowed, but not always. I wish I had something more useful to contribute. Cheers, Chris --- ** [tickets:#251] Strange hang** **Status:** open **Created:** Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels **Last Updated:** Tue Jun 01, 2021 08:28 PM UTC **Owner:** nobody **Attachments:** - [Problem Report.txt](https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt) (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Chris S. <cs...@us...> - 2021-06-01 20:29:00
|
Further to this, I am mostly in text mode and the key combination cmd-I does seem to induce the problem. --- ** [tickets:#251] Strange hang** **Status:** open **Created:** Thu Apr 22, 2021 06:00 AM UTC by Chris Skeels **Last Updated:** Sat May 15, 2021 11:07 AM UTC **Owner:** nobody **Attachments:** - [Problem Report.txt](https://sourceforge.net/p/alphacocoa/tickets/251/attachment/Problem%20Report.txt) (3.0 MB; text/plain) Every now and then, not often, I find that Alpha hangs for no apparent reason. This most recent time I caught the report that would have been sent to Apple, in case this is of any benefit at all. It doesn't happen so often that it is a major event, but it is always annoying when it does happen. Like as not it is interaction with something else on my machine rather than Alpha itself. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 13:15:36
|
- **status**: fixed --> closed - **Version**: 9.2.2 --> 9.2.3 --- ** [tickets:#252] S+/R mode - Process Current File (Cmd^T) fails** **Status:** closed **Labels:** S+/R mode **Created:** Thu May 13, 2021 09:21 AM UTC by Fischlin Andreas **Last Updated:** Tue May 18, 2021 01:46 PM UTC **Owner:** nobody The essential menu command "S+/R -> Process Current File" of the S+/R mode fails. It does no longer source, i.e. it does not process the current file. I am sorry to lack the time right now to figure out why that is. Perhaps it is the R GUI app which has changed, but then Alpha might need to adjust what Apple Event it sends to R. In any case, INMHO the mode is crippled by this problem. Does anyone perhaps know a solution to this problem? I would greatly appreciate getting any hints on how to circumvent this if bigger modifications would be required to the mode as this is rather at the moment urgent for me. Thanks. Alpha 9.2.2 (10145) -- R 3.6.1 GUI 1.70 El Capitan build -- OS X 10.14.6 (Mojave) --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 13:15:28
|
- **status**: fixed --> closed
- **Version**: 9.2.2 --> 9.2.3
---
** [tickets:#250] RemReminder on ticket #248 : Problems with the spellchecker of Alpha 9.2.2 in TeX Mode for french**
**Status:** closed
**Created:** Sun Apr 11, 2021 09:30 AM UTC by Laurent PRALY
**Last Updated:** Fri May 21, 2021 01:09 PM UTC
**Owner:** nobody
Having received no comment on ticket 248, I am rewriting it here with increasing its priority to major.
I have problems with the spellcker of Alpha 9.2.2 in TeX Mode for french. Specifically in a text in french, the job is not done correctly in presence of accents or in comments.
Here are the parameters concerning spelling in my Alpha's configuration for the TeX Mode
Choose an implementatation for spellcheck: Alpha
Alpha Preferences: "TeX" Mode > LaTeX Accents
Accent Smart Escape: Yes
Accents in Comments: No
Bind LaTeX Accents: No
Accente Syntax: \'{e} & \oe{}
Alpha Preferences: "TeX" Mode Features
LaTeX Accents: Yes
My test file is:
\documentclass[a4paper,12pt]
% letter
\begin{document}
Nous \'{e}tudions ici le bouclage dynamique de sortie qui est un sujet extr\^{e}mement extremement vaste. Nous nous li-mi-tons \`{a} l'\'{e}nonc\'{e} d'id\'{e}es directrices et \`{a} une pr\'{e}sentation tr\`{e}s in\'{e}gale des r\'{e}sultats, avec beaucoup de d\'{e}tails pour certains et \`{a} peine une \'{e}bauche pour d'autres.
\end{document}
After starting Alpha, I created a new file with the above content, change the mode to TeX, typed the above and recorded the file. Then Edit > Spelling > Spelcheck window flagged successively the following words,
**letter** Find next
**extr** Find next
**extremement** Correct
**d'id** Find next
**tr** Find next
For me **letter** should not be flagged because it is in a comment. The other flagged words show that TeX accents, as declared in the configuration, are not understood. Worse, the correction of **extremement** I get is **extr\^{e}mement** which is correct. But if I run the spellchecker on the corrected file, the corrected word is flagged as **extr**
I have noticed that the problem does not depend in the encoding. It is the same for UTF-8, OSX and ISO.
Is there a problem with my configuration or is it a problem with the spellchecker ?
Auxiliary question: how to remove "learned" words or to go back to the default dictionary ?
Thanks in advance for your help.
---
Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 13:15:20
|
- **status**: fixed --> closed
- **Version**: 9.2.2 --> 9.2.3
---
** [tickets:#249] Freeze when using command+I**
**Status:** closed
**Created:** Sat Apr 10, 2021 04:20 PM UTC by Marco Comini
**Last Updated:** Sun Apr 11, 2021 07:13 AM UTC
**Owner:** nobody
I'm writing LaTeX sources and frequently when using command+I it freezes. For example on line
~~~
\item In the first two sections, any \emph{indented} text or any text enclosed in \mlst{\%\{} $\langle$code$\rangle$ \mlst{\%\}}
~~~
---
Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 13:15:04
|
- **status**: fixed --> closed
- **Version**: 9.2.2 --> 9.2.3
---
** [tickets:#248] Problems with the spellchecker of Alpha 9.2.2 in TeX Mode for french**
**Status:** closed
**Created:** Mon Mar 29, 2021 11:23 AM UTC by Laurent PRALY
**Last Updated:** Thu May 20, 2021 12:52 PM UTC
**Owner:** nobody
I have problems with the spellcker of Alpha 9.2.2 in TeX Mode for french. Specifically in a text in french, the job is not done correctly in presence of accents or in comments.
Here are the parameters concerning spelling in my Alpha's configuration for the TeX Mode
**Choose an implementatation for spellcheck:** Alpha
**Alpha Preferences: "TeX" Mode > LaTeX Accents**
Accent Smart Escape: Yes
Accents in Comments: No
Bind LaTeX Accents: No
Accente Syntax: \'{e} & \oe{}
**Alpha Preferences: "TeX" Mode Features**
LaTeX Accents: Yes
My test file is:
*\documentclass[a4paper,12pt]{article}
% letter
\begin{document}
Nous \'{e}tudions ici le bouclage dynamique de sortie qui est un sujet extr\^{e}mement extremement vaste. Nous nous li\-mi\-tons \`{a} l'\'{e}nonc\'{e} d'id\'{e}es directrices et \`{a} une pr\'{e}sentation tr\`{e}s in\'{e}gale des r\'{e}sultats, avec beaucoup de d\'{e}tails pour certains et \`{a} peine une \'{e}bauche pour d'autres.
\end{document}*
Here are the flagged words by Alpha after the action of "spellcheck window"
letter
extr
extremement
d'id
tr
For me letter should not be flagged because it is in a comment. The other flagged words show that TeX accents, as declared in the configuration, are not understood. Worse, if I use the spellchecker to correct the word extremement I get extr\^{e}mement which is correct. But if I run the spellchecker on the corrected file, the corrected word is flagged as
extr
I have noticed that the problem does not depend in the encoding. It is the same for UTF-8, OSX and ISO.
Is there a problem with my configuration or is it a problem with the spellchecker ?
Auxiliary question: how to remove "learned" words or to go back to the default dictionary ?
---
Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 13:14:05
|
- **status**: fixed --> closed - **Version**: 9.2.2 --> 9.2.3 --- ** [tickets:#246] Freeze at (26, 70)** **Status:** closed **Created:** Mon Mar 15, 2021 09:00 AM UTC by Jose Miro Julia **Last Updated:** Mon Mar 22, 2021 01:10 PM UTC **Owner:** nobody **Attachments:** - [Captura de pantalla 2021-03-15 a las 9.48.29.jpg](https://sourceforge.net/p/alphacocoa/tickets/246/attachment/Captura%20de%20pantalla%202021-03-15%20a%20las%209.48.29.jpg) (61.8 kB; image/jpeg) I am using Alpha 9.2.2 on OS 10.14.6. I was writting a text in TeX mode and it consistently freezes when I reach line 26, column 70. I have to force it closed. It does not seem to matter what I write or if there is text after. I am sending two attachments with screen captures after freezing. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 13:12:34
|
- **status**: fixed --> closed - **Version**: 9.2.2 --> 9.2.3 --- ** [tickets:#240] Encoding** **Status:** closed **Created:** Sat Oct 24, 2020 07:43 AM UTC by James Connolly **Last Updated:** Sun Mar 07, 2021 10:48 AM UTC **Owner:** nobody Hello, first thanks for all the great work from a long term user (≈1997 on) ! A suggestion :Would it be possible to have a "Default encoding : Check file on open"? This "check file on open" would, upon opening a file, have Alpha check the file's (e.g. BSD "file" command) and use that. And only then open the "Encodings popup" if this fails. At present I have many files in ISO-8859 and the pop-up is working rather hard. And I'm not inclined to convert them all to UTF-8 in order to avoid further potential problems : if Alpha can handle ISO-8859, why not silently continue to do so where appropriate is my thinking. Cheers, James p.s. not files as "bug" nor "task" but as "RFE" which I hope means "suggestion". --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 13:09:52
|
- **status**: open --> fixed --- ** [tickets:#254] Migrating Find Patterns** **Status:** fixed **Created:** Sun May 30, 2021 08:48 PM UTC by John **Last Updated:** Mon May 31, 2021 03:00 PM UTC **Owner:** nobody Where can I find or export the Find and Replace patterns from an old installation of Alpha? It would be very tedious to copy and paste the thirty patters in my old computer to my new computer. Apple's migration assistant did not copy them over. Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 12:58:15
|
- **status**: open --> fixed --- ** [tickets:#253] Restoring Previous Versions Keyboard Shortcuts** **Status:** fixed **Created:** Sun May 30, 2021 08:45 PM UTC by John **Last Updated:** Tue Jun 01, 2021 12:57 PM UTC **Owner:** nobody Is it possible to get back to the old shortcuts from a few versions ago? I don't know exeactly when it happened, but recent versions of Alpha don't have the shortcuts I remember using for the last twenty years. Two shortcuts stick out for me: Uncomment Line and Embrace. I was able to get Uncomment Line back to the Ctrl-D shortcut from days of yore, restoring the system-wide Command-Option-D to hide and unhide the Dock. However, I have not been able to figure out how to restore Ctrl-B for Embrace. If it can't be restored, what shortcut is currently assigned to Embrace? Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-06-01 12:57:42
|
I don't see how *<< a recent version of Alpha had taken back Command-Option-D from the Dock >> *because the bindings that are hijacked by the System do not even reach the application. The only possibility there, is that you defined something different for Hiding/Showing the Dock in the System preferences. Nevermind, I have now defined `ctrl-opt-cmd-D` as the default in Alpha for the *Uncomment Line* command. The Embrace thing seems to be solved now as you explained [here](https://sourceforge.net/p/alphacocoa/tickets/254/#d25c/cf43). So I'm resolving this Ticket as fixed now. --- ** [tickets:#253] Restoring Previous Versions Keyboard Shortcuts** **Status:** open **Created:** Sun May 30, 2021 08:45 PM UTC by John **Last Updated:** Mon May 31, 2021 02:37 PM UTC **Owner:** nobody Is it possible to get back to the old shortcuts from a few versions ago? I don't know exeactly when it happened, but recent versions of Alpha don't have the shortcuts I remember using for the last twenty years. Two shortcuts stick out for me: Uncomment Line and Embrace. I was able to get Uncomment Line back to the Ctrl-D shortcut from days of yore, restoring the system-wide Command-Option-D to hide and unhide the Dock. However, I have not been able to figure out how to restore Ctrl-B for Embrace. If it can't be restored, what shortcut is currently assigned to Embrace? Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: John <uni...@us...> - 2021-05-31 17:29:50
|
Hi Bernard, Thank you for your quick response. I forgot to mention that I’m using Alpha 9.2.3 on Catalina (10.15.7). I’m also running other computers with Mojave (10.14.6) and El Capitan (10.11.6), but nothing later. I have not yet ventured into Big Sur, so I can’t speak to any shortcuts it has hijacked. While I was surprised to find that a recent version of Alpha had taken back Command-Option-D from the Dock, I don’t need you to make any change there. I have already achieved the solution I need using Prefs.tcl. Thank you for letting me know that Embrace is still working on your system. Perhaps that means something is wonky with mine. I will have to investigate more deeply. Thank you also for telling me about the Embrace trigger preference. I think that must be what I’m seeking. However, perhaps my system is more wonky than I thought: The Other Packages pane of the dialog I get when I select Alpha -> Preferences -> Package Preferences has no mention of Embrace or any other trigger preference. It has just a ember-entry field for the Shell history size. Looking at the machine running Mojave, I see it has Alpha 9.1.1 and the Other Packages pane does offer an Embrace trigger. In fact, the Package Preferences dialogs are surprisingly different for such close versions. Stranger still, the machine running El Capitan has Alpha 9.2.3 and its Other Packages pane does have the Embrace trigger. The trigger is still set to B and hitting Ctrl-B works as expected. I guess it is time for a system rebuild, Joy. Best, John > On May 31, 2021, at 10:37 AM, Bernard Desgraupes <bde...@us...> wrote: > > Hi John, > concerning the Uncomment Line binding I can easily change it by default to ctrl-D. Is it the preferred binding for this ? > > Concerning Embrace, I must have missed something because it works perfectly well for me (but I do not have a recent version of OSX because my laptop was stolen and I'm currently working with an older machine with High Sierra). Has ctrl-B been hijacked by Big Sur ? Note that the Embrace package allows you to choose something different via the Embrace-trigger preference found in Alpha ↣ Preferences ↣ Package Preferences ↣ Other packages. --- ** [tickets:#253] Restoring Previous Versions Keyboard Shortcuts** **Status:** open **Created:** Sun May 30, 2021 08:45 PM UTC by John **Last Updated:** Mon May 31, 2021 02:37 PM UTC **Owner:** nobody Is it possible to get back to the old shortcuts from a few versions ago? I don't know exeactly when it happened, but recent versions of Alpha don't have the shortcuts I remember using for the last twenty years. Two shortcuts stick out for me: Uncomment Line and Embrace. I was able to get Uncomment Line back to the Ctrl-D shortcut from days of yore, restoring the system-wide Command-Option-D to hide and unhide the Dock. However, I have not been able to figure out how to restore Ctrl-B for Embrace. If it can't be restored, what shortcut is currently assigned to Embrace? Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: John <uni...@us...> - 2021-05-31 16:34:14
|
Hi Bernard, Thank you very much for explaining this to me. For what it’s worth, I was looking to restore the saved patters from the old machine. I did not dare to hope that the transient recent patterns might be accessible. That is quite nice. As an added bonus, overwriting Alpha’s preferences on the Catalina machine with the preference folder from the El Capitan machine has solved my Embrace problem (Ticket #253). Thank you for suggesting this. Best, John > On May 31, 2021, at 11:00 AM, Bernard Desgraupes <bde...@us...> wrote: > > Hi John, > I'm not sure which patterns you have in mind. Do you mean just the last used patterns or do you mean saved patterns that would be listed at the bottom of the Patterns popup in the Find dialog. > The former are stored in a global variable called recentSearches, the latter are stored in a global array called searchPattern. Both variables are found respectively in the files defs.tcl or arrdefs.tcl located in Alpha's Preferences folder (by default ~/Library/Preferences/Alpha-v9). > > Anyway, what you could do is : > - find an older copy of Alpha's Preferences folder (maybe in a TimeMachine backup or on your older machine) > - quit Alpha > - replace the current Preferences folder by the older one > - restart Alpha > > The order matters: quit Alpha before you overwrite its Preferences folder. --- ** [tickets:#254] Migrating Find Patterns** **Status:** open **Created:** Sun May 30, 2021 08:48 PM UTC by John **Last Updated:** Mon May 31, 2021 03:00 PM UTC **Owner:** nobody Where can I find or export the Find and Replace patterns from an old installation of Alpha? It would be very tedious to copy and paste the thirty patters in my old computer to my new computer. Apple's migration assistant did not copy them over. Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Laurent L. <Lau...@un...> - 2021-05-31 15:51:04
|
Hi Bernard, > On 31 May 2021, at 17:35, Bernard Desgraupes <bde...@or...> wrote: > > Hi Laurent, > > thank you for the input. > >> The port 51954 is not busy on my laptop: the « netstat… » command filtered by « | grep 51954 » returns nothing. >> When I remove the filter, the listed ports do not contain 51954. >> When I start Alpha and repeat the « netstat… » command, the port 60235 appears in the list, associated with …/Alpha.app/…/Alpha . From Alpha, alphaServer::port logically lists the same port. >> >> (Note that when I launch Alpha from Spotlight search, I cannot switch from Terminal to Alpha by command-tab: I need to click the Alpha Icon in the Dock to get within Alpha, where I can then for instance open a Tcl shell window by command-Y. Once a window is open in Alpha, I can switch between Alpha and Terminal by command-tab.) >> > > It is very strange that port 51954 is not busy and still Alpha fails to connect to it. Out of curiosity, could you try the following command (in the Tcl shell) once Alpha is running (using any port it chose): > socket -server ::alphaServer::handleConnect -myaddr 127.0.0.1 51954 > > Does it fail ? No, it does not: sock7fe53e44c610 is returned. (while using in that command the port number listed by alphaServer::port returns Error: couldn’t open socket: address already in use). > Anyway, any port should do (there is absolutely nothing special with 51954). > > Finally, there is no harm using the workaround I indicated and I modified the code in Alpha to implement something equivalent in the future version of Alpha. What I does not understand is that I did not observe that behaviour « time ago » and have no idea what change in my macOS settings could have triggered that « new » behaviour of Alpha… Thank you very much again for the quick support! Laurent > > Cheers, > Bernard > > |
|
From: Bernard D. <bde...@or...> - 2021-05-31 15:36:12
|
Hi Laurent,
thank you for the input.
> The port 51954 is not busy on my laptop: the « netstat… » command filtered by « | grep 51954 » returns nothing.
> When I remove the filter, the listed ports do not contain 51954.
> When I start Alpha and repeat the « netstat… » command, the port 60235 appears in the list, associated with …/Alpha.app/…/Alpha . From Alpha, alphaServer::port logically lists the same port.
>
> (Note that when I launch Alpha from Spotlight search, I cannot switch from Terminal to Alpha by command-tab: I need to click the Alpha Icon in the Dock to get within Alpha, where I can then for instance open a Tcl shell window by command-Y. Once a window is open in Alpha, I can switch between Alpha and Terminal by command-tab.)
>
It is very strange that port 51954 is not busy and still Alpha fails to connect to it. Out of curiosity, could you try the following command (in the Tcl shell) once Alpha is running (using any port it chose):
socket -server ::alphaServer::handleConnect -myaddr 127.0.0.1 51954
Does it fail ?
Anyway, any port should do (there is absolutely nothing special with 51954).
Finally, there is no harm using the workaround I indicated and I modified the code in Alpha to implement something equivalent in the future version of Alpha.
Cheers,
Bernard
|
|
From: Bernard D. <bde...@us...> - 2021-05-31 15:00:54
|
Hi John, I'm not sure which patterns you have in mind. Do you mean just the last used patterns or do you mean saved patterns that would be listed at the bottom of the *Patterns* popup in the *Find* dialog. The former are stored in a global *variable* called *recentSearches*, the latter are stored in a global *array* called *searchPattern*. Both variables are found respectively in the files defs.tcl or arrdefs.tcl located in Alpha's Preferences folder (by default ~/Library/Preferences/Alpha-v9). Anyway, what you could do is : - find an older copy of Alpha's Preferences folder (maybe in a TimeMachine backup or on your older machine) - quit Alpha - replace the current Preferences folder by the older one - restart Alpha The order matters: quit Alpha *before* you overwrite its Preferences folder. --- ** [tickets:#254] Migrating Find Patterns** **Status:** open **Created:** Sun May 30, 2021 08:48 PM UTC by John **Last Updated:** Sun May 30, 2021 08:48 PM UTC **Owner:** nobody Where can I find or export the Find and Replace patterns from an old installation of Alpha? It would be very tedious to copy and paste the thirty patters in my old computer to my new computer. Apple's migration assistant did not copy them over. Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@us...> - 2021-05-31 14:37:19
|
Hi John, concerning the *Uncomment Line* binding I can easily change it by default to ctrl-D. Is it the preferred binding for this ? Concerning Embrace, I must have missed something because it works perfectly well for me (but I do not have a recent version of OSX because my laptop was stolen and I'm currently working with an older machine with High Sierra). Has ctrl-B been hijacked by Big Sur ? Note that the Embrace package allows you to choose something different via the *Embrace-trigger* preference found in *Alpha ↣ Preferences ↣ Package Preferences ↣ Other packages.* --- ** [tickets:#253] Restoring Previous Versions Keyboard Shortcuts** **Status:** open **Created:** Sun May 30, 2021 08:45 PM UTC by John **Last Updated:** Sun May 30, 2021 08:45 PM UTC **Owner:** nobody Is it possible to get back to the old shortcuts from a few versions ago? I don't know exeactly when it happened, but recent versions of Alpha don't have the shortcuts I remember using for the last twenty years. Two shortcuts stick out for me: Uncomment Line and Embrace. I was able to get Uncomment Line back to the Ctrl-D shortcut from days of yore, restoring the system-wide Command-Option-D to hide and unhide the Dock. However, I have not been able to figure out how to restore Ctrl-B for Embrace. If it can't be restored, what shortcut is currently assigned to Embrace? Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Laurent L. <Lau...@un...> - 2021-05-31 07:44:04
|
Hi Bernard, > On 28 May 2021, at 09:30, Bernard Desgraupes <bde...@or...> wrote: > > Hi Laurent, > >> Le 26 mai 2021 à 17:41, Laurent Lamalle <Lau...@un... <mailto:Lau...@un...>> a écrit : >> >> Hi Bernard, >> >>> On 26 May 2021, at 16:44, Bernard Desgraupes <bde...@or... <mailto:bde...@or...>> wrote: >>> >>> Hi Laurent, >>> >>> thank you for reporting this. I don’t know what’s going on there. >>> >>> Is it possible that the port used by the AlphaServer (51954) is already in use on your machine ? >> >> Any idea how I could check that? > > From a Terminal window : > netstat -vanp tcp | grep 51954 > > If it is busy, this command will report something like this: > tcp4 0 0 127.0.0.1.51954 *.* LISTEN 131072 131072 57072 0 > > The next to last number (here 57072) is the PID of the process using this port. > To know which process this is, type for instance (replace 57072 by the appropriate value) : > ps -ax | grep 57072 > > I my case, I get > 57072 ?? 3:45.47 /Applications/Alpha.app/Contents/MacOS/Alpha The port 51954 is not busy on my laptop: the « netstat… » command filtered by « | grep 51954 » returns nothing. When I remove the filter, the listed ports do not contain 51954. When I start Alpha and repeat the « netstat… » command, the port 60235 appears in the list, associated with …/Alpha.app/…/Alpha . From Alpha, alphaServer::port logically lists the same port. (Note that when I launch Alpha from Spotlight search, I cannot switch from Terminal to Alpha by command-tab: I need to click the Alpha Icon in the Dock to get within Alpha, where I can then for instance open a Tcl shell window by command-Y. Once a window is open in Alpha, I can switch between Alpha and Terminal by command-tab.) >>> >>> To help me debug, could you execute the following two commands from the Tcl shell (cmd-Y) once Alpha is running after this activation error: >>> >>> alphaServer::port >>> alphaServer::isRunning >>> >>> >>> Here is for instance what I get on my machine: >>> Welcome to Alpha's AlphaTcl shell. >>> «» alphaServer::port >>> 51954 >> >> I get 59218. >> The default value of 51954 is detected in several files when I run from a terminal « grep -r 51954 /Applications/Alpha.app ». >> But for some reason, it apparently looks interpreted as busy and another port number is (randomly) chosen. > > This confirms that port 51954 is busy and this is not a problem. In that case Alpha, asks for an unused port. Here you got 59218. Nothing to worry about. > >> >>> «» alphaServer::isRunning >>> 1 >> >> I get 1 >> > > Fine. > >>> «» set alphaServer::serverAddress >>> 127.0.0.1 >> >> I get 127.0.0.1 >> > > Fine. > > So at this point everything looks OK and I don’t understand why you get this error message >>>> couldn't open socket: nodename nor servname provided, or not known >>>> while executing >>>> "socket localhost $serverPort" >>> > > during the execution of the proc alphaServer::start. > I have to think more about it. > Is your machine installed behind a firewall or something ? Yes it is, and I also use LittleSnitch to have an eye on connections established. LittleSnitch does not detect anything when Alpha is launched and stopping the network filter in LittleSnitch does not change the behaviour of Alpha launches I observe on my system. > > Meanwhile, to help you out of this and let you have Alpha work normally here is what you can do: > (assuming that your Alpha is in the /Applications folder), edit the file /Applications/Alpha.app/Contents/Resources/Libraries/AlphaTcl/Tcl/Packages/alphaServer.tcl > > and comment out lines 186 to 190. Exactly, replace the following lines: > set initPhase 1 > set sock [socket localhost $serverPort] > close $sock > # Wait until the server has updated serverAddress > vwait ::alphaServer::serverAddress > > > by inserting a # at the beginning of each line like this > > # set initPhase 1 > # set sock [socket localhost $serverPort] > # close $sock > # # Wait until the server has updated serverAddress > # vwait ::alphaServer::serverAddress > > and restart Alpha. > Does that solve the problem ? Yes it does! > This AlphaServer thing is not strictly necessary to have Alpha work properly (unless you need to use a tool like ralpha to edit remote files on a remote machine through ssh). > > I’m sorry for all this trouble. Please don’t be! Alpha is a great tool I have been using for many years, and this disturbing behaviour observed just for some time is minor annoyance with respect to the functionalities I enjoy. Thank you so much for your great work! Laurent > > Bernard > > >> >> To further document the behaviour of the error message window: the « OK » button is initially displayed in blue and I need to click it, changing its aspect to un-coloured transparent, before I can use Alpha. The error message window does not disappear however: it remains with the un-coloured « OK » button. And I « need to search » the new windows that I open in Alpha: command-N results in an Alpha status line message indicating « untitled 'command symbol’1, but the new window is nowhere to be seen first. A sure way to make it appear is for instance to start a search by command-F. >> >> Thank you for your reactivity! >> >> Laurent |
|
From: John <uni...@us...> - 2021-05-30 20:48:31
|
--- ** [tickets:#254] Migrating Find Patterns** **Status:** open **Created:** Sun May 30, 2021 08:48 PM UTC by John **Last Updated:** Sun May 30, 2021 08:48 PM UTC **Owner:** nobody Where can I find or export the Find and Replace patterns from an old installation of Alpha? It would be very tedious to copy and paste the thirty patters in my old computer to my new computer. Apple's migration assistant did not copy them over. Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: John <uni...@us...> - 2021-05-30 20:45:34
|
--- ** [tickets:#253] Restoring Previous Versions Keyboard Shortcuts** **Status:** open **Created:** Sun May 30, 2021 08:45 PM UTC by John **Last Updated:** Sun May 30, 2021 08:45 PM UTC **Owner:** nobody Is it possible to get back to the old shortcuts from a few versions ago? I don't know exeactly when it happened, but recent versions of Alpha don't have the shortcuts I remember using for the last twenty years. Two shortcuts stick out for me: Uncomment Line and Embrace. I was able to get Uncomment Line back to the Ctrl-D shortcut from days of yore, restoring the system-wide Command-Option-D to hide and unhide the Dock. However, I have not been able to figure out how to restore Ctrl-B for Embrace. If it can't be restored, what shortcut is currently assigned to Embrace? Thanks, John --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |
|
From: Bernard D. <bde...@or...> - 2021-05-28 07:30:49
|
Hi Laurent,
> Le 26 mai 2021 à 17:41, Laurent Lamalle <Lau...@un...> a écrit :
>
> Hi Bernard,
>
>> On 26 May 2021, at 16:44, Bernard Desgraupes <bde...@or... <mailto:bde...@or...>> wrote:
>>
>> Hi Laurent,
>>
>> thank you for reporting this. I don’t know what’s going on there.
>>
>> Is it possible that the port used by the AlphaServer (51954) is already in use on your machine ?
>
> Any idea how I could check that?
From a Terminal window :
netstat -vanp tcp | grep 51954
If it is busy, this command will report something like this:
tcp4 0 0 127.0.0.1.51954 *.* LISTEN 131072 131072 57072 0
The next to last number (here 57072) is the PID of the process using this port.
To know which process this is, type for instance (replace 57072 by the appropriate value) :
ps -ax | grep 57072
I my case, I get
57072 ?? 3:45.47 /Applications/Alpha.app/Contents/MacOS/Alpha
>
>>
>> To help me debug, could you execute the following two commands from the Tcl shell (cmd-Y) once Alpha is running after this activation error:
>>
>> alphaServer::port
>> alphaServer::isRunning
>>
>>
>> Here is for instance what I get on my machine:
>> Welcome to Alpha's AlphaTcl shell.
>> «» alphaServer::port
>> 51954
>
> I get 59218.
> The default value of 51954 is detected in several files when I run from a terminal « grep -r 51954 /Applications/Alpha.app ».
> But for some reason, it apparently looks interpreted as busy and another port number is (randomly) chosen.
This confirms that port 51954 is busy and this is not a problem. In that case Alpha, asks for an unused port. Here you got 59218. Nothing to worry about.
>
>> «» alphaServer::isRunning
>> 1
>
> I get 1
>
Fine.
>> «» set alphaServer::serverAddress
>> 127.0.0.1
>
> I get 127.0.0.1
>
Fine.
So at this point everything looks OK and I don’t understand why you get this error message
>>> couldn't open socket: nodename nor servname provided, or not known
>>> while executing
>>> "socket localhost $serverPort"
>>
during the execution of the proc alphaServer::start.
I have to think more about it.
Is your machine installed behind a firewall or something ?
Meanwhile, to help you out of this and let you have Alpha work normally here is what you can do:
(assuming that your Alpha is in the /Applications folder), edit the file /Applications/Alpha.app/Contents/Resources/Libraries/AlphaTcl/Tcl/Packages/alphaServer.tcl
and comment out lines 186 to 190. Exactly, replace the following lines:
set initPhase 1
set sock [socket localhost $serverPort]
close $sock
# Wait until the server has updated serverAddress
vwait ::alphaServer::serverAddress
by inserting a # at the beginning of each line like this
# set initPhase 1
# set sock [socket localhost $serverPort]
# close $sock
# # Wait until the server has updated serverAddress
# vwait ::alphaServer::serverAddress
and restart Alpha.
Does that solve the problem ?
This AlphaServer thing is not strictly necessary to have Alpha work properly (unless you need to use a tool like ralpha to edit remote files on a remote machine through ssh).
I’m sorry for all this trouble.
Bernard
>
> To further document the behaviour of the error message window: the « OK » button is initially displayed in blue and I need to click it, changing its aspect to un-coloured transparent, before I can use Alpha. The error message window does not disappear however: it remains with the un-coloured « OK » button. And I « need to search » the new windows that I open in Alpha: command-N results in an Alpha status line message indicating « untitled 'command symbol’1, but the new window is nowhere to be seen first. A sure way to make it appear is for instance to start a search by command-F.
>
> Thank you for your reactivity!
>
> Laurent
>
|
368 messages has been excluded from this view by a project administrator.
){kind=link}