Comments for Lâmôlabs http://www.lamolabs.org/blog Lame Oh Labs .... Linux & Tech! Is there anything else? Fri, 12 Mar 2010 00:24:52 -0500 http://wordpress.org/?v=2.9.2 hourly 1 Comment on Managing WordPress Posts with vim by slmingol http://www.lamolabs.org/blog/2083/managing-wordpress-posts-with-vim/comment-page-1/#comment-573 slmingol Fri, 12 Mar 2010 00:24:52 +0000 http://www.lamolabs.org/blog/?p=2083#comment-573 I'm using vim & gvim version 7.2 on a Fedora 10 system, but I've had success on more recent versions of Fedora as well and also CentOS 5 too. <pre lang="bash"> % gvim --version VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 2 2009 01:26:56) Included patches: 1-148 Modified by <bugzilla@redhat.com> Compiled by <bugzilla@redhat.com> Huge version with GTK2 GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile +python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save system vimrc file: "/etc/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "/etc/gvimrc" user gvimrc file: "$HOME/.gvimrc" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=1 -D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE -I/usr/include/python2.5 -pthread -I/usr/lib/ruby/1.8/i386-linux Linking: gcc -L. -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE -L/usr/local/lib -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lXt -lselinux -lncurses -lacl -lgpm -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE -L/usr/local/lib -L/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE -lperl -lresolv -lutil -lc -L/usr/lib/python2.5/config -lpython2.5 -lutil -Xlinker -export-dynamic -lruby -lm </pre> You might be having a problem with the vim package on your distribution of Linux. I encountered a problem where ruby support wasn't compiled into vim and I needed to do this myself manually. Check out my blog post on "Fixing Ruby Support in vim on Fedora 10, 11 and CentOS 5":http://www.lamolabs.org/blog/2662/fixing-ruby-support-in-vim-on-fedora-10-11-and-centos-5-installing-the-vim-textile-plugin/. I’m using vim & gvim version 7.2 on a Fedora 10 system, but I’ve had success on more recent versions of Fedora as well and also CentOS 5 too.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

% gvim --version
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul  2 2009 01:26:56)
Included patches: 1-148
Modified by <bugzilla@redhat.com>
Compiled by <bugzilla@redhat.com>
Huge version with GTK2 GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent 
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
+cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic 
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path 
+float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand 
+jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap 
+menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm 
-mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte 
+multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript 
+printer +profile +python +quickfix +reltime +rightleft +ruby +scrollbind 
+signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary 
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
 +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo 
+vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim 
+xsmp_interact +xterm_clipboard -xterm_save 
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "/etc/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12     -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=1    -D_REENTRANT -D_GNU_SOURCE -DDEBUGGING  -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm  -I/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE  -I/usr/include/python2.5 -pthread  -I/usr/lib/ruby/1.8/i386-linux 
Linking: gcc   -L.  -rdynamic -Wl,-export-dynamic  -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE   -L/usr/local/lib -o vim   -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lXt -lselinux  -lncurses -lacl -lgpm   -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE  -L/usr/local/lib  -L/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE -lperl -lresolv -lutil -lc -L/usr/lib/python2.5/config -lpython2.5 -lutil -Xlinker -export-dynamic  -lruby -lm

You might be having a problem with the vim package on your distribution of Linux. I encountered a problem where ruby support wasn’t compiled into vim and I needed to do this myself manually. Check out my blog post on Fixing Ruby Support in vim on Fedora 10, 11 and CentOS 5.

]]> Comment on Managing WordPress Posts with vim by justin http://www.lamolabs.org/blog/2083/managing-wordpress-posts-with-vim/comment-page-1/#comment-572 justin Thu, 11 Mar 2010 15:18:09 +0000 http://www.lamolabs.org/blog/?p=2083#comment-572 Good work! the Blogit seems great, I just manage to have Blogit works with a special patched GVim (which compiled with python2.6). however, i am not able to get this working in Linux. I am using the latest GVIM, which is 7.2, with Blogit1.43, 1.42, 1.4 or 1.3. none of them works, i see errors like "Cannot Import Name CalledProcessError". it is believed GVim is still built on Python2.4 that does not support some function/lib, but i haven't found a patched version like that in Windows... ok, here also come with a question: could you please share some info about which vim are you using? i really like to have the ability to blog under linux/vim many, many, many thanks in advance... Good work!

the Blogit seems great, I just manage to have Blogit works with a special patched GVim (which compiled with python2.6).
however, i am not able to get this working in Linux. I am using the latest GVIM, which is 7.2, with Blogit1.43, 1.42, 1.4 or 1.3.
none of them works, i see errors like “Cannot Import Name CalledProcessError”.
it is believed GVim is still built on Python2.4 that does not support some function/lib, but i haven’t found a patched version like that in Windows…

ok, here also come with a question: could you please share some info about which vim are you using? i really like to have the ability to blog under linux/vim

many, many, many thanks in advance…

]]> Comment on Git and subversion setup on CentOS 5 by slmingol http://www.lamolabs.org/blog/401/git-and-subversion-setup-on-centos-5/comment-page-1/#comment-555 slmingol Sun, 20 Dec 2009 02:11:26 +0000 http://www.lamolabs.org/blog/?p=401#comment-555 Glad it helped someone out. Nice to be able to give something back! Glad it helped someone out. Nice to be able to give something back!

]]> Comment on Git and subversion setup on CentOS 5 by wkm http://www.lamolabs.org/blog/401/git-and-subversion-setup-on-centos-5/comment-page-1/#comment-554 wkm Sun, 20 Dec 2009 00:04:51 +0000 http://www.lamolabs.org/blog/?p=401#comment-554 Hey. Thanks for posting your git-daemon file; I shamelessly reused it on my site :) Cheers. Hey. Thanks for posting your git-daemon file; I shamelessly reused it on my site :)

Cheers.

]]> Comment on [one-liner]: Copying & Moving Files efficiently with xargs by slmingol http://www.lamolabs.org/blog/2745/one-liner-copying-moving-files-efficiently-with-xargs/comment-page-1/#comment-553 slmingol Fri, 18 Dec 2009 01:50:55 +0000 http://www.lamolabs.org/blog/?p=2745#comment-553 That's a terrific point. Thanks for bringing it up. I've gotten out of the habit of using spaces in files & directories but if you run this on a filesystem that does have files with spaces and/or a directory that may include files from a windows system then odds are you may run into files with spaces. Thanks! That’s a terrific point. Thanks for bringing it up. I’ve gotten out of the habit of using spaces in files & directories but if you run this on a filesystem that does have files with spaces and/or a directory that may include files from a windows system then odds are you may run into files with spaces. Thanks!

]]> Comment on [one-liner]: Copying & Moving Files efficiently with xargs by Rodrigo http://www.lamolabs.org/blog/2745/one-liner-copying-moving-files-efficiently-with-xargs/comment-page-1/#comment-552 Rodrigo Thu, 17 Dec 2009 15:04:11 +0000 http://www.lamolabs.org/blog/?p=2745#comment-552 find . -type f -ctime -1 | xargs cp -t /some/other/directory theres a problem with that command wich is revealed if you try to copy files with spaces in their names, just add -0 option to xargs find . -type f -ctime -1 | xargs -0 cp -t /some/other/directory find . -type f -ctime -1 | xargs cp -t /some/other/directory

theres a problem with that command wich is revealed if you try to copy files with spaces in their names, just add -0 option to xargs

find . -type f -ctime -1 | xargs -0 cp -t /some/other/directory

]]> Comment on [one-liner]: Copying & Moving Files efficiently with xargs by slmingol http://www.lamolabs.org/blog/2745/one-liner-copying-moving-files-efficiently-with-xargs/comment-page-1/#comment-508 slmingol Fri, 16 Oct 2009 05:35:03 +0000 http://www.lamolabs.org/blog/?p=2745#comment-508 Yup know all about find's -exec switch. The problem with -exec is that it gets called everytime find finds a file. So for example if find finds 10,000 files, it would literally call -exec 10,000 times. This is what I was trying to avoid by leveraging xargs. By using xargs you in effect are minimizing the number of times you'll be calling the body of what gets called in the -exec argument to find. Yup know all about find’s -exec switch. The problem with -exec is that it gets called everytime find finds a file. So for example if find finds 10,000 files, it would literally call -exec 10,000 times. This is what I was trying to avoid by leveraging xargs. By using xargs you in effect are minimizing the number of times you’ll be calling the body of what gets called in the -exec argument to find.

]]> Comment on [one-liner]: Copying & Moving Files efficiently with xargs by Vincent http://www.lamolabs.org/blog/2745/one-liner-copying-moving-files-efficiently-with-xargs/comment-page-1/#comment-507 Vincent Thu, 15 Oct 2009 21:19:26 +0000 http://www.lamolabs.org/blog/?p=2745#comment-507 you should look into the -exec flag in find you should look into the -exec flag in find

]]> Comment on [one-liner]: Bash’s wait Command by NssY http://www.lamolabs.org/blog/1724/one-liner-bash-wait-command/comment-page-1/#comment-392 NssY Wed, 23 Sep 2009 17:52:59 +0000 http://www.lamolabs.org/blog/?p=1724#comment-392 Just Exactly what I needed. thanks Just Exactly what I needed. thanks

]]> Comment on [one-liner]: Filtering ps from ps by Christoph http://www.lamolabs.org/blog/2425/one-liner-filtering-ps-from-ps/comment-page-1/#comment-302 Christoph Fri, 04 Sep 2009 20:41:36 +0000 http://www.lamolabs.org/blog/?p=2425#comment-302 pgrep(1) does the trick and many more and is very nice to use in scripts etc. Because its output is much better to parse. pgrep(1) does the trick and many more and is very nice to use in scripts etc. Because its output is much better to parse.

]]>