Well, mate, just read the user guide and the docs, open the preferences panel (magic happens there!), and you will get answer for 90% of your questions, you donât really have to open a thread for everything.
But TLDR: guide, guide(maybe guide), guide, no way, docs.
@extrowerk: You put it very politely. Standard computer operating procedure is âRead the Manualâ. I know everyone wants a shortcut (put the manual under your pillow and sleep on it), but I personally have very little patience with people that do not do some research on an issue they are having before asking for help.
In addition to what extrowerk said: Haiku is opensource, feel free to make any enhancements you see fit. I personally like transparent terminals. But I have other improvements that I wish to work on before working on this.
What extrowerk said.
Perhaps try using a verbose flag with pkgman. Iâm not sure if it has one, I havenât tried or really cared. If it doesnât exist, feel free to add it.
As for ~, did you try hitting [tab] immediately afterwards? I have no issues with the ~ as the home shortcut. It works as I expect it to.
As for Haikuâs terminal being fast, thatâs because it doesnât do transparency. Ricing is a resource hog. Cool features are often a trade-off with performance. I donât think terminal is ugly. But then again Iâve set my preferences. Fonts, colors, etc. Check them out. Thereâs a lot that you can customize Haiku with. But youâre going to have to look at the preferences. Many apps have preferences within their menus, as does the OS at large as can be found in the preferences menu in Deskbar.
Nothing? The ~ character wasnât echoed back to the screen, like any normal character, or it was echoed back and that wasnât what you were expecting?
Anyway ⌠may have a bug here, though not in Terminal. Hereâs what I see:
Type in ârâ â~â âaâ ⌠get âr~aâ
Open Keymap preference utility, see âSelect dead keysâ item âTilde triggerâ set to â~â
Set it to â<none>â, close Keymap.
Open Keymap, set Tilde trigger to â~â - as it was before.
Type in ârâ â~â âaâ ⌠get ârĂŁâ.
What this suggests to me is that â<none>â is actually the default in practice, until Keymap starts writing out explicit values. I didnât succeed in figuring out just exactly where that happens - it appeared to me that Keymap could write its âKeymap settingsâ file and still not interfere with the default behavior, but ⌠I have only so many fresh installs to work with. Anyway, set those âtriggersâ to â<none>â, and Terminal and everything else should start behaving more normally.
This behavior: rtfm was the reason why i left Linux (back in 2000) and joind in BeOS - sad to see the same development in HaikuâŚ
I think everyone was a beginner once and he was happy so get help also this ment that the âprosâ need to tell things 10 tausend timesâŚ
I donât really see how a âopen the preferences brah!â is the same as âRTFMâ.
The questions doesnât even dive under the hood, where the differences between Haiku and other OS would play a significant role. I have seen some Terminal clients already, and according my experiences, changing it settings happens mostly in their prefpanel, like in Haiku.
But YMMV.
No. Having things written down in wikis and a user guide means not having to type out the same thing a thousand times. Posting a link to it should suffice, in case the document isnât a link directly on the userâs Desktop anywayâŚ
Just âRTFMâ is rude when the question is not obvious.
But look carefully at the second part of miqlas reply:
open the preferences panel (magic happens there!), and you will get answer for 90% of your questions
There is actually an answer here. So it was not just RTFM. This is an important difference.
when someone does not take the 10 seconds it requires to find this, why should we spend the time for them? Asking a question without spendin a few seconds doing your own research is also not nice, and can ruin the community just as well as people just replying RTFM without any extra info would.
Not all the needs are covered, and a shortcut for changing font size would indeed be nice (I use this a lot on linux and have it on control + mousewheel there)
My favorite terminals (urxvt, xterm) outside of Haiku use man pages and config files. Perhaps @nerd is used to this. I think it was another of his posts that mentioned i3wm (tiling window manager), which I also use. Thereâs really not much in the way of prefs panels there. Just man pages and config files. Coming from a man-page/config-file world to a mostly GUI prefs world can be confusing at first. Our system is much more intuitive, so a little bit of RTM, mixed with a welcome and nudging in the right direction is appropriate here. I see nothing wrong with how this was handled. âI see you came from an RTFM world. Welcome to ours. Have you checked out the Preferences in GUI? Our docs are warm and friendly. Have you browsed them yet?â
I seem to remember BeOS had an app that dealt with handling keyboard shortcuts by mapping them to applications and other commands and scripts. It was similar to QuickKeys for Mac. Iâm not sure if it was OSS, or got updated for Haiku. I canât seem to find it anymore. Do we have something like this? All of my query in Google and our webpages seem to come up with related content, but not quite on target.
SpicyKeys was converted into our Preferences->Shortcuts, but it can only run commands, not send messages directly to applications. Well, you can combine it with hey, I guess.
In this particular case anyways, it makes sense to add the shortcuts to Terminal instead of hacking up something.
Iâve started to add a shell argument for calling the Terminal and setting the initial working directory. There are times I donât want the default working directory, such as when calling Terminal with a Preferences->Shortcuts key combo. The default working directory there is â/â, which isnât very useful. This could have uses elsewhere that I havenât thought of.
The syntax will be:
$ Terminal -w /boot/home/
Or:
$ Terminal --working-directory /boot/home/
This example will set the initial working directory in Terminal to /boot/home/
I have the argument implemented in Arguments.h and Arguments.cpp. I also have the -h/âhelp updated to reflect the new argument. Next step is getting TermApp.cpp and TermApp.h fleshed out for the new command. I already have the new argument being received by TermApp.* I hope to have the rest of it working within a week.