![]() These are known as file descriptors, they describe where the output should go. STDERR (which receives the output from system errors, and by default sends them to the screen so that the user is aware of the error). STDOUT (usually the screen, but again this can be changed, for example to send the output of a command to a file) STDIN (the standard input device, usually the keyboard but this can be changed) The numbers 0, 1 & 2, are associated with: I can figure out what most scripts do, but bash is so terse, and confusingly like C but not always, that writing a working script from scratch is dicey.īut if I manage to produce anything interesting, I’ll be happy to share. I may or may not find the energy to become proficient, but a little more practice can’t hurt. Like, from a book and examples on the internet. In any case, these menus are inspiring me to try learning bash scripting again. In the middle of everything, my back decided it did not want to do its job anymore, so I have been in bed reading for the last few days. It took me a bit to test this out as I decided to update the menu system on my desktop which meant moving a few customizations into mb-jgtools, including a submenu of tag^s that I figured out where to put the first time and then forgot why it was there and not somewhere else. It works! That is, xdg-open does what it is supposed to do where you put it in the menu scripts: it opens text and other sublime-text-assigned mime types in sublime text. Even if it’s just thinking about it and deciding not to do more than that.) As it is, I will just thank you in advance for anything you do decide to do. (And if it were a decade or so ago and/or time would slow back down to a reasonable rate of passage and/or the body would return to a reasonable rate of doing things, I would offer that ambition, time and energy for this. There may be other, faster ways to do this, but if I were feeling very ambitious and wanted to implement this myself, I would probably start with one of these. Instead of having geany hard-coded as the text editor throughout the menus, scripts could check the mimetype of the file to be edited and open it in the default app for that mimetype.Īdd a mechanism for assigning a default text editor scripts could then call for that default to open text files for editing. Two ways to do this occur to me at the moment: Given all the work you have done on them, they could be worth sharing outside of Mabox. Thus: would you, keeper(s) of this awesome distro, consider adding support for text editors besides geany to the jgmenu system? It would make the menus themselves much more portable. And it has occurred to me that extensively customizing the jgmenu system would mean needing to keep an eye on updates and figure how best to merge any new features that I wanted–or just let the future of the menus unfold without me. It’s been 8 months? And I am no closer to doing that than I was before. So probably there is more that I have to change … ![]() Every file there that contained Geany I changed to gvim, and also restarted a couple of times. But somehow, if I open a config file from the left menu (for example “edit config file mabox2001 tintrc”), it still is opened with Geany. I’m trying to change the default text-editor Geany to Gvim, and for the most it works. How to change the default text-editor (geany) to gvim completely Basic Help & Support
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |