Hi, I'm gonna release a small version 3 when the summer's gone. So far as a user I've done most of what I need to program better my little shitty programs. However if you have reasonable ideas (e.g asking for debuging  is not reasonable) you can go here and fill an issue:

https://github.com/BBasile/Coedit/issues

If you're not interested by Coedit at all, never mind, several times non-users ppl have helped me with their ideas.

To avoid dups, there's a list of what is/will be done here:
https://github.com/BBasile/Coedit/milestone/3

- things like #78, #87, #45 are examples of reasonable request.
- things like #77, #59, #68 are examples of irrational request.

I'd also like to mention this (icons for comp menu and symbol list):

https://github.com/BBasile/Coedit/issues/43

which I can't do myself because it requires graphic skills. I seriously don't know how to find these kind of icons.

See ya.

On Saturday, 16 July 2016 at 02:00:47 UTC, Basile B. wrote:
> Hi, I'm gonna release a small version 3 when the summer's gone. So far as a user I've done most of what I need to program better my little shitty programs. However if you have reasonable ideas (e.g asking for debugging  is not reasonable)

Finally I can say that GDB will be supported under linux. Here's a small teaser:

https://vid.me/1MYy  (sorry the quality is not good, if anyone knows a better host without registration...)

showing:
- breaking
- steping
- call stack dump, call stack naviguation
- GPR dump
Not many much more is implemented so far.

Technically GDB integration is easy but boring (not to say that it's monkey work) !

The machine interface output is almost compliant with JSON but since not totally the output stream has to be tokenized to build a true JSON. From this JSON the messages can be finally interpreted easily.

On Monday, 19 September 2016 at 21:37:35 UTC, Basile B. wrote:
> On Saturday, 16 July 2016 at 02:00:47 UTC, Basile B. wrote:
>> Hi, I'm gonna release a small version 3 when the summer's gone. So far as a user I've done most of what I need to program better my little shitty programs. However if you have reasonable ideas (e.g asking for debugging  is not reasonable)
>
> Finally I can say that GDB will be supported under linux. Here's a small teaser:
>
> https://vid.me/1MYy  (sorry the quality is not good, if anyone knows a better host without registration...)

slightly better quality https://sendvid.com/uo8ljnre

On Monday, 19 September 2016 at 21:37:35 UTC, Basile B. wrote:
> On Saturday, 16 July 2016 at 02:00:47 UTC, Basile B. wrote:
>> Hi, I'm gonna release a small version 3 when the summer's gone. So far as a user I've done most of what I need to program better my little shitty programs. However if you have reasonable ideas (e.g asking for debugging  is not reasonable)
>
> Finally I can say that GDB will be supported under linux. Here's a small teaser:
>
> https://vid.me/1MYy  (sorry the quality is not good, if anyone knows a better host without registration...)
>
> showing:
> - breaking
> - steping
> - call stack dump, call stack naviguation
> - GPR dump
> Not many much more is implemented so far.
>
> Technically GDB integration is easy but boring (not to say that it's monkey work) !
>
> The machine interface output is almost compliant with JSON but since not totally the output stream has to be tokenized to build a true JSON. From this JSON the messages can be finally interpreted easily.

Nice work!

On Monday, 19 September 2016 at 21:37:35 UTC, Basile B. wrote:
> On Saturday, 16 July 2016 at 02:00:47 UTC, Basile B. wrote:
>> Hi, I'm gonna release a small version 3 when the summer's gone. So far as a user I've done most of what I need to program better my little shitty programs. However if you have reasonable ideas (e.g asking for debugging  is not reasonable)
>
> Finally I can say that GDB will be supported under linux. Here's a small teaser:
>
> https://vid.me/1MYy  (sorry the quality is not good, if anyone knows a better host without registration...)
>
> showing:
> - breaking
> - steping
> - call stack dump, call stack naviguation
> - GPR dump
> Not many much more is implemented so far.
>
> Technically GDB integration is easy but boring (not to say that it's monkey work) !
>
> The machine interface output is almost compliant with JSON but since not totally the output stream has to be tokenized to build a true JSON. From this JSON the messages can be finally interpreted easily.

News from the front:

- Input can be passed to the "inferior" when using ">" as first character in the custom commands.
- Runnable modules can be debugged. I.E: you can debug a module that's not even saved... (but it still needs -g in the shebang).

Example:

http://sendvid.com/twz6x4ln