It's quite possible I broke it by changing some setting in some area that
I never thought would be related, but recently, I know perl language
indentation used to work. In advance, I ask that some people not take
personal insult. Truly, none is meant personally, or otherwise. I just
devolve into rantations due to a spell of contrariness cast on me by an
evil fairy godmother who didn't get asked to my birth...*sigh*.
It no longer (in my version of vim, version info at end so as not to
interrupt writing) does. Instead of putting closing braces on the same
indent level as the beginning of the line containing it's open brace,
it's placing indented one level to the right, consistent with python.
Obviously, this is wrong for perl as it isn't a format used in any
reference, though recently, I've even been subjected to misformatted javascript, making virtually unreadable (as they also had a strong
resistance against breaking any long lines resulting in unreadable
code in a standard 80-column vim window.
However, I realize this could be considered "personal preference",
as wrong as I may think it is (as much as it is wrong to force
python programmers to program in such a constrained manner).
I realize, that some people feel that being constrained by someone
they choose, 'frees them', but I am not one of them.
I'd like to where to look to fix my copy, as I presume it's not that
way in the official version.
If it is, I'd like to know how to submit a patch to fix it, or to request
that it be fixed. Either way, I'd like to know how to fix my copy.
Even to python users -- it would be beneficial to help me, as it might
lessen my dislike of the language and disdain for its users for continuing
to use a language who's creator is willing to use his personal force as
its creator to veto any addition of braces to the language for those
who would prefer it ( or so I have read).
I'd _like_ to use python, but could not get over the horribly verbose and tedious syntax -- I liked the semantics, sadly, but really couldn't program that way without injuring myself.
I certainly would regard the lack of an easy fix as another reason to
dislike python more, and another 'reason' to entertain creation of 'bython',
a brace enabled version (though, I admit, I'd need alot of reasons to
go through such effort for a language I don't use and that wouldn't be,
initially, very portable). Though I suppose making it backwards compatible
would make it an instant workhorse, while including switches to convert
compile source, in place while running it! :-)
But I have obviously devolved into fantasy -- induced by having to correct
mis-indentation while humbling programming a perl script to maintain my
system.
So please consider helping me in my plight. It's horrible having such dark
thoughts!
:-)
Linda
promised version info:
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Feb 25 2009 17:43:35)
Included patches: 1-108
Compiled by 'http://www.opensuse.org/'
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: "/etc"
f-b for $VIMRUNTIME: "/usr/share/vim/current"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/g
tk-2.0 -I/usr/lib64/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/lib64/glib-2.0/include -
I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -fme
ssage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -
fasynchronous-unwind-tables -g -Wall -pipe -fno-strict-aliasing -fstack-protecto
r-all -I/usr/include64 -D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -DDE
BUGGING -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.10.0/x86
_64-linux-thread-multi/CORE -I/usr/include/python2.6 -pthread -I/usr/include -
D_LARGEFILE64_SOURCE=1 -I/usr/lib64/ruby/1.8/x86_64-linux
Linking: gcc -L/usr/lib64 -L. -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpa
th,/usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/CORE -L/usr/local/lib -L/op
t/gnome/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 -lz -lfontc
onfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lXt -lncurses -lacl -lgpm -Wl,
-E -Wl,-rpath,/usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/CORE -L/usr/local
/lib64 -L/usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/CORE -lperl -L/usr/lib
64/python2.6/config -lpython2.6 -lutil -Xlinker -export-dynamic -L/usr/lib64 -lt
cl8.5 -lieee -Wl,-R -Wl,/usr/lib64 -L/usr/lib64 -lruby -lm
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
