#81

I too run into this fairly often and have found that refreshing the browser seems to fix it.

1 Like
#82

The primary browsers which were tested during development were:

  • Chrome (macOS, Windows 10, Linux)
  • Firefox Quantum (macOS, Windows 10)
  • Safari (macOS)

There have been various references to file rename operations not working here on lines, enough that a GH issue was opened up: https://github.com/monome/maiden/issues/127. Until that issue gets addressed the best bet is to save the file and refresh the browser window.

#83

If I happen to generate 3 or 4 untitled .lua scripts and need to do a refresh I often lose them.

#84

Did you either save the untitled scripts or ran them (which also saves them)?

#85

Doh! thatā€™s it :disappointed_relieved::disappointed_relieved: thanks!

#86

I just started using Coda. Local/remote fie management is indeed a breeze.

Question though: I canā€™t seem to get the remote path set quite right. The remote pane always opens to the /home/we/ directory.

Iā€™ve tried various combinations of the following:

/home/we/dust
/home/we/dust/
/dust
/dust/

In all cases it opens to the /home/we/ directory and Lua scripts I upload always end up in /home/we/ .

Iā€™m sure I have configured it incorrectly. Any cure?

Thanks.

BTW: I was using IntelliJā€™s PHPStorm (used it in a past life). Worked fine, but I could not get the code highlighting settled. Also tried Visual Studio Code, but could not get SFTP configured. Lovely code highlighting though.

Coda seems to have it all for norns script dev.

1 Like
#87

As we transitioned into 2.0 I suddenly felt very out of my league and backed up out of the room while the adults figured out the adult problems.

This was the face I was making --> :grimacing:

That said, Iā€™m only now realizing Iā€™ve missed the giant beta 2.0 thread, so I have designs of taking the beta plunge tonight and Iā€™ll report back asap!

3 Likes
#88

come in
the waters warm :blush:

same happened to me (for slightly different reasons)

3 Likes
#89

Aw! That makes me feel better. You were real busy in the beginning!

I had so many aspirations and so little skills, but Iā€™ve at least skimmed EVERY single git commit to stay somewhat informed (and to further validate my decision to stay quiet and listen).

It certainly didnā€™t help that my lines visits started heading in the i2c/modular/er301 camp instead of norns.

2 Likes
#90

Wait for the new beta that should be ready for tomorrow, so you wonā€™t have to pull the corrections since the start of the beta!

2 Likes
#91

is there a way to update maiden without rebuilding?

#92

get one of the releases and unzip it to your home folder (it should live in /home/we/maiden): https://github.com/monome/maiden/releases

#93

many thanks will do now

#94

Good looking out. Been lurking in the shadows this longā€¦ whatā€™s a few more days?

:blush:

#95

FINALLY getting around to updating tonight.

For Coda 2 as my IDE, Iā€™m just using /home/we/dust in the ā€˜siteā€™ settings here:

08%20PM
Screen Shot 2019-03-16 at 8.51.08 PM.png952Ɨ848 100 KB

Connecting with SFTP:

17%20PM
Screen Shot 2019-03-16 at 8.53.17 PM.png952Ɨ846 81.5 KB

And hereā€™s the slick ssh settings:

29%20PM
Screen Shot 2019-03-16 at 8.53.29 PM.png942Ɨ850 61.3 KB

Iā€™ve never had a ton of luck with the source control (git) stuff, but Iā€™m more comfortable with the command line with git.

1 Like
#96

Yes. Codaā€™s Terminal window makes it pretty convenient.

#97

Did you ever get it to resolve correctly to the appropriate root folder? My answer may have been overkill for your initial question. I just got excited to help!

1 Like
#98

Thanks. Yes, got it all sorted. :metal:

#99

Is there a way to side-step maiden and get the same repl & run functionality from the command line? I would love to be able to edit using my vim config and have the repl/log going in another terminalā€¦

This seems to handle the repl part of the equationā€¦ Unfortunately sounds like it might not be easy:

As it goes, I can edit the file on my norns box using vim, with the repl in another window this way, then just re-load the script from norns directly, seems to be an OK compromise for now, I wish I understood golang a bit better maybe I could write a simple interface to the maiden backend from the command line. Looked over the code for about an hour and couldnā€™t figure it outā€¦

3 Likes
#100

Assuming that you have ssh working, in terminal A:

ssh norns.local
cd dust/code
vim hello.lua

ā€¦in a second terminal B:

ssh norns.local
# shutdown the existing wrapped copy of matron
systemctl stop norns-matron
# run the raw matron command directly
norns/build/matron/matron
# while there is no prompt this is the lua repl
norns.script.load("code/hello.lua")
# to exit
^C
# to restore normal operation reboot norns or
systemctl start norns-matron

The play button in maiden is simply saving the current file to disk and then calling norns.script.load(<relative_path_under_dust_dir>) for you. The raw lua repl in matron doesnā€™t have any command history or line editing like the maiden repl does (that is done in the browser)

I have thought about a simple extension to the maiden backend (running on norns) which exposes the repl for either matron or sc by tapping into the existing sockets which the browser client uses thus allowing both to work side by side.

Hopefully that helps.

10 Likes