vimのソースコードを読んでみるテスト

なんとなく気になったのでソースコードを読んでみることにした。emacsでもよいと思ったがlispで書かれてるとか(基本Ｃ)(cバージョンもあるらしいけど)量が半端じゃないとかいう理由でvimにしてみた。

対象ソースはvim-7.0.tar.bz2としよう

mainのトップ

/* vi:set ts=8 sts=4 sw=4: *
　* VIM - Vi IMproved by Bram Moolenaar *
　* Do ":help uganda" in Vim to read copying and usage conditions.
　* Do ":help credits" in Vim to see a list of people who contributed.
　* See README.txt for an overview of the Vim source code. */

READMEを読めとかいてるので読んでみよう

というわけでREADMEを読む

README for the Vim source code

Here are a few hints for finding your way around the source code. This
doesn't make it less complex than it is, but it gets you started.

You might also want to read ":help development".

:help developmentを実行するとソースコードを読むのに役立つtipsが見れるとのこと。ただしまだ見ない(
ぇー

JUMPING AROUND

First of all, use ":make tags" to generate a tags file, so that you can use
the ":tag" command to jump around the source code.

To jump to a function or variable definition, move the cursor on the name and
use the CTRL-] command. Use CTRL-T or CTRL-O to jump back.

To jump to a file, move the cursor on its name and use the "gf" command.

:make tagsでtagを作れとのこと。ただし既にctagsでタグを作ってたりする。:make tagsってのは使ったことはないので今度使ってみるかな... gfコマンドも知らなかった。　ファイルに移動するのに使うとのこと。　ctrl + ] と　ctrl + tは一応知ってた。

... gf使ったら元のファイルに戻れなくなったorz どうすれば戻れるのやら... とりあえずわかるまで使用禁止にする。結局のところソースコードよんで解決しろということなのかな...

つぎにファイルの概略についての説明があるのでみてみる　

fold.cのfoldingってのが気になったりする。foldingって何をするというのだ！　

Most code can be found in a file with an obvious name (incomplete list):
buffer.c manipulating buffers (loaded files)
diff.c diff mode (vimdiff)
eval.c expression evaluation
fileio.c reading and writing files
fold.c folding
getchar.c getting characters and key mapping
mark.c marks
mbyte.c multy-byte character handling
memfile.c storing lines for buffers in a swapfile
memline.c storing lines for buffers in memory
menu.c menus
message.c (error) messages
ops.c handling operators ("d", "y", "p")
option.c options
quickfix.c quickfix commands (":make", ":cn")
regexp.c pattern matching
screen.c updating the windows
search.c pattern searching
spell.c spell checking
syntax.c syntax and other highlighting
tag.c tags
term.c terminal handling, termcap codes
undo.c undo and redo
window.c handling split windows

概略でした。gf問題を解決するためにはtag.cを見ればいいのかな。。

次はグローバル変数についての説明. とりあえずglobals.hにまとまってるらしい

IMPORTANT VARIABLES

The current mode is stored in "State". The values it can have are NORMAL,
INSERT, CMDLINE, and a few others.

The current window is "curwin". The current buffer is "curbuf". These point
to structures with the cursor position in the window, option values, the file
name, etc. These are defined in structs.h.

All the global variables are declared in globals.h.

一気に最後までみてみる。とりあえず重要な処理についての説明は描かれてるっぽい。　とりあえずソースを見るときは、メインからみていくかな

main_loop()を読んであれこれと...そしてnormal_cmd()でコマンド処理とか

THE MAIN LOOP

This is conveniently called main_loop(). It updates a few things and then
calls normal_cmd() to process a command. This returns when the command is
finished.

The basic idea is that Vim waits for the user to type a character and
processes it until another character is needed. Thus there are several places
where Vim waits for a character to be typed. The vgetc() function is used for
this. It also handles mapping.

Updating the screen is mostly postponed until a command or a sequence of
commands has finished. The work is done by update_screen(), which calls
win_update() for every window, which calls win_line() for every line.
See the start of screen.c for more explanations.

COMMAND-LINE MODE

When typing a ":", normal_cmd() will call getcmdline() to obtain a line with
an Ex command. getcmdline() contains a loop that will handle each typed
character. It returns when hitting or or some other character that
ends the command line mode.

EX COMMANDS

Ex commands are handled by the function do_cmdline(). It does the generic
parsing of the ":" command line and calls do_one_cmd() for each separate
command. It also takes care of while loops.

do_one_cmd() parses the range and generic arguments and puts them in the
exarg_t and passes it to the function that handles the command.

The ":" commands are listed in ex_cmds.h. The third entry of each item is the
name of the function that handles the command. The last entry are the flags

NORMAL MODE COMMANDS

The Normal mode commands are handled by the normal_cmd() function. It also
handles the optional count and an extra character for some commands. These
are passed in a cmdarg_t to the function that handles the command.

There is a table nv_cmds in normal.c which lists the first character of every
command. The second entry of each item is the name of the function that
handles the command.

ご存知insertモード。viを使ったことのない人はモードの切り替えに気分を害して、二度とviを使わなくなるとかいう事態が多発されることもあるらしい.. 慣れないとたしかにやっかいかもしれない。

説明としては、iもしくはaでインサートモードにするときにはnormal_cmd()がedit()ファンクションを呼び出すとのこと。予想としては多分メインループでセレクトとか使った処理になってるとおもはれる。

処理についてはnormal_cmd()関数内のedit()の付近を調べればよさそう

INSERT MODE COMMANDS

When doing an "i" or "a" command, normal_cmd() will call the edit() function.
It contains a loop that waits for the next character and handles it. It
returns when leaving Insert mode.

OPTIONS

There is a list with all option names in option.c, called options[].

THE GUI

Most of the GUI code is implemented like it was a clever terminal. Typing a
character, moving a scrollbar, clicking the mouse, etc. are all translated
into events which are written in the input buffer. These are read by the
main code, just like reading from a terminal. The code for this is scattered
through gui.c. For example: gui_send_mouse_event() for a mouse click and
gui_menu_cb() for a menu action. Key hits are handled by the system-specific
GUI code, which calls add_to_input_buf() to send the key code.

Updating the GUI window is done by writing codes in the output buffer, just
like writing to a terminal. When the buffer gets full or is flushed,
gui_write() will parse the codes and draw the appropriate items. Finally the
system-specific GUI code will be called to do the work.

GUIでバッギング方法についての説明　gdbであれこれととかって書いてるっぽい... gdbは面白そうではあるかな,ただしあまり使ったことはないのでいまいち使い方がわからなかったりする

DEBUGGING THE GUI

Remember to prevent that gvim forks and the debugger thinks Vim has exited,
add the "-f" argument. In gdb: "run -f -g".

When stepping through display updating code, the focus event is triggerred
when going from the debugger to Vim and back. To avoid this, recompile with
some code in gui_focus_change() disabled.

とまあこんなところでREADMEはおしまいにしてみようっと　続きはあったら書いてみるかな(ぇー)