Re: [gNewSense-users] KFV Mode 0.5: partial uploads, more feedback and checking

[Bake Timmons]

> After that I give
> http://wiki.gnewsense.org/Kernel/Ubuntu-hardy-linux-2-6-24-12-22--fs--hostfs
> as URL but I just get beep and message "[No match]" and URL is not accepted.

I cannot reproduce this error on my installations, but I have not tried
that exact version, 22.1.1.  I will try it if I get that the chance and
do not hear from you.

Some things to try:

1. Before you try to give any URL, what happens when you just press TAB
alone?  You should be presented with a huge list of valid URLs.

2. Try running this at a shell prompt:

head ~/.gns-kfv/kfv-sections

Its output should start off like:

http://wiki.gnewsense.org/Kernel/Ubuntu-hardy-linux-2-6-24-12-22
http://wiki.gnewsense.org/Kernel/Ubuntu-hardy-linux-2-6-24-12-22--Documentation

If the file does not exist, read #5 below about the kfv-req-section-url
function, but instead of debugging that function, debug the
kfv-init-sections function.

3. What happens at the shell prompt when you try:

cd /usr/src/ && find -L linux-2.6.24_12.22 -type d | \
sed -e 's/[._]/-/g' -e 's/\//--/g' \
-e 's/^/http:\/\/wiki.gnewsense.org\/Kernel\/Ubuntu-hardy-/g' | head

4. In Emacs after you get your error message, press C-h v or run the
command describe-variable.  Then type kfv-sections .  Emacs should show
a big list of valid sections.

5. Finally, this last step is a little involved, but it is also very
enlightening.  I assume that you are in Emacs and have loaded kfv.el.
Next, open the same kfv.el file into Emacs so that you can read the
code.  Search for the function "kfv-req-section-url" and once you have
found it.  Put the cursor anywhere inside this function definition and
press C-u C-M-x or C-u eval-defun to enable debugging on that function.
Then run kfv-start and Emacs will step through the kfv-req-section-url
function so that you might spot some inconsistency.  Every time Emacs
advances the cursor during this process, the bottom of the Emacs window
will be updated with any new value that should be shown of the
expression that immediately precedes the cursor position.  Press the
space bar to advance the debugger.

   The last step seems like a pain, but it does not take long at all.
However, I hope the error pops up before that point. :)

Good luck Markus and please let me know what you find out.