Skip to forum content
CrunchBang Linux Forums
A discussion board for CrunchBang Linux users.
Search options (Page 1 of 7)
Add this to your menu.xml. Make adjustments for your path to JDarkRoom.
<item label="DarkRoom">
<action name="Execute">
<execute>
java -jar ~/bin/JDarkRoom.jar
</execute>
</action>
</item>

How is this resolved? Please share your ideas.
Jeroen,
Here is a tip. Type in a console
and let us know what the output. If working you will see the correct XML output that creates the "Places" menu
I suspect that the name of the command needed is actually
or not in your $PATH. Try fully qualifying the path like
/home/jeroen/.config/openbox/obpipmenu-places.py
And, I'm not sure that the script excepts command line variables. My script had to be edited to include and exclude the directories I want to appear in "Places". Try changing menu.xml like this:
<separator/>
<menu execute="obpipemenu-places.py" id="places" label="Places"/>
<separator/>
Jeroen wrote:I just get a small a small piece of the drop down list (1 x 2 mm).
This indicates script failure for one reason or another. Testing in the command line is always helpful.
arpinux wrote:a test of desktop integration

wallpaper mod of rfquerin'work
openbox theme on work...
gtk : macchiato
icon : buuf-deuce
fbpanel on top left
tint and conky on bottom
Love the camouflaged openbox menu. Having the menu background color the same and the wallpaper is a bright idea. With compositing on it is probably cool to see the menu text fade up from the background. It will be nice if the Openbox team can get the menu background set to transparency so non monochromatic backgrounds would work like this.
Can you give a hint as to how you changed the openbox menu bullet to the "#" character?
Thanks for sharing Danny. One thing I find harder and harder is remembering all the cool little functions, scripts and aliases I've created and collected over the years. I need a function that remembers all my functions??
This seem like a cool idea. One more thing to encrypt. How are potential conflicts between different versions of installed software on different machines handled? I'm thinking my eeepc1000 and my desktop. Big differences I think?
I use truecrypt on my usb thumbdrive and it works great for that. It does not support system encryption in Linux. This can only be done in Windows.
It would be cumbersome to use TrueCrypt for volume encryption as the volume would have to hashed with your password and mounted from a command line at every boot. This would be separate from normal login processes.
The advantage of a private folder and the forth coming "encrypted home directory" in jaunty are they unencrypt and mount as part of the normal booting/login processes.
The best best practice is to do full system encryption using the mini CD Ubuntu installer and crunchbang shell script described here. One tip is to consider your hash key carefully as you will have to present it at every boot.
I have this setup on my desktop and love it. I do not notice any degradation in speed or boot times. This desktop has a dual core AMD 3.2gHz with fast SATA drives. A bit different from the eeepc1000.
I saw a review putting full disk encryption on a eeepc 901 machine and comparing it to a eeepc 901 without encryption. Then they performed a variety of speed tests and compared to non encrypted eeepc 901 the encrypted one was noticeably slower. http://www.phoronix.com/scan.php?page=a
&num=1 (Sorry about the visually coarse ads on this site. Page 5 has good info.)
I find the eeepc to such a dog slow machine now, I'm afraid what will happen if I us full system encryption. There are a few people over on eeeforums that confirm that this slows the eeepc even more than otherwise. I'm, waiting for encrypted home directory to see if how that performs.
pakman wrote:@ Kestrel: I really like the idea of a separate file. Where abouts in the .bashrc would you add the additional line? Or is it possible to just add it anywhere?
pakman, I'd go with the safer suggestion by rantak. As far as placement, I don't think it matters though mine in near the middle.
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# Set some colors
BLACK='\e[0;30m'
BLUE='\e[0;34m'
GREEN='\e[0;32m'
CYAN='\e[0;36m'
RED='\e[0;31m'
PURPLE='\e[0;35m'
BROWN='\e[0;33m'
LIGHTGRAY='\e[0;37m'
DARKGRAY='\e[1;30m'
LIGHTBLUE='\e[1;34m'
LIGHTGREEN='\e[1;32m'
LIGHTCYAN='\e[1;36m'
LIGHTRED='\e[1;31m'
LIGHTPURPLE='\e[1;35m'
YELLOW='\e[1;33m'
WHITE='\e[1;37m'
NC='\e[0m' # No Color
# don't put duplicate lines in the history. See bash(1) for more options
export EDITOR=/usr/bin/vim # the one and only editor
export HISTFILESIZE=300000 # save 300000 commands
export HISTCONTROL=ignoredups # no duplicate lines in the history.
export HISTSIZE=100000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
shopt -s histappend
export PROMPT_COMMAND='history -a'
# enable color support of ls and also add handy aliases
if [ "$TERM" != "dumb" ]; then
eval `dircolors -b`
alias ls='ls --color=auto'
#alias dir='ls --color=auto --format=vertical'
#alias vdir='ls --color=auto --format=long'
fi
. /home/will/.aliases
. /home/will/.functions
# export PATH=/opt/openoffice.org3/program:/home/will/bin:$PATH
# make less more friendly for non-text input files, see lesspipe(1)
#[ -x /usr/bin/lesspipe ] && eval "$(lesspipe)"
# set variable identifying the chroot you work in
if [ -z "$debian_chroot" -a -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# A color and a non-color prompt:
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w \$ '
# Comment in the above and uncomment this below for a color prompt
#PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\] \$ '
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007"'
;;
*)
;;
esac
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc).
#if [ -f /etc/bash_completion ]; then
# . /etc/bash_completion
#fi
# This line was appended by KDE
# Make sure our customised gtkrc file is loaded.
export GTK2_RC_FILES=$HOME/.gtkrc-2.0
#------------------------------------------
#------WELCOME MESSAGE---------------------
# customize this first message with a message of your choice.
# this will display the username, date, time, a calendar, the amount of users, and the up time.
clear
# Gotta love ASCII art with figlet
figlet "Welcome, " $USER;
echo -e ""
echo -ne "Today is "; date
echo -e ""; cal ;
echo -ne "Up time:";uptime | awk /'up/'
echo "";
#------------------------------------------
#------ENCRYPTION/DECRYPTION--------------
# requires gpg
# the proper way to use these functions is simply to enter "encrypt filename" or "decrypt filename"
encrypt ()
{
gpg -ac --no-options "$1"
}
decrypt ()
{
gpg --no-options "$1"
}
#------------------------------------------
#------Extraction of compressed files--------------
# from ARCH Wiki
extract () {
if [ -f $1 ] ; then
case $1 in
*.tar.bz2) tar xvjf $1 ;;
*.tar.gz) tar xvzf $1 ;;
*.bz2) bunzip2 $1 ;;
*.rar) rar x $1 ;;
*.gz) gunzip $1 ;;
*.tar) tar xvf $1 ;;
*.tbz2) tar xvjf $1 ;;
*.tgz) tar xvzf $1 ;;
*.zip) unzip $1 ;;
*.Z) uncompress $1 ;;
*.7z) 7z x $1 ;;
*) echo "don't know how to extract '$1'..." ;;
esac
else
echo "'$1' is not a valid file!"
fi
}
Kind of shaggy:/
Wouldn't that be spelled "Curbee"?
corenominal wrote:About that, personally I am not sure that duplicating the articles on the Wiki is totally desirable -- I was thinking more in terms of using TiddlyWiki to produce a guide/handbook with Tiddlers which could be linked to from Openbox's main menu, as opposed to trying to distribute a full community wiki.
Yes, I too was not thinking that all the articles would be reproduced but maybe an appropriate subset of articles. Much work has already been done. The current online DokuWiki could act as a sort of repository or CSV for the help documentation. Using DokuWiki's built in tools for version control and collaboration system. Otherwise possibly Launchpad might work. I'm not familiar with Launchpad enough to know but am willing to learn.
Yes, this should live locally in the Openbox main menu, in the "Help" section.
Two of my favorite Linux applications are command line tools.
will search the names and descriptions of all the packages available. Great for finding hidden gems via apt.
will search through all man pages for a string. Great for us who can't remember ....
I like to keep all my aliases in a separate file for mobility. I then add this line to my .bashrc
Contents of /home/will/.aliases before swiping some of yours:D
# some more ls aliases
alias ls='ls -hF --color' # add colors for filetype recognition
alias lx='ls -lXB' # sort by extension
alias lk='ls -lSr' # sort by size
alias la='ls -Al' # show hidden files
alias lr='ls -lR' # recursice ls
alias lt='ls -ltr' # sort by date
alias lm='ls -al |more' # pipe through 'more'
alias tree='tree -Cs' # nice alternative to 'ls'
alias ll='ls -l' # long listing
alias l='ls -hF --color' # quick listing
alias lsize='ls --sort=size -lhr' # list by size
alias l?='cat /home/will/technical/tips/ls'
alias lsd='ls -l | grep "^d"' #list only directories
Command substiution
alias ff='sudo find / -name $1'
alias df='df -h -x tmpfs -x usbfs'
alias psg='ps -ef | grep $1'
alias h='history | grep $1'
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
alias which='type -all'
alias ..='cd ..'
alias path='echo -e ${PATH//:/\\n}'
alias vi='vim'
alias du='du -h --max-depth=1'
#Personal Help
alias a?='cat /home/will/.alias.help'
alias f?='cat /home/will/.function.help'
alias dn='OPTIONS=$(\ls -F | grep /$); select s in $OPTIONS; do cd $PWD/$s; break;done'
alias help='OPTIONS=$(\ls ~/.tips -F);select s in $OPTIONS; do less ~/.tips/$s; break;done'
#Truecrypt
alias mtrue='sudo truecrypt /media/usbdisk/kestrel.tc ~/kestrel'
alias utrue='sudo truecrypt -d'
#Rsync
#alias usbb='rsync -avz /media/usbdisk/ ~/backup/usb/'
#Timestamps
alias stamp='date "+%Y%m%d%a%H%M"'
alias da='date "+%Y-%m-%d %A %T %Z"'
#show most popular commands
alias top-commands='history | awk "{print $2}" | awk "BEGIN {FS="|"} {print $1}" |sort|uniq -c | sort -rn | head -10'
# search for a package
alias search="apt-cache search"
# empty trash
alias trash="rm -fr ~/.Trash"
TiddlyWiki has some server extenders that would allow the importation of articles from other sources, only DokuWiki is not included. "Raw Text" might work. Possibly one of our resident script masters can create an adapter of our own. It doesn't seem documented how to use this Server Adaptors. I assume we add the code somewhere and then in the import server type the adapter becomes an option.
http://www.tiddlywiki.org/wiki/Server_Adaptor_Mechanism
Figuring out the importation of the articles seems to me to be the biggest challenge.
You shouldn't have to set anything in any config file to do copy on selection. The trick is that anything selected with the mouse can be pasted with the mouse. Try this - in a terminal enter this command.
Watch life flash before your eyes.;)
Pick one of the commands listed and highlight it with the mouse. Just the command and not the history number. Now without click on anything hover the mouse near the command prompt and preform a middle mouse click. On a eee pc click both trackpad buttons at the same time. This will insert the high lighted text on the command line. This takes a little coordination and practice.
This works in the terminal and in a gui and between the terminal and a gui. This technique is separate from the 'cut and paste' and allows you to have two peices of text in the resister, one pasted via the middle mouse button and on pasted via ctrl-c. Works on all unixes and linuxes.
fhsm wrote:kestrel wrote:...nslug...
That's cool. I've always wondered about those. Do you have debian on it? I've got enough old computers sitting around that the idea of fighting to make it work like a full system never did much for me. My power bill is making me give it a second thought.
Yes it runs debian etch. Now only $62 at Amazon. If I remember correctly only 5 watts and fanless. I have a 160g usb drive that is usb powered. Does my DAAP, NAS, podcatching, torrents, rsync backup repository, sometimes irssi. Really a cool device.
Really nice evolution. Inspiring.
iggykoopa, the quality is great. Links are a problem. This particular html to pdf converter only does one page at a time. Includes unnecessary page decorations and names the pdf poorly. Bit inefficient. It looks like Doku's built in converter does the same. The documentation describes putting a button in the include header that allows the user to manually request a pdf download of the current page. Untested but links likely still a problem and again one page at a time.
I wonder about the approach of setting up a local DokuWiki and setting the root part of the url to //localhost so that all links that referred //crunchbanglinux.org/wiki/ referred to //localhost instead. This seems maybe an overkill. Setting up a webserver and installing a wiki and converting links. This is what made tiddlywiki so attractive.
Lets keep looking around.
Sorry to hear your problems. Mine just worked. No setup at all. Opened Rhythmbox 0.11.6 and daap share was visible in the left hand pane. I'm using Firefly (mt-daap) on a nslug pointing at the same port. Never had to add, Rhythmbox did self discovery.
If you have a eeepc then this tip will work for disabling the tap feature of the trackpad. Different touchpads have different ways of controlling the tap.
http://www.array.org/ubuntu/elantech.html
iggykoopa wrote:if we aren't totally set on having the local version as a wiki as well there are some tools to export dokuwiki to pdf http://www.dokuwiki.org/tips:pdfexport . Just another idea that might be easier to implement. I really like the idea of having easily accessible offline documentation, maybe we can start making some screencasts as well for the more visually inclined.
This could work. Who has access to the export functionality so we can see a mockup/sample? A PDF could be easily folded into the menu using the piped menu ebook reader Philip coded here.
Without seeing it, it sounds like a way to quickly get something in play. Something more sophisticated may come out of it.
These rules have been implemented to prevent various counter reloading schemes:
* Repeated page and counter reloads in short or regular intervals are not permitted. If you are inclined to set up cron jobs to repeatedly "wget" your favourite distro's page counter, then please do yourself a favour and go to see a psychologist. You need help.
OH OH! Time to make appointment?:D
<item label="cb_ninjawork.2009_01_31_18_55_49.0.svg">
<action name="Execute">
<execute>pcmanfm '/home/foom/cb_ninjawork.2009_01_31_18_55_49.0.svg'</execute>
</action>
Looks as thought there is a bad character right after the "k" in cd_ninjawork. It appears to be a Unicode Character 'CANCEL' (U+0018) not likely well handled by xml parser. Try removing the character.
Sweet! It is like having Gnome-do inside of the Firefox.
Mich wrote:Isn't it possible to just maintain it as an article in CrunchBang's wiki?
It is version controlled and the community can then contribute to it 
The goal is to have our cake and eat it too.
Maintain articles on line and periodically export ->convert -> package -> distribute for off line use.
The only way for this process to be sustainable is if it can be automated.
iggykoopa wrote:I had mentioned to core in irc ikiwiki, not sure if it will match what we need but it has the capability to be used as a distributed wiki with git. I'll try installing it if I remember tonight and see if it would be suitable. It would be nice to have something like tiddlywiki though that doesn't need a server, also updates can be pushed easily through the repos. maybe we could just put a copy of tiddly in launchpad and track changes through bzr?
The challenge is not so much having a distributed wiki as the online wiki could be used for collection and vetting of articles and has a built in versioning system. The challenge would be converting the wiki markup from one application like dokuwiki markup to tiddly wiki markup and in this example compiling many articles into a single file. The two markup schema's are not the same and a conversion process would have to run to make the on line version packageable. As a example, compare the online "Release Notes" with the unconverted "Release Notes" in the mockup.
Posts found [ 1 to 25 of 163 ]
Forums powered by PunBB. Hosted by Linode.
Copyright © CrunchBang Linux.
Proudly powered by Debian GNU/Linux.
Debian is a registered trademark of Software in the Public Interest, Inc.