Comments by "OpenGL4ever" (@OpenGL4ever) on "DistroTube" channel.

  1.  @JD-im4wu  Your're talking bs. Real coders of course do use an IDE.
    4
  2.  @Cookiekeks  nano is for editing small text files, if i need to code i use a real IDE. There is no point for me to use vim. The time it takes to make vim ready for debugging is a waste of time, because a real IDE does already have an integrated debugger.
    3
  3. My nano config looks like this: set autoindent set guidestripe 80 set stripecolor normal,lightblack set linenumbers set numbercolor yellow,black set brackets ""')>]}" set matchbrackets "(<[{)>]}" # set tabstospaces set trimblanks
    2
  4. The config can be found in ~/config/nano/nanorc
    2
  5. I tested Micro today and it's quite annoying that it uses keyboard shortcuts from Nano but then implements them halfway. To give an example here would be CTRL+K and CTRL+U to cut and paste a line in nano. Micro only implements the first combination and has reserved the second for something else. This ruins the whole workflow. Either you implement these two completely or you leave them out completely. But not half measures like that. Yes, you can change all the keybindings, but that's extra work and who knows if the help will adapt to that?
    2
  6. and ne and pico.
    2
  7. Nothing. Nano is a great editor for small editing tasks. And if you want go coding, you use a full IDE anyway.
    2
  8. How does i3 behave on a multi monitor setup if the left monitor of two monitors is turned off? Does it show everything on the center monitor the only one that is turned on or does it place new gui processes on the screen of the turned off left monitor?
    1
  9. That question can't be answered because it depends on the work to be done. Sometimes there are bugs to find and finding them can take some hours, days or weeks. Some bugs might never be fixed. If you need a distribution that always have the newest stuff but does care that the avoidable showstoppers are fixed before release you could give Manjaro a try. Here's a nice graph showing what steps are done: https://manjaro.github.io/homepage/public/features/background/ Between Manjaro stable and arch daily are about 2 weeks, thus the software is rather new. Personally i don't need thew newest stuff, i prefer a stable system, thus i use Debian stable.
    1
  10.  rs_  I want to be able to see the output of "ls -a ~/" without having to scroll. This can be only accomplished if the software developers comply to the XDG directory specification.
    1
  11.  rs_  It's not much effort. It's a check if an old directory exist, if yes, use it. If not, check for XDG_DIR, if it exist, use it, if not, fallback to old dir. This check should be done by runtime, thus there is no need to take additional care for old installations. The old installations are used just as before.
    1
  12.  rs_  KDE and Gnome are both projects with large code pages. Thus the size of the code is not an argument. Also, large code bases tend to use the same functions to read the configuration if the software is programmed in a modern reusable way, thus you need to change it only once in one place. The only valid argument where a change to XDG_DIR can be software, where other software is based upon and requires to change the config of that base software. And these are only very few projects. The majority of software can be easily transformed to XDG_DIR standard.
    1
  13.  @Hro18059  Yes it does. KWrite is the simpler one with much less features. It's a little like if you compare notepad (kwrite) with notepad++ (kate).
    1
  14.  @alextrotta796  Don't they use a distribution? Installing other software should be easy with them.
    1
  15. But there was pico, if it was installed. nano is a re-implementation of pico.
    1
  16.  @DistroTube  You don't need a shift with CTRL+G.
    1