[00:52] hi. you guys have any experience with xclip/xdotool? I'm trying to avoid using the mouse as much as possible, but I want to copypaste things into command lines. [00:52] thx in advance. === cristianv is now known as rodia [01:56] hi [02:47] im trying to get my ~/.profile file to work correctly with aliases... [02:47] ...when i type the following in the shell, it works perfectly: youtube-dl $(xclip -o)... [02:47] ...and when i alias it like this, it works perfectly: alias y="youtube-dl '$(xclip -o)'"... [02:47] ...but when i put alias y="youtube-dl '$(xclip -o)'" into the ~/.profile file, I am forced to then type . ~/.profile, otherwise the xclip portion of it "expands" to whatever its contents were at the moment I last saved the file. which is obviously not what im trying to do... [02:47] ...i want whatever is *currently* saved at this very moment within the copybuffer to be sent to youtube-dl as an argument.... [02:48] and im trying to save an alias to do so wihtin my profile, so i dont need to type $alias y="youtube-dl '$(xclip -o)'"... [02:48] ...because: i have MANY shells open simultaneously, whenever im using linux. especially when im simultaneously downloading many videos... [02:48] ...any help pls? thx in advance! :) [04:24] also... [04:24] also, where is the procfs located? [04:25] rtndog, the linux proc file system (procfs) is a virtual file system created at boot and exists in memory [04:26] oh. [04:26] so there is no analog to it within the filesystem that appears in midnight commander, or in the shell? there is no way to view it by cd-ing to it and typing ls -la? [04:27] y/n? [04:28] you can `cd /proc` normally (unix/linux treats heaps of things as if files, 'everything is a file' in unix theory), but being a virtual file system, it doesn't exist on disk [04:29] oh ok [04:30] so when im viewing my "root" file system using ls -la or withing mc or some other file browser, and I see that dir called /proc, im actually looking at a dir that does not truly exist on disk, correct? [04:30] basically, the procfs is "mounted" to /proc as a mount point, correct? [04:31] well, the dir *itslef* probably exists as a blank dir called /proc, but i think you understand what im asking. [04:31] I would expect the /proc to exist actually (like you need to create a directory to `mount` something onto it), but it's contents are in the virtual-fs & thus contents won't exist on disk [04:31] ok [04:31] i get it now. thx. [04:40] so now i understand that the procfs filesystem is "mounted" onto the folder called /proc, and that... [04:40] ...the /mnt files are located on other partitions, CD, DVD, floppy, usb, etc. drives [04:40] ...but only /mnt and /proc are special in that regard, right? or are there others? [04:40] but all the other dirs that are just one step away from / are real dirs, correct? [04:41] like /boot, etc. [04:41] those are all real? or are some of them "unique" like /mnt and /proc? [04:45] If you `stat /proc` you'll note the directory itself appears as a normal directory; it's use case makes it special. Likewise too with /mnt. /mnt is often not used so you can `sudo cp` files to it and it acts like a normal directory... /proc however will be used on a normal boot of your system which makes it behave different [04:46] if you were to copy files to /mnt/blah/ when it wasn't in use, the files will exist on disk.. If you later mount a device called "blah" the subsequent mount will 'shadow' the contents of /mnt/blah/ and what appears from then on is the mounted drive... when you `umount` the device that was using /mnt/blah, you'll see once again the files you copied earlier in my example (if you follow me) [04:48] (the shadowning of directories & their contents via `mount` can be useful and times, but also scary if you do something which causes data you put there to be shadowed & thus appears to disappear..) [04:48] s/useful and times/useful at times [07:47] hi [07:48] what:'s up guys [07:56] sup [07:58] guiverc: oh thx [07:58] guiverc: ive scared myself like that before. [07:59] guiverc: especially when i first started out on linux (i started on gentoo, which does not automount anything, so therefore *I*, as a complete noob, had to do it by hand!) [08:00] guiverc: needless to say, i thought that i had accidentally deleted important files. [08:00] guiverc: i was praising God after I umounted [08:00] guiverc: and noticed my files were still there. [08:00] gentoo! a real newbies distro lol [08:01] lol [08:01] well at the time i didn't know a distro from a hole in the ground. [08:01] i thought "linux is linux". [08:01] :p [08:02] actually, there *is* a file you can change to make it automount upon boot [08:03] but those settings must be put into the file by hand, and at the time I was very confused about the nature of the Linux Directory Structure (I still am, actually) [08:04] in any event, aparently the file doesn't always get read at boot. perhpas it only gets read if other files don't exist or something. i dunno. [08:04] it some kinda configuration file [08:05] so i changed the contents, and successfuly saved the file. [08:05] but it had no effect. [08:05] so i ended up needing to always run mount and ntfs-3g by hand. [08:06] every day, every time i booted up. [08:06] very annoying. [08:06] at the time, i had no idea you could script stuff. [08:06] and when i first learned of the existence of "scripts" i kept referring to them as "batch files", which i still do very often. [08:07] cuz batch files are a Winshit thing. [08:07] I'm also a completely self-taught Winshit Power-User. [08:08] I had the advantage of using unix before windows was any good (windows v1), but this isn't support released and should be in #lubuntu-offtopic [08:08] I used to run a Hardened WinshitXP, but I never allow it to touch the web, despite all the Hardening steps which I always follow upon a new WinXP installation. [08:08] ok. [08:09] bye === root is now known as Guest27462 [11:49] hi there .. === ddevault_ is now known as ddevault [19:11] hi guys [21:22] es fantastico [22:28] hi friends.. whast up? [22:29] i installed compiz but it doesnt work perfect.. what should i do? === guiverc2 is now known as guiverc