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: jwq <jw...@us...> - 2019-01-08 21:58:59
|
The Release Notes are euphemistic at best; the crash which *explains* the change appears to be entirely undocumented. The fundamental problem is that a fix to a bug - which I do want - has been conflated with non-cosmetic changes to the UI - which I don't want. The popup menus: * no longer look the same - they don't look like popups at all * are located on the opposite side of the window * no longer convey the state information they used to convey Hardly cosmetic: they are unrecognizable. This doesn't appear to be *the minimum possible disturbance to the GUI in fixing the bug.* I would really like the latter, please, because I very much appreciate the work you put into bug-fixes. --- ** [tickets:#206] User Interface Changes Capriciously in Minor-Point-Update** **Status:** closed **Created:** Sat Nov 24, 2018 10:42 PM UTC by jwq **Last Updated:** Sun Dec 09, 2018 05:31 PM UTC **Owner:** nobody **Attachments:** - [Alpha 9.0.1.png](https://sourceforge.net/p/alphacocoa/tickets/206/attachment/Alpha%209.0.1.png) (29.7 kB; image/png) - [Alpha 9.0.png](https://sourceforge.net/p/alphacocoa/tickets/206/attachment/Alpha%209.0.png) (28.2 kB; image/png) Alpha 9.0.1 has a new UI for mode selection, etc., per the attachments. The UI wasn't *broken* and this change adds *no* value for me as a user; it's not even post-hoc explained in the release notes. Rather, having the UI change capriciously in a minor-point update (9.0 → 9.0.1) is irksome. I appreciate the bug fixes - and all the hard work that is required for them. Please don't tarnish my appreciation with UI annoyances. Please. --- 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: jwq <jw...@us...> - 2019-01-08 20:54:54
|
I'm afraid that there isn't an `Alpha` folder in `~/Library/Logs/` only `AlphaTcl`, across multiple installations. I've just re-tested, on mulitple installs, and it fails silently. --- ** [tickets:#204] Update Functionality: "Download and Install" Silently Fails to Install** **Status:** open **Created:** Sat Nov 24, 2018 10:06 PM UTC by jwq **Last Updated:** Thu Dec 13, 2018 09:03 AM UTC **Owner:** nobody Alpha 9.0 displayed a dialog stating that 9.0.1 is available, containing a button "Download and Install". When clicked, Alpha 9.0 downloads Alpha_9.0.1.dmg.zip [to the system-default download folder] and then, on completion, displays a "Download completed" message in the message bar and triggers the system alert sound. No install. A minor pest, but it would be nice to fix this for future versions so update functions as desired. --- 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: Joachim K. <ko...@ma...> - 2019-01-03 08:24:17
|
> I need more input to debug this updating problem. I’m surprised that > you have a message related to vcsRun(done) because the updating > process does not use the svn console any longer. I saw the new update status window once, but then I got an error, and then I downloaded a new Alpha and afterwards I only got the old svnConsole. > Furthermore there is no such command as alpha::restartAlpha and I > can’t figure out where it comes from. I see. Surely I am using an outdated binary, but I just downloaded it from SoruceForge, so maybe there is an old version there? > So I have two questions: > - how did you trigger the developer checkout (is it just by selecting > the appropriate command from the "Update Alpha" menu) ? Yes. > - if the new mechanism got an error, you should have something in the > file ~/Library/Logs/AlphaTcl/upgradeAlpha.log. Is there something > useful therein ? No, there is no such file. > > Now, regarding the relaunch issue, it just means that the core has to > be recompiled. As a workaround, you could try to modify the > minCoreVersion variable in the file AlphaVersionInfo.tcl and set it > to 9.0.2: variable minCoreVersion 9.0.2 This will avoid the annoying > message about Alpha being too old, but I can’t guarantee that > everything will work properly since the core would be left > unchanged. OK, this worked (after manual quit and relaunch). Cheers, Joachim. |
From: Bernard D. <bde...@or...> - 2019-01-02 08:17:13
|
Hi Joachim, happy new year! I need more input to debug this updating problem. I’m surprised that you have a message related to vcsRun(done) because the updating process does not use the svn console any longer. Furthermore there is no such command as alpha::restartAlpha and I can’t figure out where it comes from. So I have two questions: - how did you trigger the developer checkout (is it just by selecting the appropriate command from the "Update Alpha" menu) ? - if the new mechanism got an error, you should have something in the file ~/Library/Logs/AlphaTcl/upgradeAlpha.log. Is there something useful therein ? Now, regarding the relaunch issue, it just means that the core has to be recompiled. As a workaround, you could try to modify the minCoreVersion variable in the file AlphaVersionInfo.tcl and set it to 9.0.2: variable minCoreVersion 9.0.2 This will avoid the annoying message about Alpha being too old, but I can’t guarantee that everything will work properly since the core would be left unchanged. Cheers, Bernard Le 1 janv. 2019 à 21:42, Joachim Kock <ko...@ma...> a écrit : > Hi Bernard, > > happy new year! > > I still have problems with the update > mechanism, developer checkout :-( > > Downloaded latest Alpha, > did developer checkout (to revision 1607), > got error > > can't set "vcsRun(done)": invalid command > name "alpha::restartAlpha" > > Then, upon relaunch: > > This version of Alpha (9.0.2) is too old. > Minimum required version is 9.0.3d1. > Upgrade from https://sourceforge.net/projects/alphacocoa > Alpha must quit now. > > (I am perfectly happy with 9.0.2 otherwise.) > > Cheers, > Joachim. > > > _______________________________________________ > AlphaCocoa-devel mailing list > Alp...@li... > https://lists.sourceforge.net/lists/listinfo/alphacocoa-devel |
From: Joachim K. <ko...@ma...> - 2019-01-01 21:42:30
|
Hi Bernard, happy new year! I still have problems with the update mechanism, developer checkout :-( Downloaded latest Alpha, did developer checkout (to revision 1607), got error can't set "vcsRun(done)": invalid command name "alpha::restartAlpha" Then, upon relaunch: This version of Alpha (9.0.2) is too old. Minimum required version is 9.0.3d1. Upgrade from https://sourceforge.net/projects/alphacocoa Alpha must quit now. (I am perfectly happy with 9.0.2 otherwise.) Cheers, Joachim. |
From: Bernard D. <bde...@us...> - 2018-12-22 16:24:59
|
Thank you Joachim for looking into this. I have just committed your patch to the repository ([rev. 1607](https://sourceforge.net/p/alphacocoa/code/1607/)). --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Sat Dec 22, 2018 04:00 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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: Joachim K. <jk...@us...> - 2018-12-22 16:00:45
|
Hi again, a miminal fix is to add these three lines to tetexComm.tcl, in line 2080 (after the other entries of the patList): # The following is specifically to remove an unbalanced # message issued by the 'physics' package: lappend patList {\. Defining command [^\r\n]*} I have tested it. Would you apply the patch, Bernard? I have some trouble with svn :-( In the long run, I want to revise the whole logfile scanning mechanism. It is not fair that this error message should bother innocent users who might not even use error browsing. It should be decoupled from the general tex run and only be performed on the fly when error browsing is invoked. And the error handling should be more graceful. I will implement this structural change and test it thoroughly over the coming weeks. Cheers, Joachim. --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 09:14 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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...> - 2018-12-21 21:54:06
|
Hi Matt, In my experience, once this happens the unbalanced parameters sit in the log file and kills all subsequent runs of LaTeX. It may not solve the problem but, if you haven’t done so, delete the existing log file (I usually throw out everything except the source files) and start the process as though it is the first time it has been run. That often helps, although is a workaround rather than a real fix for the problem. I hope this helps. Cheers, Chris. From: Joachim Kock via AlphaCocoa-devel <alp...@li...> Reply-To: "[alphacocoa:tickets]" <21...@ti...> Date: Saturday, 22 December 2018 at 8:15 am To: "alp...@li..." <alp...@li...> Cc: Joachim Kock <jk...@us...> Subject: [Alphacocoa-devel] [alphacocoa:tickets] #211 TeX Mode error using standard package My last sentence does not make sense, because all packages are of course input from the main file. But it is true that I will look into a better fix. ________________________________ [tickets:#211]<https://sourceforge.net/p/alphacocoa/tickets/211/> TeX Mode error using standard package Status: open Created: Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad Last Updated: Fri Dec 21, 2018 09:12 PM UTC Owner: nobody Attachments: * solnmanual.log<https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log> (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. ________________________________ Sent from sourceforge.net because 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. --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 09:14 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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: Joachim K. <jk...@us...> - 2018-12-21 21:14:44
|
My last sentence does not make sense, because all packages are of course input from the main file. But it is true that I will look into a better fix. --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 09:12 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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: Joachim K. <jk...@us...> - 2018-12-21 21:12:28
|
Thanks for reporting this and thanks for the log file. There is indeed an unbalanced parenthesis in line 565 of the log file, issued by the package as part of some message from the package. A minimal patch would consist in taking exception for this kind of message. But potentially other packages could issue messages with unbalanced parentheses and there is no point in trying to detect them in packages, since presumably packages have no errors (the parens matching is only for the sake of error browsing), so a more thorough fix would consist in only starting the parens matching business once tex actually begins reading the main input file. I will look into this. Cheers, Joachim. --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 07:26 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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: Matt H. <mjh...@us...> - 2018-12-21 19:48:51
|
Sure thing. Here you are > On Dec 21, 2018, at 2:22 PM, Bernard Desgraupes <bde...@us...> wrote: > > Thank you for reporting this. Could you provide a minimal tex file to reproduce the problem ? > > [tickets:#211] <https://sourceforge.net/p/alphacocoa/tickets/211/> TeX Mode error using standard package > > Status: open > Created: Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad > Last Updated: Fri Dec 21, 2018 05:54 PM UTC > Owner: nobody > Attachments: > > solnmanual.log <https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log> (71.3 kB; application/octet-stream) > When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: > "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." > > It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. > > Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/alphacocoa/tickets/211/ <https://sourceforge.net/p/alphacocoa/tickets/211/> > To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ <https://sourceforge.net/auth/subscriptions/> --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 07:26 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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: Matt H. <mjh...@us...> - 2018-12-21 19:26:19
|
Sure thing. Attachments: - [test.tex](https://sourceforge.net/p/alphacocoa/tickets/_discuss/thread/a411a07555/9fa1/attachment/test.tex) (99 Bytes; application/x-tex) --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 07:22 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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...> - 2018-12-21 19:22:37
|
Thank you for reporting this. Could you provide a minimal tex file to reproduce the problem ? --- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 05:54 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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: Matt H. <mjh...@us...> - 2018-12-21 17:54:48
|
--- ** [tickets:#211] TeX Mode error using standard package** **Status:** open **Created:** Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad **Last Updated:** Fri Dec 21, 2018 05:54 PM UTC **Owner:** nobody **Attachments:** - [solnmanual.log](https://sourceforge.net/p/alphacocoa/tickets/211/attachment/solnmanual.log) (71.3 kB; application/octet-stream) When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation: "Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report." It happens on each run of pdfLaTeX and on all computers that I have been able to test this on. --- 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...> - 2018-12-21 12:31:55
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#202] Navigate in a fileset with an explorer-like window** **Status:** closed **Created:** Mon Nov 19, 2018 09:21 AM UTC by Sylvain Loiseau **Last Updated:** Mon Dec 17, 2018 08:50 AM UTC **Owner:** nobody This is a RFE. When using fileset, I find sometime that it would be comfortable to have a view of the files of the fileset in a explorer-like or finder-like window, in witch you can select the files to be opened. Indeed, when searching in a fileset, it may sometime turn out to be boring to have to go back to the fileset menu and to the submenu corresponding to the (possibly deeply nested) directory I am currently searching in. Another editor, whose name start with a T and end ends with "Mate" has something quite usefull: you can open a directory and have its structure displayed on the side of the window (never in my life have I dared to use this program, I was told about it by friends). Best, Sylvain --- 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...> - 2018-12-21 12:31:03
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#209] Window position/size saved state is altered when re-opening a document** **Status:** closed **Created:** Tue Dec 11, 2018 07:09 PM UTC by Greg Dunn **Last Updated:** Fri Dec 14, 2018 07:54 AM UTC **Owner:** nobody When changing something like the wrapping and/or window size/position, recording the window state and then saving the document, the document (when re-opened) displays with the top left corner of the window displaced downward by about 60 pixels. The lower left/right coordinates aren't disturbed (so the window ends up being a little smaller). Subsequent opens of saved documents retain this offset - I had thought perhaps it was attempting to tile or overlap the windows, but it seems just to be applying a fixed offset from the upper left corner of the screen to the top left of the document window. Curiously, if I reduce the window size by resizing from the top of the window, making it yet smaller, that state seems to be retained. Resizing it so that the top nestles just below the status bar (where a default document is placed) and then saving does not retain the setting, but causes the window top left to be displaced downward again on re-open. OS X Yosemite 10.10.5, Alpha 9.0.1 (8030) --- 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...> - 2018-12-21 12:30:51
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#208] RFE - add chosen text wrapping value to document saved window state** **Status:** closed **Created:** Tue Dec 11, 2018 07:01 PM UTC by Greg Dunn **Last Updated:** Fri Dec 14, 2018 04:49 PM UTC **Owner:** nobody **Attachments:** - [text wrapping.png](https://sourceforge.net/p/alphacocoa/tickets/208/attachment/text%20wrapping.png) (19.9 kB; image/png) I would like to see the "text wrapping" preference for a document be included in the "saved window state" parameters so that the document's chosen text wrapping is saved with the document and restored when the document is re-opened.. --- 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...> - 2018-12-21 12:30:43
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#205] Emacs Command "Yank" Non-functional** **Status:** closed **Created:** Sat Nov 24, 2018 10:23 PM UTC by jwq **Last Updated:** Mon Dec 10, 2018 11:04 AM UTC **Owner:** nobody Neither the menu item Edit → Emacs Commands → Yank nor the keyboard shortcut Ctrl-Y inserts the text most recently killed by, e.g. the Kill Line command (Ctrl-K). Worked in AlphaX, would be nice to have for AlphaCocoa. --- 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...> - 2018-12-21 12:30:35
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#203] "Display Palettes" in Markdown mode: two bugs and one RFE** **Status:** closed **Created:** Tue Nov 20, 2018 02:42 PM UTC by Sylvain Loiseau **Last Updated:** Mon Dec 10, 2018 07:05 PM UTC **Owner:** nobody When "Display Palettes" is activated in Mardown mode, two things seem strange: - If I click again on "Display Palettes", only one palette disapears. Beside, I suggest that the menu item swith to "Hide Palettes" once activated. - If I switch to another document (while one Markdown file is open, with Palettes shown), the "Mardown" menu disapear from the menu bar, but the Palettes are still visible Beside, one RFE (maybe not a good one) : to have the shortcut displayed on the palette beside the function names. Best, Sylvain --- 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...> - 2018-12-21 12:30:29
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#201] Offer to create a fileset with a directory dragged onto Alpha Icon** **Status:** closed **Created:** Mon Nov 19, 2018 09:11 AM UTC by Sylvain Loiseau **Last Updated:** Mon Dec 10, 2018 07:16 AM UTC **Owner:** nobody This is a RFE. When dragging a folder on the Alpha Icon, the "chose encoding" dialog appears. The user has no other option but to select "cancel" since no encoding is going to be correct... I'm wondering whether it could'nt be a nice feature to open the "create fileset" dialog in order to offer the user, when a folder is droped onto the Alpha Icon, the option to create a fileset with this dicrectory (/hierarchy). Best, Sylvain --- 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...> - 2018-12-21 12:30:23
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#200] xml::electricClosingAngleBracket : two issues** **Status:** closed **Created:** Mon Nov 19, 2018 08:57 AM UTC by Sylvain Loiseau **Last Updated:** Mon Dec 10, 2018 03:18 PM UTC **Owner:** nobody In XML mode, xml::electricClosingAngleBracket offers to insert the end-tag of an XML element while typing the closing ">" of the start-tag. I have noted two issues: - with prefixed element name (QName), for instance "xsl:param", only "xsl" is inserted in the end tag. It is due to the regexp used for matching the start tag: `regexp -- {[\w]+} $tag tag` l. 511 of Modes/XML Modes/xmlMode.tcl I think it could be turned into: `regexp -- {[\w]*:?[\w]+} $tag tag` - second ; when typing a start-tag at the very end of a document (the cursor is at the last position), the closing tag is not inserted. I havn't been able to trace the issue. It may be a common situation to enter the root element of a document and to expect it to be closed also. Best, Sylvain --- 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...> - 2018-12-21 12:30:16
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#198] unsaved change when typesetting in tex mode** **Status:** closed **Created:** Tue Nov 13, 2018 11:16 AM UTC by Sylvain Loiseau **Last Updated:** Mon Dec 10, 2018 02:32 PM UTC **Owner:** nobody When typesetting a buffer in tex mode that have unsaved changes, a dialog appears: "The window 'xxx' has unsaved changes"... Do you want to save it before typesetting? The odd point is that the user is left with only one button "Save and Typeset", the question in the dialog being then rather rhetorical :-) Maybe a "abort" button would be more coherent, even if it will not be very useful in practice. --- 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...> - 2018-12-21 12:29:47
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#197] Default behaviour of "Clear Undo Stack on Save"** **Status:** closed **Created:** Tue Nov 13, 2018 11:12 AM UTC by Sylvain Loiseau **Last Updated:** Mon Dec 17, 2018 06:36 AM UTC **Owner:** nobody A very minor point: by default, the Undo Stack is cleared on save. I know this is a preference that can be changed in global preference, Document, "Clear Undo Stack on Save". However, I'm wondering whether the default behaviour should not be to preserve the stack on save. This is the behaviour in most app, and before realizing it is different in Alpha -- and changing it in the pref -- one can lost work. --- 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...> - 2018-12-21 12:28:53
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#196] Enter does not wok on menu item** **Status:** closed **Created:** Fri Nov 09, 2018 12:57 PM UTC by Sylvain Loiseau **Last Updated:** Wed Dec 12, 2018 04:35 PM UTC **Owner:** nobody Having selected any menu entry with either the mouse or the keyboard and hitting "enter" does not trigger this menu item. --- 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...> - 2018-12-21 12:28:47
|
- **status**: fixed --> closed - **Version**: 9.0.1 --> 9.0.2 --- ** [tickets:#194] Same file opened twice with the "File->Open..." dialog** **Status:** closed **Created:** Thu Nov 08, 2018 03:21 PM UTC by Sylvain Loiseau **Last Updated:** Mon Dec 10, 2018 01:18 PM UTC **Owner:** nobody If I drag (the icon of) a file on the Alpha icon, and if this file is already open, Alpha does not open it a second time a bring the corresponding buffer on the foreground. The same thing occurs if I select an already opened file in the "File->Open Recent" list. However, if I select a file already opened in the "File->Open..." dialog, it open a new buffer of that file whose name is suffixed with <2>. At some point (I cannot determinate when exactly), the "Open Recent" list start working the same way: each time I select the same file in the list, it open a new buffer, incrementing the <n> suffix. Best, Sylvain --- 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. |