General Linux Chat and Small Questions v. Year of the Linux Desktop!

[Genericenemy]

Back running Linux Mint. Everything running fine except a NTFS partition that won't mount, working to fix it.

[Van-man]

[QUOTE=Genericenemy;47844800]Back running Linux Mint. Everything running fine except a NTFS partition that won't mount, working to fix it.[/QUOTE]

Often it needs to be accessed by windows, restarted into windows again and accessed and then shut down, then Linux can access it.

NTFS is weird.

[shodan]

Decided to make my netbook a TTY-only system since I'm pretty comfortable in the TTY. I'll launch awesome for when I need to use firefox.

vim seems to hate me and refuses to be set up. Been ages since I've used vim so this is a surprisingly painfull experience. tmux was set up in like 1 minute and learning how to use it took me maybe 2 minutes.

I'm missing a bunch of kernel modules so sound and battery status won't work. Sound is not really an issue since it's a system built for sysadmin stuff and programming on the go. Battery status is a PITA since I'm unable to find shit about it. WIFI needs a dirty hack to stay connected. I have ping 8.8.8.8 running in a small tmux window so that the wifi connection never goes idle. if it goes idle then it just freaks out and sometimes refuses to reconnect.

I'd love some pointers to how the fuck I should get powerline and code completion in vim working.

[t]http://i.imgur.com/V9bLsfm.png[/t]

[editline]31st May 2015[/editline]

I seem to be missing the kernel modules for on-board Realtek RT5640 and battery status should in theory work [url]https://wiki.debian.org/InstallingDebianOn/Asus/X205TA#Power_Management[/url]

[Van-man]

nano > vim

[Darkwater]

[QUOTE=Van-man;47845470]nano > vim[/QUOTE]

u w0t m8

[Van-man]

[QUOTE=Darkwater124;47845599]u w0t m8[/QUOTE]

[URL="http://en.wikipedia.org/wiki/GNU_nano#/media/File:Nano_2.1.2-svn.png"]You heard me[/URL]

[Van-man]

[QUOTE=~Kiwi~v2;47845625]I also support the nano feud.

Nano is god tier CLI text editor.[/QUOTE]

VI and VIM were absolute bitches to learn to use, and I kept forgetting how to use them.
On the other hand, I mastered nano in less than 5 minutes and that's stuck with me.

[Darkwater]

[QUOTE=Van-man;47845630]VI and VIM were absolute bitches to learn to use, and I kept forgetting how to use them.
On the other hand, I mastered nano in less than 5 minutes and that's stuck with me.[/QUOTE]

That's easy, it's not like nano has a lot to offer \:v:/

[Stonecycle]

[QUOTE=Van-man;47845470]nano > vim[/QUOTE]

I feel like I hold the unpopular opinion on this and I use both. [I]nano[/I]'s good with regular general-purpose text files (eg. notes) and [I]vi[/I] is better suited for coding. Still accidentally :wq at the end of things.

[editline]:q[/editline]

But a real unpopular opinion is that nvi > Vim. Vim's just bloated and full of crap. Extensible text editors are not my cup of tea.

[editline]vi[/editline]

The only things to get the hang of in vi-likes is [B]h[/B], [B]j[/B], [B]k[/B], [B]l[/B] to move, [B]i[/B] to insert text, and [B]x[/B] to delete characters. Just focus on those and the other keys will come to you. Then you find out very neat things, like [B]o[/B] to open a new line below, [B]O[/B] (shift-O) to open a line above, [B]J[/B] to join the current and the next lines.

[Darkwater]

[QUOTE=Stonecycle;47846317]I feel like I hold the unpopular opinion on this and I use both. [I]nano[/I]'s good with regular general-purpose text files (eg. notes) and [I]vi[/I] is better suited for coding. Still accidentally :wq at the end of things.

[editline]:q[/editline]

But a real unpopular opinion is that nvi > Vim. Vim's just bloated and full of crap. Extensible text editors are not my cup of tea.[/QUOTE]

pf, I use ed

[Comfy]

cat "Plebs" >> fp.c

[lavacano]

I actually use Windows Notepad in wine.

The real one, not the fake one the Wine devs made.

[mastersrp]

[QUOTE=Darkwater124;47846404]pf, I use ed[/QUOTE]

I have The UNIX Book in Danish (UNIX Bogen), which specifies instructions on how to use both vi and ed. Apparently ed is still used among some people, even though it wasn't very popular back then either.

[Darkwater]

[QUOTE=kaukassus;47846486]cat "Plebs" >> fp.c[/QUOTE]

what's in the Plebs file then

[editline]31st May 2015[/editline]

[QUOTE=mastersrp;47846916]I have The UNIX Book in Danish (UNIX Bogen), which specifies instructions on how to use both vi and ed. Apparently ed is still used among some people, even though it wasn't very popular back then either.[/QUOTE]

I find ed genuinely useful when making very simple edits like removing a known line from a file (in the case of conflicting keys for ssh; ed ~/.ssh/known_hosts; 12d; wq)

[Stonecycle]

[QUOTE=mastersrp;47846916]Apparently ed is still used among some people, even though it wasn't very popular back then either.[/QUOTE]

The only people I can imagine who would still use [I]ed[/I] are either:
A) people with hardcopy terminals (think Pentium actually has one, not trying to pull a crack at him) or otherwise without the resources to run a visual editor,
B) people really trying to learn the [I]ex[/I] commands like s/regx/subs/ that makes [I]vi[/I] easier to use, or
C) gluttons for pain. Don't think you can hide those handcuffs, harnesses, and ball gags. We already know.

[rilez]

I usually default to nano because it's included with most distros I use

Been meaning to try [url=http://ne.di.unimi.it/]nice editor.[/url] Actively maintained, which is a plus

[vlad]

I don't think nano and vim are really comparable, I feel they're both used for different things. sure, some may use vim for text editing and maybe some people use nano for coding? but in the end, nano feels a lot more directed at general text editing than anything else while vim is more of a complete program intended for more than just text editing

[lavacano]

I've been having problems with ncmcpp not sorting my playlist when I tell it to (instead losing connection to mpd and not actually doing anything).

So I'm solving my problem the way Linux users across the globe have done since the dawn of strftime() - I'm making my own goddamn MPD client, with blackjack and hookers.

[DrTaxi]

[QUOTE=~Kiwi~v2;47845625]Nano is god tier CLI text editor.[/QUOTE]

Nano is god tier fixing-typos-in-production editor.

[FPtje]

[QUOTE=PredGD;47848031]I don't think nano and vim are really comparable, I feel they're both used for different things. sure, some may use vim for text editing and maybe some people use nano for coding? but in the end, nano feels a lot more directed at general text editing than anything else while vim is more of a complete program intended for more than just text editing[/QUOTE]

My uni forces me to use emacs for some language called agda. I have no choice because emacs is the only editor that reasonably incorporated "agda shortcuts", and it's truly impossible to code agda without them.

I am in great pain and hate emacs with a passion.

[mastersrp]

I prefer vi, not because of the editor and not because of it being "simpler than vim" (it's pretty shitty in comparison, in my opinion anyway), but because as opposed to nano, this one is actually always installed.

I've encountered a lot of server installations where no editor was installed. Except vi, it was the only thing available. Well, that and ed, but I can't fucking figure that shit out, so vi was the go to tool for a lot of the hot maintenance tasks I've had to do.

[shodan]

[QUOTE=DrTaxi;47850636]Nano is god tier fixing-typos-in-production editor.[/QUOTE]

[highlight]FUCK IT! WE'LL PATCH IT LIVE![/highlight]

[MuThing]

nano is the only one I can actually understand how to control, vi and vim are just lost on me for some reason

entering commands for a text editor just seems kind of strange

[larikang]

If you don't grok vim you are guaranteed to hate vim. It's a lot like git: if you aren't used to thinking of software development as a nonlinear graph, you're guaranteed to find git over-complicated and confusing. But that doesn't mean git is a bad tool.

Luckily the vim developers are entirely aware of this problem, so if your distro has vim it also has vimtutor. It's a simple, interactive tutorial that walks you through all of the basic features. You can easily complete it in one sitting and by the end you'll be a functioning vim user. It might not make vim your favorite editor, but at least you'll be one less person posting horror stories about trying to quit vim, which still makes me happy.

[Van-man]

[QUOTE=Larikang;47855633]If you don't grok vim you are guaranteed to hate vim. It's a lot like git: if you aren't used to thinking of software development as a nonlinear graph, you're guaranteed to find git over-complicated and confusing. But that doesn't mean git is a bad tool.

Luckily the vim developers are entirely aware of this problem, so if your distro has vim it also has vimtutor. It's a simple, interactive tutorial that walks you through all of the basic features. You can easily complete it in one sitting and by the end you'll be a functioning vim user. It might not make vim your favorite editor, but at least you'll be one less person posting horror stories about trying to quit vim, which still makes me happy.[/QUOTE]

I completed that, and in less than a week, vim will be back to being my sworn enemy.

On the other hand, Nano is love, Nano is life.

[Trekintosh]

I need more Raspberry Pi help from y'all. I'm trying to follow [url=http://www.oblivion-software.de/index.php?id=56&type=98]these instructions[/url] to compile VLC with HW acceleration on a Pi. The intent is to get two raspberries playing 2 video files with near perfect synchronization and VLC apparently has built-in service for that. Now I'm running into trouble after following the directions. Everything is going perfectly until I hit "make clean" or even just "make" or "make ***", it doesn't matter. For Make Clean it gives me

pi@raspberrypi ~/vlc $ make clean
make: *** No rule to make target 'clean'.  Stop.

and for just make or make *** it gives me

pi@raspberrypi ~/vlc $ make
make: *** No targets specified and no makefile found.  Stop.

or

pi@raspberrypi ~/vlc $ make ***
make: Nothing to be done for 'Makefile.am'.

Where am I going wrong?

[Stonecycle]

[QUOTE=Trekintosh;47856309]:words:
Where am I going wrong?[/QUOTE]

It's not finding a makefile. Is there a [B]Makefile[/B] in the directory you're compiling in? Going by the instructions you linked, have you installed the packages mentioned in step 5? And have you run the configuration script from step 6?

# ./configure --enable-rpi-omxil --enable-dvbpsi --enable-x264

That will generate the [B]Makefile[/B] to use.

[Trekintosh]

[QUOTE=Stonecycle;47856368]It's not finding a makefile. Is there a [B]Makefile[/B] in the directory you're compiling in? Going by the instructions you linked, have you installed the packages mentioned in step 5? And have you run the configuration script from step 6?

# ./configure --enable-rpi-omxil --enable-dvbpsi --enable-x264

That will generate the [B]Makefile[/B] to use.[/QUOTE]

Yeah I followed the steps, there's Makefile.in, Makefile.am, and make-alias (no extension). Do they need to be not capitalized?

[lavacano]

I figured having my current SELinux role in my prompt would be nice, so I cooked up a few lines for my zshrc

idZ=$(id -Z 2>/dev/null)
if [ $? -eq 0 ]; then
        selinux_currole=$(echo $idZ | cut -d ":" -f 2)
else
        selinux_currole="" # To prevent errors on non-SELinux systems
fi

Then you just stick ${selinux_currole} in PROMPT or RPROMPT somewhere. Perfectly safe to use on non-SELinux systems too, in case you're like me and just copy the same zshrc everywhere.

[Relaxation]

Terminal-based music player suggestions? Been out of the loop on it for a bit.