SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 Re: Tips, Tricks & Scripts » Thunar - Create New File » 2015-04-19 18:31:22

Isn't there specifically an option in Thunar to create an empty file? Right click in Thunar -> Create Document -> Empty File

#2 Re: Artwork & Screenshots » April 2015 Screenshot Thread » 2015-04-19 00:17:47

I just installed compton today on my Arch machine. I'm a sucker for quickly faded in windows and menus and gentle shadows on floating windows

http://i.imgur.com/SMAgVn9m.png

#3 Re: Off Topic / General Chat » Show your packg number » 2015-04-15 18:02:09

I'm happy with my new Arch install

woodape[etc]$ pacman -Q|wc -l
650

I have libreoffice, skype, firefox, thunderbird, etc. I can't imagine needing more packages

#4 Re: Off Topic / General Chat » How clean is your $HOME? » 2015-04-14 18:10:57

KrunchTime wrote:

anki is the reason I have two documents folders.  It insists on using Documents instead of documents to store addons and options.  roll

Do you have a "$HOME/.config/user-dirs.dirs" file? If so does it have

XDG_DOCUMENTS_DIR="$HOME/documents/"

#5 Re: Off Topic / General Chat » How clean is your $HOME? » 2015-04-14 18:07:36

This feels a bit like airing out dirty laundry...

woodape[~]$ la
.              .config    .fehbg      .macromedia    torrents      .vimrc
..             .dbus      .fonts      .mozilla       .urxvt        .Xauthority
.adobe         documents  .gimp-2.8   .screenlayout  videos        .xinitrc
.bash_history  downloads  .gnupg      .Skype         .vim          .Xresources
.bash_logout   .dropbox   .gtkrc-2.0  .stata12       .viminfo
.bash_profile  Dropbox    .icons      .themes        .viminfo.tmp
.bashrc        dwm        images      .thumbnails    .viminfx.tmp
bin            .dwm0      .lesshst    .thunderbird   .viminfy.tmp
.cache         dwm1       .local      tmp            .viminfz.tmp

Thankfully I did the laundry last week smile

#6 Re: Help & Support (Other) » Crunchified Debian Installs - How Are You Exiting/Shutting Down? » 2015-04-12 15:44:35

M.I.H.H wrote:

i've installed debian jessie-testing & wheezy 'netinstall'

So which one is it? If you are on a Jessie machine you should be using bl-exit to make use of the systemd calls

#7 Re: Help & Support (Other) » Crunchified Debian Installs - How Are You Exiting/Shutting Down? » 2015-04-12 13:16:50

M.I.H.H wrote:

How do i use cb-* script on debian, i've installed debian jessie-testing & wheezy 'netinstall' and also i've done customize the theme like #!, but i can't execute the cb-* scripts (the script is in /usr/bin with executable permission) from openbox

What does your openbox entry look like? Also maybe this should be it's own help request thread?

#8 Re: Ideas & Suggestions » Proposed BunsenLabs default backgrounds » 2015-04-12 12:13:56

These look great! Lots of great options in that repo smile Thanks for all the hard work damo et.al.

#9 Re: Artwork & Screenshots » April 2015 Screenshot Thread » 2015-04-11 21:55:43

Head_on_a_Stick wrote:

Trying out the latest git pull of DWM -- with XFT support (again)!
smile
Direct link:
http://postimg.org/image/ab0j9x5ib/

wink
Pl34EVxm.png

#10 Re: Help & Support (Other) » Crunchified Debian Installs - How Are You Exiting/Shutting Down? » 2015-04-11 21:14:03

In a less-than-bunsified setup I'm running the following little script which is bound to Super-X:

#!/bin/bash
systemctl $(echo -e "poweroff\nreboot\nsuspend\nhibernate" | dmenu -p "Power Options:")

Not exactly bunsen themed but super light and effective.

#11 Re: Ideas & Suggestions » Pulse or Alsa/Jack in BunsenLabs » 2015-04-06 10:37:52

I've found that Pulse does a lot of things better than Alsa, the biggest being Pulse's ability to split audio output from various applications to different channels. Also much easier to configure audio to output through HDMI. Also Skype requires it. Also, also, also...

I have headphones plugged in all the time as well as a TV with an HDMI cable. Pulse allows me to always have Skype conversations or Youtube videos to play through headphones, but everytime I play a video on VLC the audio goes through the TV. I remember trying to look for an Alsa-only workaround for this a while ago, but couldn't get anything to work, let alone something that is even close to as easy as opening pavucontrol and clicking a few times.

I know some people are against Pulse (there's a very long thread about it), but I haven't had an issue with it recently. If Pulse isn't in the default, it'll definitely be one of the first things I install. But considering that bl has been taking the view that it is best to make the user add things than remove things, maybe it should be put in bl-welcome as an optional install with the reminder that several popular programs (eg. Skype) depend on it, it provides a few useful functions lacking in Alsa (eg. channel splitting), but is somewhat controversial (...not sure why, does it have issues with certain hardware? Are the developers jerks?).

#12 Re: Ideas & Suggestions » Multimedia pipemenu » 2015-04-01 06:26:02

damo wrote:

Any thoughts for a desktop recorder/capture application?

I've been using gtk-recordmydesktop to record presentations and such. I really like it. Lightweight, no frills, just records the screen or a portion of the screen and the audio and saves it to a video file. Easy peasy.

#13 Re: Off Topic / General Chat » Show your packg number » 2015-03-29 20:01:40

[woodape@archbox ~]$ pacman -Q | wc -l # count
627

Hmmm. Much less than my Sid machine, makes me wonder if I should convert to Arch with BL on top...

#15 Re: Off Topic / General Chat » CrunchBang Plus Plus...the Community Fork of CrunchBang?! » 2015-03-27 19:58:35

Sector11 wrote:

And there is this: CrunchBang File Repository

I wonder if this one is a relic. From the site:

This project will only be funded if at least £500 is pledged by 13th October 2014

Though all of these guys are wrong to claim that anything other than BunsenLabs is the community continuation of crunch bang, the strongest way to combat these claims is to get a solid version of BL rolled out soon as it can be.

#16 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-27 15:56:31

Sector11 wrote:

DUH!!!  OK, that works ...

NICE!  I like it!

Great! I think the code could use a little cleaning up, and I'd like to see a few more people give it a test run and try and break it (though you are notoriously good at that yourself  ]:D  ), but otherwise it seems to work as intended.

#17 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-27 12:57:36

Sector11 wrote:

I don't like the idea that every "Unmanaged Conky" is killed automatically when I choose to run "bl-top"

I can see in your picture that you're in replace mode. Click 'Toggle Load / Kill' mode at the bottom and then that won't happen. 'Replace' mode is made so that all open conkies are killed and the "replaced" with the conky / conky group that you select. 'Load / Kill' mode allows you to "load" and "kill" individual conkies / conky groups without interfering with any open conkies, including the ones that are "unmanaged".

#18 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-27 06:52:52

Smack smacz?  8.(

For references though, @kbmonkey updated the first post of this thread with instructions on how to get the switcher from my github, what command to put in the rc.xml file to see the switcher in the menu, and the command to put in the openbox autostart file to get the conkies in the 'session.log' file produced by the script to be launched at startup.

The first post where I switched to github is here, and I haven't posted code directly in this thread since - it's a pain to try and update long code by editing posts, especially since in python spacing matters very much. Github makes it easy to obtain the code and any updates, as well as making it easy to keep track of bugs, feature requests, etc.

Sector11 wrote:

Does it also include the "tint2" pipemenu?

There is a tint2 version on the github page. It isn't much more than replacing any instance of the word "conky" with "tint2", and removing the "-q" arguments from the relevant lines.

In my screenshots, both pipemenus are listed under an "Appearance" menu because I intend to do a few more theming pipemenus. Probably one for terminal colors, lightdm, and wallpapers - these would all be somewhat simpler than the conky-switcher as there would be no 'Load/Kill' mode. I haven't got time to work them out just yet, but to anybody who wants to figure them out please fork my repo and then submit a pull request when you've got something working!

#19 Re: Help & Support (Crunchbang 11 "Waldorf") » [SOLVED] Run two commands on obmenu » 2015-03-24 08:37:34

The above is the easiest way to do it, but for reference to other #!ers who come across this, you can split the commands in the OB menu like so:

<item label="Twofer">
    <action name = "Execute">
        <execute>
            bash -c 'vnstati -h -i eth0 -o ~/images/scrot/day.png'
        </execute>
    </action>
    <action name = "Execute">
        <execute>
            bash -c 'viewnior ~/images/scrot/day.png'
        </execute>
    </action>
</item>

#20 Re: Off Topic / General Chat » Linux and malware? » 2015-03-24 08:31:13

pvsage wrote:
Head_on_a_Stick wrote:

Remember: if you can't `apt-get` it, it's not worth having!

I'm working up a "what has been decided" type of post, and since the above so succinctly and eloquently expresses part of my philosopy for BunsenLabs, I am shamelessly stealing this. ]:D

So what about Dropbox or Skype? Until we convince everybody using Windows to move to something open source (owncloud and pidgin?) I think many users are stuck downloading deb files. Waldorf comes with that wonderful Dropbox pipemenu to install and run it, but it isn't just an apt-get away...

#21 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-19 13:46:48

smacz wrote:

Honestly, I can't find any unexpected behavior in this program. I'll give my standing ovation to @woodape. Nice job man. And thanks.

Thanks for the thanks! I'd personally like the unmanaged conkies which are launched without config files to come up as "Unknown Conky 1", "Unknown Conky 2" etc. but the way it is right now is descriptive enough and functional. The tint2 version is basically the same thing. Together they make for some quick theming action smile

Here's the full menu:

mLkwtyQl.png

Here are some sequential screenshots to showcase the functionality:

H7mUDVCm.png

A2gzaNzm.png

x839wdGm.png

kHveRphm.png

ZofJfnem.png

lQOBf9Om.png

#22 Re: Off Topic / General Chat » Grammar Pet Peeves » 2015-03-18 07:46:06

pvsage wrote:

Regarding the informal second person, I'm really not advocating a return to early Modern English; I just think "you" for singular/plural is a little grammatically lazy.  It would be nice to be able to read something and know if someone were addressing me individually (thou/thee/thy/thine) or the forum as a group (ye/you/your/yours).  (Of course, appropriate conjugations of "to be" would probably be required, but other than that...)

Plural of "you" is "y'all" as far as I'm concerned.

Brooklyn Steryotype1:  "Hey what are youse guys up to?"
Southern Steryotype1: "What the h**l are you sayin' 'youse guys'? It's 'What are y'all up to?'. Don't be throwin' in extra words."
Actual British/English Person : "Americans...."

#23 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-18 07:18:50

kbmonkey wrote:

I'm liking the direction this is taking and am keen to play with the modified code  8)
...
Edit: had a quick look at the new look of this menu and, oh my hat, great work!

Glad you're liking it! The headers idea is definitely attributable to @smacz

kbmonkey wrote:

To make things easier I am going to update the original post to point to the GitHub repository woodape set up, to make getting new versions easier  O:)

Thanks for point to the github, it is way easier than trying to continually update posts here. For those who are just looking at the end of this thread, the repository is https://github.com/woodape/bl-switcher and you can get the code for just the conky-switcher by saving https://raw.githubusercontent.com/wooda … witcher.py
or use kbmonkey's nifty command-line:

cd ~/bin && wget -N https://raw.githubusercontent.com/woodape/bl-switcher/master/bl-conky-switcher.py && chmod +x bl-conky-switcher.py

Any further bug reports can of course be posted in this thread, but I think it would be better to start logging them as issues on the github page.

Speaking of bugs...

smacz wrote:

EDIT: REVOKED -- behavior still present when invoked with -qc as well as just -c

Another reason to move to github:

woodape wrote:

pkill is already implemented in the script to handle any conkies launched outside of the script like

conky -q -c $HOME/.config/conky/bl-right.conky

so long as a full path is given when launching the conky. It wouldn't be so difficult to change it to kill conkies that only have the '-c' tag as well.

I would have logged this as an open issue when I posted it. In any case, the latest code handles conkies launched outside of the script with the  '-c' , '-qc', and '-q -c' arguments.

smacz wrote:

In REPLACE mode it acts as a "killall". The entries show up great on the menu, but the functionality is just not there.

I wasn't able to replicate this on my machine. Before the edit for additional arguments, trying to kill unmanaged conkies launched with only a '-c' or a '-qc' argument didn't kill the unmanaged conkies or any other conkies. Am I reading this weirdness wrong?

smacz wrote:

but I feel that the new functionality can be less ambiguous. Any chance you would put a separator tag at the top containing which method we're currently in?

Great idea! I put it in the latest version, much better looking I think smile

Sector11 wrote:

9. Toggle Load / Kill -  conkys still there
10 killed each individually and the went ...
11 tried again and got into a situation where the conkys were gone BUT the menu said they were there and so did the session log but "killall conky" reported no conkys, but look at the menu and the log:

I'm reading this as "if conkies that are launched by the script are killed outside of the script they should no longer appear in the 'session.log'". I've added the functionality that if no conkies are open, then the 'session.log' file is flushed to reflect that nothing is open. This needs to be changed when I get a chance to "if a conky is in the 'session.log' file but isn't open, remove it from the 'session.log' file". Issue opened in github smile

Also thanks to @detinith, the code in the github has comments throughout. It is a very bad habit of mine to not be continuously commenting throughout code, one which I'm trying to get rid of. Also @detinith has made it more 'python-y', another good habit I need to pick up.

#24 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-16 18:20:48

Sector11 wrote:

I'm not a coder so I am about to find out if:

45 CONFIGSHOME = os.path.join(/media/5, 'BL-conky')

will work.  I love breaking things.  ]:D ]:D
...
.. it will probably break. ...
EDIT:  Yup!

Yes this is a particular python-y thing. The 'os.path.join()' function is how python joins together directories so that the code is compatable across different filesystems. This is how it was coded by @kbmonkey and is the proper way to do things in python apparently.
You almost had the right thing, every directory must be a new argument. So just take out the slashes and put '5' in a new argument:

CONFIGSHOME = os.path.join('media' , '5' , 'BL-conky')

Putting in

CONFIGSHOME = '/media/5/'

has unwanted effects, but

CONFIGSHOME = '/media/5'

seems to work - it just isn't proper python.

Sector11 wrote:

Not even a chance to break things - yet, OK, it's a comment BUT.

21 #       + Added support for single conkies in $HOME/.config/conky

and a hardcoded let's break the CONFIGSHOME variable at line 98:

98                    sh -c 'echo "%(toggle)s" > $HOME/.config/conky/session.log'

and again:

190        print('<openbox_pipe_menu><item label="Place your .conky files under ~/.conky to use this switcher."></item></openbox_pipe_menu>')

yikes
Yep you're totally right, these should be changed. I've just updated the code in my last post.

Sector11 wrote:

Also I see bl-conky-switcher-pipemenu-resume.sh has:

$HOME/.config/conky/session.log

hardcoded.

...this is hardly hardcoded. It's the only mention of the file in a script that's all of 8 lines. To add a variable at line 2 that is referenced once at line 8 seems a bit pointless.

It does bring up the fact that there are currently 2 scripts to make this thing work fully. I'm sure another function can be added in "bl-conky-switcher-pipmenu.py" that checks if an argument 'resume' is passed and then loads all conkies in the 'session.log' file. This would eliminate the need for the twofiles and solve the issue of specifying a directory once and only once.

Thus adding

"bl-conky-switcher-pipmenu.py resume" 

to the openbox autostart file to get the resume functionality currently provided by the separate script  "bl-conky-switcher-pipemenu-resume.sh".

#25 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-15 16:07:16

Sector11 wrote:

Part of the reason I suggested seeing if killing a conky (lets use the ~/.config/conky structure) with:

pkill -xf "conky -c $HOME/.config/conky/bl-right.conky"
247                        ckill="conky -q -c " + configFile
248                        subprocess.Popen(['pkill', '-xf', ckill ])
...
270                        ckill="conky -q -c " + sys.argv[1]
271                        subprocess.Popen(['pkill', '-xf', ckill ])

pkill is already implemented in the script to handle any conkies launched outside of the script like

conky -q -c $HOME/.config/conky/bl-right.conky

so long as a full path is given when launching the conky. It wouldn't be so difficult to change it to kill conkies that only have the '-c' tag as well.

Sector11 wrote:

Please - I beg you - don't take this to conkys outside of whatever directory structure you are using now.  I don't want to wait for the pipemenu to call up 2000+ conkys, if the session log ever recorded my conky daily usage it would be popping up test conkys all over the place.  But then, I simply wouldn't use it if that was the case.

KISS it!

Totally agree, that would be a nightmare! The script does recognize running conkys [is it conkys or conkies??] that were started outside of the script, and gives the option to kill these, but it doesn't look anywhere outside of the directory specified by

45 CONFIGSHOME = os.path.join(USERHOME, '.config','conky')

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo