CudaText build for Common Lisp, with compiler

[Alexey-T]

@DeivAstra
can you make zip file with Cud entire folder, with Common Lisp lexer + compiler, with External Tools plugin (which you configured already)? i will look at it. will try to convert it to Runner plugin.

[DeivAstra]

Hello, I did't see this discussion. )
Yes, I intended to create CudaText archive and put necessary utils into.
My question is what the name can I use for this build? Do you have any ideas?
Then deploy it, for example, on SourceForge.

[Alexey-T]

CudaText with CL
CudaText-CL
CudaText-Lisp

[Alexey-T]

Imho its good to put into pack:

Lexer
Compiler
Runner
Build system for CL
Maybe, ConfigureToolbar plugin with confugured toolbar buttons to call buildsystem and~or to run the result

Or

Lexer
Compiler
External Tools plugin and its config to call needed commands

[Alexey-T]

@DeivAstra I see this is not discussed, no replies. If you need a help with CmnLisp package, tell me.

[DeivAstra]

Hello, I'm busy with other things at the moment. But remember a problem which meet before: Tools Properties => Capture Output => Console. I tested to redirect compiler output to the console and there 2 issues:

1. I see lag - text appears 1-2 sec later after code executed. (=> Output Panel has no lags at all)
2. How to read input? For example, we need handle user input, how to do it?
   I use linux terminal to run compiler now, so, this is not handy because there are so many different in many Linux distro.
   Using of embedded Console is more preferable but the issues block this.

PS I plan to continue move forward to create CL build a bit later.

[Alexey-T]

1. "Console shows a lag" - yes, it's Cud issue, it is by design. all output to console is flushed to the UI in the 'app is idle' event. ie this delay can be more than 2 secs if you type something in editor. I don't plan to change this, current 'idle' output is good, it don't make app busy by reacting to python output. If you don't like the delay, config output to the Output-panel.

2. "how to input something for a tool?" - External Tools has macros for this:

   {Interactive}      - Text will be asked at each running
   {InteractiveFile}  - File name will be asked

specify them as tool parameters in "" quotes.

[DeivAstra]

"how to input something for a tool?"

No, user input should handles by the code.

[Alexey-T]

If it is 3rd party code, it can show any gui window, no? Or is it console app? Then its a problem.

[Alexey-T]

inactivity; closing...

[DeivAstra]

I want to create archive of CudaText with predefined settings.

1. Extracted editor should opens a project located in CudaText directory and some Welcome file(s).
   So, need to use relative path here:
   cuda_project_man.json

{
  "recent_projects": [
    "${CUDATEXT_HOME}/default-project/default.cuda-proj"
  ],

2. I did't find something like 'CUDATEXT_HOME' in variables to use in the Tools.
   For example, some additional executable files are included to editor archive but cant be run from the relative directory of the editor.

It is problem to build something over on CudaText due to mentioned restrictions.
The main idea to avoid enforcing a developer to setup whatever.

Steps to fast start to develop:
Download CudaText -> Extract -> Run -> Welcome file or files with examples will opened -> Developer can create files and dirs in default project, compile and run the code.

[Alexey-T]

Hi. You have posted the same in #5845, so I will answer there.