gambas-devel Mailing List for Gambas
Brought to you by:
gambas
This list is closed, nobody may subscribe to it.
2003 |
Jan
(8) |
Feb
(17) |
Mar
(10) |
Apr
(19) |
May
(39) |
Jun
(82) |
Jul
(12) |
Aug
(21) |
Sep
(50) |
Oct
(21) |
Nov
(45) |
Dec
(42) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(83) |
Feb
(58) |
Mar
(18) |
Apr
(63) |
May
(33) |
Jun
(36) |
Jul
(42) |
Aug
(154) |
Sep
(90) |
Oct
(117) |
Nov
(120) |
Dec
(73) |
2005 |
Jan
(231) |
Feb
(117) |
Mar
(157) |
Apr
(94) |
May
(42) |
Jun
(41) |
Jul
(62) |
Aug
(75) |
Sep
(46) |
Oct
(72) |
Nov
(74) |
Dec
(25) |
2006 |
Jan
(34) |
Feb
(18) |
Mar
(84) |
Apr
(40) |
May
(19) |
Jun
(43) |
Jul
(59) |
Aug
(101) |
Sep
(123) |
Oct
(49) |
Nov
(80) |
Dec
(18) |
2007 |
Jan
(28) |
Feb
|
Mar
(1) |
Apr
(25) |
May
(11) |
Jun
(8) |
Jul
(9) |
Aug
(12) |
Sep
(13) |
Oct
(17) |
Nov
(73) |
Dec
(15) |
2008 |
Jan
(108) |
Feb
(34) |
Mar
(112) |
Apr
(82) |
May
(56) |
Jun
(74) |
Jul
(31) |
Aug
(72) |
Sep
(47) |
Oct
(9) |
Nov
(17) |
Dec
(11) |
2009 |
Jan
(139) |
Feb
(33) |
Mar
(16) |
Apr
(10) |
May
(11) |
Jun
(6) |
Jul
(86) |
Aug
(50) |
Sep
(13) |
Oct
(27) |
Nov
(59) |
Dec
(243) |
2010 |
Jan
(61) |
Feb
(31) |
Mar
(7) |
Apr
(22) |
May
(15) |
Jun
(12) |
Jul
(13) |
Aug
(33) |
Sep
(5) |
Oct
(33) |
Nov
(27) |
Dec
(19) |
2011 |
Jan
(16) |
Feb
(41) |
Mar
(7) |
Apr
(13) |
May
|
Jun
|
Jul
(10) |
Aug
(67) |
Sep
(7) |
Oct
(23) |
Nov
(5) |
Dec
(5) |
2012 |
Jan
(40) |
Feb
(53) |
Mar
(6) |
Apr
(35) |
May
(50) |
Jun
(19) |
Jul
(43) |
Aug
(110) |
Sep
(71) |
Oct
(24) |
Nov
(13) |
Dec
(18) |
2013 |
Jan
(13) |
Feb
(9) |
Mar
(29) |
Apr
(6) |
May
(18) |
Jun
(4) |
Jul
(24) |
Aug
(25) |
Sep
(30) |
Oct
(30) |
Nov
(8) |
Dec
(6) |
2014 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(28) |
May
(6) |
Jun
(12) |
Jul
(8) |
Aug
(14) |
Sep
(128) |
Oct
(31) |
Nov
(27) |
Dec
(19) |
2015 |
Jan
(5) |
Feb
(3) |
Mar
(11) |
Apr
(4) |
May
(10) |
Jun
|
Jul
(1) |
Aug
(11) |
Sep
(20) |
Oct
(19) |
Nov
|
Dec
(6) |
2016 |
Jan
(1) |
Feb
(1) |
Mar
(11) |
Apr
(4) |
May
|
Jun
(7) |
Jul
|
Aug
|
Sep
(6) |
Oct
(22) |
Nov
(6) |
Dec
(8) |
2017 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(6) |
Jul
(28) |
Aug
(87) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
From: Benoît M. <ga...@us...> - 2017-10-15 19:51:43
|
Hi, Thanks to Christof Thalhofer and Hostsharing.net, we have now a dedicated mailing-list server for Gambas, and so we can leave SourceForge mailing-list. Since a few weeks, SourceForge prevents me from accessing the list of subscribers, so people have to manually subscribe to the new mailing-list one by one. The server is hosted at: http://lists.gambas-basic.org There is one mailing-list at the moment, named "User". Additional mailing-list will be able to be added freely according to the needs. The Gitlab Gambas repository will now be able to send all commits to a new "Commit" mailing-list. The Bug Tracker will send its mails to the "User" mailing-lists, as everybody may be interested in bug fixes. Once that done, the SourceForge mailing-list will be deactivated. I will update the website as soon as possible. The website is now the only thing hosted by SourceForge. If you have any questions, please ask. Best regards, -- Benoît Minisini |
From: PICCORO M. L. <mck...@gm...> - 2017-09-16 15:13:28
|
you are working hard right! take easy! you are doing a great work! (but i noted the amount of "new bugs" jajaja) Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-09-15 19:02 GMT-04:00 Benoît Minisini <ga...@us...>: > Le 16/09/2017 à 00:55, Benoît Minisini via Gambas-devel a écrit : > >> Le 15/09/2017 à 20:32, PICCORO McKAY Lenz a écrit : >> >>> today i created to feature request and i notes saved as bug 1 and bug >>> 2... >>> >>> new look are great, but new numbering seems will conflicts with ohter >>> existing bugs right? >>> >>> >>> Lenz McKAY Gerardo (PICCORO) >>> http://qgqlochekone.blogspot.com >>> >>> >> @#$*!!! This is a new bug... krszmlnkrz... >> >> > It should be fixed now. > > -- > Benoît Minisini > |
From: Benoît M. <ga...@us...> - 2017-09-15 23:02:21
|
Le 16/09/2017 à 00:55, Benoît Minisini via Gambas-devel a écrit : > Le 15/09/2017 à 20:32, PICCORO McKAY Lenz a écrit : >> today i created to feature request and i notes saved as bug 1 and bug >> 2... >> >> new look are great, but new numbering seems will conflicts with ohter >> existing bugs right? >> >> >> Lenz McKAY Gerardo (PICCORO) >> http://qgqlochekone.blogspot.com >> > > @#$*!!! This is a new bug... krszmlnkrz... > It should be fixed now. -- Benoît Minisini |
From: Benoît M. <ga...@us...> - 2017-09-15 22:55:18
|
Le 15/09/2017 à 20:32, PICCORO McKAY Lenz a écrit : > today i created to feature request and i notes saved as bug 1 and bug 2... > > new look are great, but new numbering seems will conflicts with ohter > existing bugs right? > > > Lenz McKAY Gerardo (PICCORO) > http://qgqlochekone.blogspot.com > @#$*!!! This is a new bug... krszmlnkrz... -- Benoît Minisini |
From: PICCORO M. L. <mck...@gm...> - 2017-09-15 18:32:59
|
today i created to feature request and i notes saved as bug 1 and bug 2... new look are great, but new numbering seems will conflicts with ohter existing bugs right? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com |
From: Tony M. <tmo...@aj...> - 2017-08-29 13:13:50
|
Another approach would be to use termios to detect whether the terminal is in raw or canonical mode and then translate CR to LF appropriately. On 2017-08-29 12:48 AM, Tony Morehen wrote: > I did some more research into this issue and it seems related to what > mode the tty is in. There is canonical mode, which is the standard > mode using readline ie with line editing and, it seems, CR to NL > translation. The other mode is raw mode, where keyboard input is sent > directly to the application. The read command uses raw mode. > > So I tried experimenting with stty. stty raw gave me the step effect > on output but the enter keypress appeared to behave normally ie. stty > -raw fixed the step effect but then I found that enter now worked in > the full screen cli text editors, read, and password prompts! A > work-around for this issue. > > It turns out that stty raw is not symmetric. Further experimenting > showed that sending stty icrnl to the terminal on initialization fixes > the enter bug. > > This suggests that adding a property such as EnableCRtoNL to > Process.term could be a good approach for a long-term fix. > EnableCRtoNL would toggle a flag in the termios structure related to > Process.term. > > > On 2017-08-28 11:50 AM, Tony Morehen wrote: >> Mea Culpa. >> >> We need to revert this change. >> >> While the fix I proposed did fix read and git's username/password >> prompts, it broke several terminal-based text editors: nano, joe and >> micro were the one's I tested. For the editors, you now need to >> press ctrl-M to get a new line. Emacs though works fine. >> >> As far as read and git are concerned, you can press ctrl-J to get a >> new line. As well "read -e" will accept ctrl-M as new line. >> >> Obviously, there is no simple fix. TerminalView needs to detect >> whether the application is expecting keyboard input and so will work >> only with ctrl-M or file-type input (ctrl-J). I'll follow up on this. >> >> Sorry for the mess. >> Tony >> >> >> On 2017-08-25 05:10 PM, Benoît Minisini wrote: >>> Le 25/08/2017 à 22:32, Tony Morehen a écrit : >>>> When using terminalview in a terminal program, you cannot respond >>>> to prompts such as git's requests for username and password. Bash's >>>> built-in read command also doesn't work properly. You can type in >>>> text ok, but when you press enter, all you see is "^M" and nothing >>>> happens. All you can do is press control-C to abort. >>>> >>>> To duplicate: >>>> 1) run FTerminalView in gb.form.terminal >>>> 2) enter "read -p '>' >>>> 3) type some text, press enter >>>> 4) all you see is your text + ^M >>>> >>>> Potential fix: >>>> >>>> line 673 in TerminalFilter_VT100, change the False action of the >>>> IIf from "\r" to "\n" >>>> >>>> gb.form.terminal must be driving you guys nuts. >>>> >>>> Cheers, >>>> Tony >>>> >>> >>> OK, fixed. >>> >> >> >> >> ------------------------------------------------------------------------------ >> >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Gambas-devel mailing list >> Gam...@li... >> https://lists.sourceforge.net/lists/listinfo/gambas-devel > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gambas-devel mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gambas-devel |
From: Tony M. <tmo...@aj...> - 2017-08-29 04:49:01
|
I did some more research into this issue and it seems related to what mode the tty is in. There is canonical mode, which is the standard mode using readline ie with line editing and, it seems, CR to NL translation. The other mode is raw mode, where keyboard input is sent directly to the application. The read command uses raw mode. So I tried experimenting with stty. stty raw gave me the step effect on output but the enter keypress appeared to behave normally ie. stty -raw fixed the step effect but then I found that enter now worked in the full screen cli text editors, read, and password prompts! A work-around for this issue. It turns out that stty raw is not symmetric. Further experimenting showed that sending stty icrnl to the terminal on initialization fixes the enter bug. This suggests that adding a property such as EnableCRtoNL to Process.term could be a good approach for a long-term fix. EnableCRtoNL would toggle a flag in the termios structure related to Process.term. On 2017-08-28 11:50 AM, Tony Morehen wrote: > Mea Culpa. > > We need to revert this change. > > While the fix I proposed did fix read and git's username/password > prompts, it broke several terminal-based text editors: nano, joe and > micro were the one's I tested. For the editors, you now need to press > ctrl-M to get a new line. Emacs though works fine. > > As far as read and git are concerned, you can press ctrl-J to get a > new line. As well "read -e" will accept ctrl-M as new line. > > Obviously, there is no simple fix. TerminalView needs to detect > whether the application is expecting keyboard input and so will work > only with ctrl-M or file-type input (ctrl-J). I'll follow up on this. > > Sorry for the mess. > Tony > > > On 2017-08-25 05:10 PM, Benoît Minisini wrote: >> Le 25/08/2017 à 22:32, Tony Morehen a écrit : >>> When using terminalview in a terminal program, you cannot respond to >>> prompts such as git's requests for username and password. Bash's >>> built-in read command also doesn't work properly. You can type in >>> text ok, but when you press enter, all you see is "^M" and nothing >>> happens. All you can do is press control-C to abort. >>> >>> To duplicate: >>> 1) run FTerminalView in gb.form.terminal >>> 2) enter "read -p '>' >>> 3) type some text, press enter >>> 4) all you see is your text + ^M >>> >>> Potential fix: >>> >>> line 673 in TerminalFilter_VT100, change the False action of the IIf >>> from "\r" to "\n" >>> >>> gb.form.terminal must be driving you guys nuts. >>> >>> Cheers, >>> Tony >>> >> >> OK, fixed. >> > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gambas-devel mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gambas-devel |
From: Tony M. <tmo...@aj...> - 2017-08-28 15:50:36
|
Mea Culpa. We need to revert this change. While the fix I proposed did fix read and git's username/password prompts, it broke several terminal-based text editors: nano, joe and micro were the one's I tested. For the editors, you now need to press ctrl-M to get a new line. Emacs though works fine. As far as read and git are concerned, you can press ctrl-J to get a new line. As well "read -e" will accept ctrl-M as new line. Obviously, there is no simple fix. TerminalView needs to detect whether the application is expecting keyboard input and so will work only with ctrl-M or file-type input (ctrl-J). I'll follow up on this. Sorry for the mess. Tony On 2017-08-25 05:10 PM, Benoît Minisini wrote: > Le 25/08/2017 à 22:32, Tony Morehen a écrit : >> When using terminalview in a terminal program, you cannot respond to >> prompts such as git's requests for username and password. Bash's >> built-in read command also doesn't work properly. You can type in >> text ok, but when you press enter, all you see is "^M" and nothing >> happens. All you can do is press control-C to abort. >> >> To duplicate: >> 1) run FTerminalView in gb.form.terminal >> 2) enter "read -p '>' >> 3) type some text, press enter >> 4) all you see is your text + ^M >> >> Potential fix: >> >> line 673 in TerminalFilter_VT100, change the False action of the IIf >> from "\r" to "\n" >> >> gb.form.terminal must be driving you guys nuts. >> >> Cheers, >> Tony >> > > OK, fixed. > |
From: PICCORO M. L. <mck...@gm...> - 2017-08-26 22:03:31
|
Git uses two main types of tags: lightweight and annotated. Gitlab had predefined lightweithg and github annotated.. how are this doing by administrations? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-08-26 18:01 GMT-04:00 Christof Thalhofer <ch...@de...>: > Am 26.08.2017 um 23:21 schrieb Benoît Minisini: > > > By the way, I'm currently thinking that the easier and the better may be > > a 3.11 very fast, as soon as the TerminalView and process management is > > stabilized (it seems now). Because there are far more than these 3 fixed > > to merge. > > No problem, I would stay at 3.9 till then ... > > > Alles Gute > > Christof Thalhofer > > -- > Dies ist keine Signatur > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gambas-devel mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gambas-devel > > |
From: Christof T. <ch...@de...> - 2017-08-26 22:01:09
|
Am 26.08.2017 um 23:21 schrieb Benoît Minisini: > By the way, I'm currently thinking that the easier and the better may be > a 3.11 very fast, as soon as the TerminalView and process management is > stabilized (it seems now). Because there are far more than these 3 fixed > to merge. No problem, I would stay at 3.9 till then ... Alles Gute Christof Thalhofer -- Dies ist keine Signatur |
From: Benoît M. <ga...@us...> - 2017-08-26 21:21:25
|
Le 26/08/2017 à 22:58, Christof Thalhofer a écrit : > Am 26.08.2017 um 21:43 schrieb Benoît Minisini: > >> Yep. Apparently the git tag missed the three last commits of the >> final 3.10.0. I think I have to add them to the stable branch too. > > There is no stable branch, just a tag called v3.10.0. > > I think it makes sense to create a branch called v3.10.1 and cherry-pick > the fixes into it. > > So: > > git branch v.3.10.1 > git checkout v.3.10.1 > git cherry-pick 954f3ff7069e55 > git cherry-pick b2901f7d41e35b > git cherry-pick 8cd2dba1d4f116 > > Then the branch has to be pushed upstream > > git push -u origin v3.10.1 > > AFAIK > > Alles Gute > > Christof Thalhofer > By the way, I'm currently thinking that the easier and the better may be a 3.11 very fast, as soon as the TerminalView and process management is stabilized (it seems now). Because there are far more than these 3 fixed to merge. Regards, -- Benoît Minisini |
From: Christof T. <ch...@de...> - 2017-08-26 20:58:37
|
Am 26.08.2017 um 21:43 schrieb Benoît Minisini: > Yep. Apparently the git tag missed the three last commits of the > final 3.10.0. I think I have to add them to the stable branch too. There is no stable branch, just a tag called v3.10.0. I think it makes sense to create a branch called v3.10.1 and cherry-pick the fixes into it. So: git branch v.3.10.1 git checkout v.3.10.1 git cherry-pick 954f3ff7069e55 git cherry-pick b2901f7d41e35b git cherry-pick 8cd2dba1d4f116 Then the branch has to be pushed upstream git push -u origin v3.10.1 AFAIK Alles Gute Christof Thalhofer -- Dies ist keine Signatur |
From: <gb...@op...> - 2017-08-26 20:11:45
|
Merge request for Dutch translations. All parts and components should e translated to Dutch now. gbWilly |
From: Benoît M. <ga...@us...> - 2017-08-26 19:43:29
|
Le 26/08/2017 à 19:34, Christof Thalhofer a écrit : > Am 24.08.2017 um 21:35 schrieb Benoît Minisini via Gambas-devel: > >>> For everything to work, I would need to have in the stable branch the >>> same code as in the source archive. Right now, I can't speak on the >>> source itself, but the version numbers at least correspond to a >>> developing branch, not to a stable one. >> >> "stable" is the equivalent of "/branches/3.10". To get the 3.10.0 code, >> you must look at the "3.10.0" tag. >> >> Anyway I will fix the "stable" version with "3.10.0". > > On launchpad now there is a version called 3.10.0 whithout the fixes you > made before releasing 3.10.0 > > You asked for a last test, I reported, you fixed: > > b2901f7d41e35b "[DEVELOPMENT ENVIRONMENT] * BUG: Editor: Fix identation > of code beautifier on lines ending with an operator and on strings > spread over multiple lines." > > I now tested 3.10.0 from launchpad, it scrambles my code over and over > ... because this fix is not in it. > > Maybe the tag v3.10.0 is set to the wrong commit? It should have been set to > > 8cd2dba1d4f1169676 ... > > But it is at this commit: > bd1b84afcdafd1961d50b0f809c45eecca5b90eb > > So it lacks the last fixes ... > > > Alles Gute > > Christof Thalhofer > Yep. Apparently the git tag missed the three last commits of the final 3.10.0. I think I have to add them to the stable branch too. -- Benoît Minisini |
From: <gb...@op...> - 2017-08-26 18:51:59
|
In gambas3 there is gambas-wiki and gb.wiki. What slots do I use in changelog for gambas-wiki and gb.wiki? gbWilly |
From: Christof T. <ch...@de...> - 2017-08-26 17:35:03
|
Am 24.08.2017 um 21:35 schrieb Benoît Minisini via Gambas-devel: >> For everything to work, I would need to have in the stable branch the >> same code as in the source archive. Right now, I can't speak on the >> source itself, but the version numbers at least correspond to a >> developing branch, not to a stable one. > > "stable" is the equivalent of "/branches/3.10". To get the 3.10.0 code, > you must look at the "3.10.0" tag. > > Anyway I will fix the "stable" version with "3.10.0". On launchpad now there is a version called 3.10.0 whithout the fixes you made before releasing 3.10.0 You asked for a last test, I reported, you fixed: b2901f7d41e35b "[DEVELOPMENT ENVIRONMENT] * BUG: Editor: Fix identation of code beautifier on lines ending with an operator and on strings spread over multiple lines." I now tested 3.10.0 from launchpad, it scrambles my code over and over ... because this fix is not in it. Maybe the tag v3.10.0 is set to the wrong commit? It should have been set to 8cd2dba1d4f1169676 ... But it is at this commit: bd1b84afcdafd1961d50b0f809c45eecca5b90eb So it lacks the last fixes ... Alles Gute Christof Thalhofer -- Dies ist keine Signatur |
From: Fabien B. <gam...@gm...> - 2017-08-26 17:20:07
|
2017-08-26 14:51 GMT+02:00 Tony Morehen <tmo...@aj...>: > I know. One of the first programs I wrote back in the early 80s was a > terminal program to let my first IBM-compatible, a 12 mHz 80286, talk to my > other computer, a Z80 CP/M machine. > > Don't get me started on wiring a serial cable. Back then, nothing was > plug'n'play. Everything, including serial ports, was custom. > You have the luck to known these beautifull years :-). In these days i was only a baby and i've known my first computer only at 12 :-/ So it was in 1990... on m$dos 6 and W3.11. just before linux was born :-). The first computer i've used was a 86286 20Mhz. It took 2 sec to excel to show a letter after pressing the keyboard !!!. In fact, i've discovered the terminals on the late but i keep a good feeling about them for true productivity interconnected programs... better for that than actual cloudified web products. > > On 2017-08-26 02:37 AM, Fabien Bodard wrote: >> >> 2017-08-25 23:10 GMT+02:00 Benoît Minisini via Gambas-devel >> <gam...@li...>: >>> >>> Le 25/08/2017 à 22:32, Tony Morehen a écrit : >>>> >>>> When using terminalview in a terminal program, you cannot respond to >>>> prompts such as git's requests for username and password. Bash's >>>> built-in >>>> read command also doesn't work properly. You can type in text ok, but >>>> when >>>> you press enter, all you see is "^M" and nothing happens. All you can do >>>> is >>>> press control-C to abort. >>>> >>>> To duplicate: >>>> 1) run FTerminalView in gb.form.terminal >>>> 2) enter "read -p '>' >>>> 3) type some text, press enter >>>> 4) all you see is your text + ^M >>>> >>>> Potential fix: >>>> >>>> line 673 in TerminalFilter_VT100, change the False action of the IIf >>>> from >>>> "\r" to "\n" >>>> >>>> gb.form.terminal must be driving you guys nuts. >> >> Yes but it's so interresting ! And available emulator are not so numerous >> too. >> >> >>>> Cheers, >>>> Tony >>>> >>> OK, fixed. >>> >>> -- >>> Benoît Minisini >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Gambas-devel mailing list >>> Gam...@li... >>> https://lists.sourceforge.net/lists/listinfo/gambas-devel >> >> >> > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gambas-devel mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gambas-devel -- Fabien Bodard |
From: Tony M. <tmo...@aj...> - 2017-08-26 12:52:18
|
I know. One of the first programs I wrote back in the early 80s was a terminal program to let my first IBM-compatible, a 12 mHz 80286, talk to my other computer, a Z80 CP/M machine. Don't get me started on wiring a serial cable. Back then, nothing was plug'n'play. Everything, including serial ports, was custom. On 2017-08-26 02:37 AM, Fabien Bodard wrote: > 2017-08-25 23:10 GMT+02:00 Benoît Minisini via Gambas-devel > <gam...@li...>: >> Le 25/08/2017 à 22:32, Tony Morehen a écrit : >>> When using terminalview in a terminal program, you cannot respond to >>> prompts such as git's requests for username and password. Bash's built-in >>> read command also doesn't work properly. You can type in text ok, but when >>> you press enter, all you see is "^M" and nothing happens. All you can do is >>> press control-C to abort. >>> >>> To duplicate: >>> 1) run FTerminalView in gb.form.terminal >>> 2) enter "read -p '>' >>> 3) type some text, press enter >>> 4) all you see is your text + ^M >>> >>> Potential fix: >>> >>> line 673 in TerminalFilter_VT100, change the False action of the IIf from >>> "\r" to "\n" >>> >>> gb.form.terminal must be driving you guys nuts. > Yes but it's so interresting ! And available emulator are not so numerous too. > > >>> Cheers, >>> Tony >>> >> OK, fixed. >> >> -- >> Benoît Minisini >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Gambas-devel mailing list >> Gam...@li... >> https://lists.sourceforge.net/lists/listinfo/gambas-devel > > |
From: Fabien B. <gam...@gm...> - 2017-08-26 06:37:14
|
2017-08-25 23:10 GMT+02:00 Benoît Minisini via Gambas-devel <gam...@li...>: > Le 25/08/2017 à 22:32, Tony Morehen a écrit : >> >> When using terminalview in a terminal program, you cannot respond to >> prompts such as git's requests for username and password. Bash's built-in >> read command also doesn't work properly. You can type in text ok, but when >> you press enter, all you see is "^M" and nothing happens. All you can do is >> press control-C to abort. >> >> To duplicate: >> 1) run FTerminalView in gb.form.terminal >> 2) enter "read -p '>' >> 3) type some text, press enter >> 4) all you see is your text + ^M >> >> Potential fix: >> >> line 673 in TerminalFilter_VT100, change the False action of the IIf from >> "\r" to "\n" >> >> gb.form.terminal must be driving you guys nuts. Yes but it's so interresting ! And available emulator are not so numerous too. >> >> Cheers, >> Tony >> > > OK, fixed. > > -- > Benoît Minisini > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gambas-devel mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gambas-devel -- Fabien Bodard |
From: Benoît M. <ga...@us...> - 2017-08-25 21:52:59
|
Le 25/08/2017 à 23:18, gb...@op... a écrit : > Hi all, > > I submitted a merge request for Dutch translations for gb.term.form. > No idea if you get a notification on that at gitLab. > So to make sure you know, I post it here. > > gbWilly No, but maybe there is a way to get notifications of merge requests and I didn't activate it. Anyway, I regularly go to gitlab, so it's not a big deal. Regards, -- Benoît Minisini |
From: <gb...@op...> - 2017-08-25 21:18:14
|
Hi all, I submitted a merge request for Dutch translations for gb.term.form. No idea if you get a notification on that at gitLab. So to make sure you know, I post it here. gbWilly |
From: Benoît M. <ga...@us...> - 2017-08-25 21:10:59
|
Le 25/08/2017 à 22:32, Tony Morehen a écrit : > When using terminalview in a terminal program, you cannot respond to > prompts such as git's requests for username and password. Bash's > built-in read command also doesn't work properly. You can type in text > ok, but when you press enter, all you see is "^M" and nothing happens. > All you can do is press control-C to abort. > > To duplicate: > 1) run FTerminalView in gb.form.terminal > 2) enter "read -p '>' > 3) type some text, press enter > 4) all you see is your text + ^M > > Potential fix: > > line 673 in TerminalFilter_VT100, change the False action of the IIf > from "\r" to "\n" > > gb.form.terminal must be driving you guys nuts. > > Cheers, > Tony > OK, fixed. -- Benoît Minisini |
From: Tony M. <tmo...@aj...> - 2017-08-25 20:32:52
|
When using terminalview in a terminal program, you cannot respond to prompts such as git's requests for username and password. Bash's built-in read command also doesn't work properly. You can type in text ok, but when you press enter, all you see is "^M" and nothing happens. All you can do is press control-C to abort. To duplicate: 1) run FTerminalView in gb.form.terminal 2) enter "read -p '>' 3) type some text, press enter 4) all you see is your text + ^M Potential fix: line 673 in TerminalFilter_VT100, change the False action of the IIf from "\r" to "\n" gb.form.terminal must be driving you guys nuts. Cheers, Tony |
From: Benoît M. <ga...@us...> - 2017-08-24 19:35:46
|
Le 24/08/2017 à 20:46, Sebastián Kulesz a écrit : > Hi everyone! > > Sorry for the delay in getting into this, I just got back from an > exchange semester. > > This week I moved the building infrastructure of the PPAs from the SVN > repo to the git repo, but I had some problems in the way. First of all, > the stable branch in gitlab is not actually the same as the released > source archive for Gambas 3.10.0. > > For everything to work, I would need to have in the stable branch the > same code as in the source archive. Right now, I can't speak on the > source itself, but the version numbers at least correspond to a > developing branch, not to a stable one. "stable" is the equivalent of "/branches/3.10". To get the 3.10.0 code, you must look at the "3.10.0" tag. Anyway I will fix the "stable" version with "3.10.0". Regards, -- Benoît Minisini |
From: Sebastián K. <se...@gm...> - 2017-08-24 18:47:13
|
Hi everyone! Sorry for the delay in getting into this, I just got back from an exchange semester. This week I moved the building infrastructure of the PPAs from the SVN repo to the git repo, but I had some problems in the way. First of all, the stable branch in gitlab is not actually the same as the released source archive for Gambas 3.10.0. For everything to work, I would need to have in the stable branch the same code as in the source archive. Right now, I can't speak on the source itself, but the version numbers at least correspond to a developing branch, not to a stable one. I have already pushed builds to the three PPAs, to the stable one without knowing I would have this problem. I don't have access to the gitlab project to change it myself, so please update the version numbers as soon as possible. If there is any difference from the released source archive, that should also be fixed ASAP so that I can issue a new build. Thanks for the help, and sorry again for the delay. Regards, Sebastian |