[email protected]
[Top] [All Lists]

Bug#536741: marked as forwarded (vim-scripts: xmledit added as user fai

Subject: Bug#536741: marked as forwarded vim-scripts: xmledit added as user fails to open xml files
From: Debian Bug Tracking System
Date: Tue, 14 Jul 2009 23:12:02 +0000
Your message dated Tue, 14 Jul 2009 19:09:12 -0400
with message-id <[email protected]>
has caused the   report #536741,
regarding vim-scripts: xmledit added as user fails to open xml files
to be marked as having been forwarded to the upstream software
author(s) Devin Weaver <[email protected]>

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]

536741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536741
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: xmledit's automatic documentation generation
From: James Vega
Date: Tue, 14 Jul 2009 19:09:12 -0400

While I understand the benefit of automatically generating xmledit's
documentation from a developer perspective, would it be possible to
package the generated documentation along with the plugin when
publishing to vim.org?  A simple .zip of both the plugin (without the
out of date detection) and the generated .txt file would be great.

The reason I ask is that the "up-to-date documentation" can cause
problems when shipping the plugin as part of a distribution's package.
The way our users make use of the script is by symlinking the plugin and
doc files from their system-wide location into their ~/.vim.

When the documentation generation gets triggered (because of the
timestamps, not any actual out of date scenario) the script tries to
write out the documentation but is unable to.  This results in a buffer
of the plugin's documentation being present in the user's Vim session
and, depending on their setup, this being the buffer presented to the
user instead of the file they intended on opening.

I've also attached a patch which allows the user to let the
g:loaded_xmledit variable to disable loading of the script.  Again, this
is something that's targetted towards distributions since the script may
be installed system-wide and it would be useful to let users prevent it
from being loaded for their account.

Thanks for considering the feedback.

GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]>

Attachment: disabledby-xmledit.vim
Description: Text document

--- End Message ---
<Prev in Thread] Current Thread [Next in Thread>
  • Bug#536741: marked as forwarded (vim-scripts: xmledit added as user fails to open xml files), Debian Bug Tracking System <=