Cherry Popped!

Liam89 · 2014-02-19 04:46:15

I'm new to #! and Linux in general. In fact, apart from using my Mothers Mac the odd time, I've never really ventured from Windows ops . I wanted to breathe new life into an older laptop of mine and after a short search I came to the conclusion that a lightweight linux distro was the way to go. Crunchbang seemed to be getting most of the praise and it seemed to be founded so I made the leap and couldn't be happier. I'm virgin-new when it comes to operating through the terminal and although I don't need it to pursue my interests (Web design and possibly development), I figure it really can't hurt. So apart from saying Hello World and asking for well wishes I would also like to kindly inquire as to any starting tips anybody might have to help me become a more powerful user. E-books, tutorials, guides, documentation etc. would all be very useful! This is all very exciting! Thank you for reading this, if you did!

Oh and can somebody please tell me what the button is in the top left of the windows. The one that looks like 4 squares. I couldn't submit a screenshot as I couldn't figure out how to do so. Do I provide the path as a link and if so, what would the path be provided it's in my images directory?

nore · 2014-02-19 10:52:39

Welcome, Liam89.

Liam89 wrote:

Oh and can somebody please tell me what the button is in the top left of the windows. The one that looks like 4 squares.

Omnipresent: "Make the window visible on all desktops, if it is not already. Otherwise, make it visible only on the current desktop." Press it and move to another workspace. The window follows you.

For screenshots, use some image hosting service, like imgbox.

photonucleon · 2014-02-19 11:35:15

Welcome! One of the best ways to learn, in my opinion, is to mess with the system and tweak settings here and there (though this is not 100% Terminal-oriented). If you start off by tweaking Conky (the system monitor that's on your desktop) to suit your preferences, you'll soon get the hang of working with config files. Go [Right-click on the Desktop > Settings > Conky > Edit .conkyrc] and have a look at the file. Make a backup of any config files you change, though, so if you break something it's not too hard to put it back smile Pressing Ctrl+H in the file manager will show hidden files (ones that begin with a "."), and many of these are config files like .conkyrc; then just copy/paste the one you want to edit so you can tweak the original in relative safety big_smile Start with conky, and then move on to tint2 would be my suggestion. Of course, you're also free to leave them as they are smile

Hopefully I haven't got too carried away with that ^ big_smile it did end up rather a wall of text hmm

Enjoy #!

Liam89 · 2014-02-19 13:12:33

No not too carried away at all! Like I said, I'll welcome any and all advice. So thanks guys really! The biggest adjustment for me is probably the terminal. It's a daunting thing to learn when you've used Windows all your life but the allure far outways the trepidation.

photonucleon · 2014-02-20 19:53:27

Oh, just remembered one helpful thing I learned when first using the command line (on a Mac, but same thing applies here on #!):

Commands generally follow the syntax "command options arguments", command being the name of the command you're entering, options being extra things you can 'tag on' to modify what exactly the command does, and arguments being things that the command is acting on (files, for example). However, it is not always necessary to have options and/or arguments, depending on the command. So, using the simple example of figlet (you can try this in a terminal without worrying, as it's a very simple command and will in no way affect your system (in theory tongue )
Type

figlet

in a terminal, press enter, and then type any text you want and press enter. Figlet shows what you wrote in 'bubble writing'. Press Ctrl+C to end figlet. This is using just a command. Now do the same, but with the command, followed by an option as shown:

figlet -f script

Now you are using the option "-f script", i.e. choose the font which is called 'script'. Finally, enter

figlet -f script "CrunchBang"

This uses the command, the option, and the 'argument' "CrunchBang", which tells figlet to act using that 'argument', i.e. take that as the text to display rather than something you type after you entered the command.
This is a basic outline of terminal syntax, and as I say, not all of it will be applicable to every command, and some commands will be more complex. To finish with, have a look at the 'man' command, using figlet as an 'argument':

man figlet

This shows the manual page for figlet. (Or any command you specify instead).

Another wall of text hmm but never mind... big_smile

Last edited by photonucleon (2014-02-20 19:54:35)

CrunchBang Linux

SEARCH

#1 2014-02-19 04:46:15

Cherry Popped!

#2 2014-02-19 10:52:39

Re: Cherry Popped!

#3 2014-02-19 11:35:15

Re: Cherry Popped!

#4 2014-02-19 13:12:33

Re: Cherry Popped!

#5 2014-02-20 19:53:27

Re: Cherry Popped!

Board footer