Vim will remember the cursor position as long as ~/.viminfo is writable
by your user. The ' setting in your 'viminfo' option is limiting Vim to
only remember marks for the last 10 files, though.
--
vim hangs loading 100%
https://bugs.launchpad.net/bugs/673680
You received this bug notification
Your stated bug #1 is not a bug. The vi name is managed by the
alternatives system. Packages with more functionality have a higher
priority in the alternatives system. As such, installing the vim
package installs a higher priority alternative for the vi name. If you
want to use the vi binary
If you could confirm whether this happens when starting Vim in the
following ways, that should help narrow down whether this is a bug in
Vim or some script that is loaded.
1) vim -u NONE -N testfile
2) vim -u NORC -N testfile
3) vim --noplugin -N testfile
4) vim -u /etc/vim/vimrc -N testfile
** Bug watch added: Debian Bug tracker #561080
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561080
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561080
Importance: Unknown
Status: Unknown
--
Bug with vim's syntax highlighting in perl
This is a general user support question, not a bug. I would suggest
asking your question in the Absolute Beginner Talk section of
http://www.ubuntuforums.org/
** Package changed: vim (Ubuntu) = ubuntu
** Changed in: ubuntu
Status: New = Invalid
--
unable to apply AMR code patch
This bug was fixed in version 2:7.2.284-1 of the Debian package, which
was merged to Ubuntu in 2:7.2.330-1ubuntu1. This is available in Lucid
(10.04).
** Changed in: vim (Ubuntu)
Status: Confirmed = Fix Released
--
Changing font size in a maximized window doesn't recalculate usable area
** Bug watch added: Debian Bug tracker #568378
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568378
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568378
Importance: Unknown
Status: Unknown
--
vim crontab syntax highlighting should treat
The default sh syntax highlighting is based on the Bourne shell, which
doesn't understand $(()). If you're going to be writing POSIX sh
scripts, then you want to add let g:is_posix=1 in your ~/.vimrc as is
described at :help ft-sh-syntax.
** Changed in: vim (Ubuntu)
Status: New = Invalid
This is fixed by upstream patch 7.2.097. The Vim packages in Karmic and
later include this patch.
** Changed in: vim (Ubuntu)
Status: New = Fix Released
--
External command are broken in gvim started from menu
https://bugs.launchpad.net/bugs/322023
You received this bug notification
Upstream patch 7.2.413 adds largefile support. Some of the Vim packages
(those which support scripting via Perl) already have this transitively
via libperl's CFLAGS. I'll be uploading a new Vim package to Debian
with patch 7.2.413 soon.
--
can't open files larger than 2gb
When you start Vim normally, the system-wide vimrc is sourced, which
sources $VIMRUNTIME/debian.vim, which calls set nocompatible. When
the 'nocompatible' option is set, that tells Vim to set the 'wildchar'
option to Tab instead of the default of C-e. If you want the
same behavior when you use
*** This bug is a duplicate of bug 269904 ***
https://bugs.launchpad.net/bugs/269904
** This bug has been marked a duplicate of bug 269904
Screen refresh problems with nvidia on intrepid
--
VIM don't refresh the content correctly
https://bugs.launchpad.net/bugs/295593
You received this
The -f option is required to allow programs to invoke gvim and wait for
the user to exit gvim, as you can see from
http://bugs.debian.org/329292. Without the -f, gvim immediately
forks, thus returning control back to whatever process spawned it.
There are many other ways to start programs other
*** This bug is a duplicate of bug 365860 ***
https://bugs.launchpad.net/bugs/365860
** This bug has been marked a duplicate of bug 365860
File chooser in gvim replaced by old-style bookmarkless file selector
--
gvim uses a feature-limited file open dialog in gnome
Anatoly, Vim runs in 'compatible' mode by default. This isn't specific
to vim-tiny. The way that you change this is by creating a ~/.vimrc
file. The mere presence of this file tells Vim that you know you're
using something other than vi and it changes the option to
'incompatible', allowing you
As discussed, this was an error in the watch file. The regex is used in
an anchored match against the entire href for HTTP sites, so it needs to
be formed to account for this.
** Changed in: devscripts (Ubuntu)
Status: Confirmed = Invalid
--
uscan: option --user-agent doesn't work
This bug is fixed in the latest development version of Ubuntu - Lucid
Lynx.
** Changed in: devscripts (Ubuntu)
Status: New = Fix Released
--
debcommit fails when -r and -c are used together.
https://bugs.launchpad.net/bugs/368563
You received this bug notification because you are a
** Bug watch added: Debian Bug tracker #538280
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538280
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538280
Importance: Unknown
Status: Unknown
--
cmake.vim syntax is out of date
The order of directories in 'runtimepath' is intentional and follows the
way that Vim upstream orders the directories. The only difference is
that the /var/lib/vim/addons{,/after} directories are inserted.
Using the after/ directories isn't a workaround. The entire reason they
exist is so the
Closing the bug as it is user error. vim-tiny defaults to running with
the 'compatible' option set. Using :set nocompatible or :set
esckeys will restore the expected behavior.
** Changed in: vim (Ubuntu)
Status: New = Invalid
--
Using arrow keys in vim-tiny while in Insert mode
In general, debchange doesn't update the original changelog unless your
explicitly save the temporary file that you are presented with for
editing. Unless I'm misunderstanding the description, this seems like
expected behavior.
--
DEBEMAIL confusion when using dch -e and vim
debian/changelog files are required to be utf8-encoded. The line
causing the error contains a latin1 o-umlaut and as such the error seems
appropriate.
--
does not map to Unicode
https://bugs.launchpad.net/bugs/191845
You received this bug notification because you are a member of Ubuntu
Bugs,
This is a transient error that occurs during dinstall runs. The
database is temporarily removed and then rebuilt. There is nothing the
rmadison script can do about this as the error is occurring on Debian's
server, not in devscripts' rmadison script.
--
rmadison crashed with OperationalError;
** Bug watch added: Debian Bug tracker #542484
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542484
** Also affects: devscripts (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542484
Importance: Unknown
Status: Unknown
--
Unicode problem in dch
Your second point, about Vim hanging trying to create temporary
directories, is fixed as of patch 7.2.294 and will be available once
2:7.2.330-1 is synced from Debian.
--
vim uses ./$TMPDIR (literally, not expanded) as temporary directory
https://bugs.launchpad.net/bugs/184719
You received this
** Bug watch added: Debian Bug tracker #466088
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466088
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466088
Importance: Unknown
Status: Unknown
--
Changing font size in a maximized window
Right, because :let is a command that requires +eval which vim-tiny
doesn't have. Vim will always recognize if 1, so you can put anything
that requires +eval inside an if 1 block and it will be properly
guarded.
I'm curious why you're sourcing $VIMRUNTIME/syntax/syntax.vim instead of
just
This problem is happening because the users only have vim-tiny installed
and manually installed vim-runtime instead of installing a more
featureful vim package (vim, vim-nox, vim-gtk, vim-gnome) which will
automatically pull in vim-runtime.
Ideally users won't run into this as much once they
Marking as invalid as per reporter's comment.
** Changed in: vim (Ubuntu)
Status: New = Invalid
--
vim cannot find installed spell files
https://bugs.launchpad.net/bugs/367841
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Jonas, simply doing apt-get install vim when vim-gnome is installed
isn't going to change the binary that is used for the vim alternative.
Steffen was still using vim-gnome until he changed the alternative to
not use it. Therefore, this bug is still invalid as explained by Colin.
** Changed in:
** Bug watch added: Debian Bug tracker #379612
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379612
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379612
Importance: Unknown
Status: Unknown
--
vim-gnome window does not resize correctly when
** Bug watch added: Debian Bug tracker #532027
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532027
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532027
Importance: Unknown
Status: Unknown
--
[karmic] vim-7.2.148-2ubuntu2 - broken regexp
This behavior is intentional. You should use :e to open files. :o
only exists to appease POSIX compliance as a vi-clone. If you are
getting the ^I character when tab-completing :e or :w, then you
have the 'compatible' option set or the 'wildchar' option is not set to
Tab.
** Changed in: vim
Enabling syntax highlighting runs afoul of the same problem that caused
me to stop enabling filetype plugins by default in the Debian package.
It causes Vim to source various script from its runtimepath. This
cannot be undone by the user and therefore makes the user unable to make
certain
You could also write your vimrc so it is robust to different feature
levels built into Vim. vim-runtime is a data package which may be
interesting to people independent of using it with Vim. There's no
reason that it should have a hard dependency on one of the more
featureful vim binary
You're running your own Supybot setup. This error is from the recent
upstream release 0.83.4, not the packaged version of Supybot.
** Changed in: supybot (Ubuntu)
Status: New = Invalid
--
supybot suffers Python Exception when help on Factoids is requested
Hmm, that doesn't actually seem to be the case. I missed the reported by
date initially. This is a different bug that affected Factoids which is
fixed in the recent 0.83.4 release. :)
** Changed in: supybot (Ubuntu)
Status: Invalid = New
--
supybot suffers Python Exception when help on
This is now fixed upstream and will be included in 0.83.4. Thanks for
the bug report.
--
supybot parses regular expressions crudely and incorrectly for String plugin's
re command
https://bugs.launchpad.net/bugs/235500
You received this bug notification because you are a member of Ubuntu
Bugs,
** Bug watch added: Debian Bug tracker #471331
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471331
** Also affects: gtkam (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471331
Importance: Unknown
Status: Unknown
--
gtkam crashes if you change folders while it
** Bug watch added: SourceForge.net Tracker #2146042
http://sourceforge.net/support/tracker.php?aid=2146042
** Also affects: gtkam via
http://sourceforge.net/support/tracker.php?aid=2146042
Importance: Unknown
Status: Unknown
--
gtkam crashes if you change folders while it is
If you don't want Vim saving the swapfile in the same directory as the
file being edited, then configure it not to. For example, I have the
~/.vim/tmp as the first directory Vim tries to store swapfiles in by
adding the following line to my ~/.vimrc:
set directory^=~/.vim/tmp Prepend
The user is referring to documentation on the upstream website. This is
not a bug in the fish package.
** Changed in: fish (Ubuntu)
Status: Confirmed = Invalid
** Changed in: fish (Ubuntu)
Assignee: James Vega (jamessan) = (unassigned)
--
Cannot set fish as default shell
https
** Bug watch added: Debian Bug tracker #466789
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466789
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466789
Importance: Unknown
Status: Unknown
--
mrxvt breaks vim
*** This bug is a duplicate of bug 212494 ***
https://bugs.launchpad.net/bugs/212494
** This bug has been marked a duplicate of bug 212494
mrxvt breaks vim
--
vim starts in change mode when opening file
https://bugs.launchpad.net/bugs/210032
You received this bug notification because you
*** This bug is a duplicate of bug 219546 ***
https://bugs.launchpad.net/bugs/219546
** This bug has been marked a duplicate of bug 219546
vim crashed using rails.vim on Hardy
--
Vim crash when trying to expand a path
https://bugs.launchpad.net/bugs/215374
You received this bug
** Bug watch added: Debian Bug tracker #400771
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400771
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400771
Importance: Unknown
Status: Unknown
--
Vim locks up while editing a specific file
** Bug watch added: Debian Bug tracker #421312
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421312
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421312
Importance: Unknown
Status: Unknown
--
Apache config files in
Public bug reported:
Binary package hint: vim
The Ubuntu patch to the vim packaging contains a few diversions from Debian
that are unneeded.
1) set textwidth=0 in debian/runtime/debian.vim.in since that is Vim's default
2) set nobackup in debian/runtime/debian.vim.in since that is Vim's default
There are various modes that Vim uses for backups. By default (set
nobackup, set writebackup), a backup file is created just before
saving and if the save is successful it is deleted. You can see a full
explanation of the different backup behavior at :help backup-table.
You may also be
If you're still seeing this problem with :set backupcopy=yes, then I'd
definitely push the bug to gvfs/fuse. Even if that still exhibits the
behavior, I'd be inclined to think this is a bug in gvfs/fuse. Yes,
Vim's behavior is not the same as other editors but that doesn't make it
wrong. A
The packaging problem which caused the help to be inaccessible was fixed
in Gutsy.
** Bug watch added: Debian Bug tracker #464393
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464393
** Also affects: vim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464393
Importance:
This is fixed by upstream's 7.1.147 patch.
--
vim crashed using rails.vim on Hardy
https://bugs.launchpad.net/bugs/219546
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
If you chsh to accept a shell you're installing from source, you need to
modify /etc/shells to accept the path to that shell as a valid shell.
It is not the job of the fish package to support independent installs
from source.
** Changed in: fish (Ubuntu)
Assignee: (unassigned) = James Vega
The Ubuntu package does not install the shell into /usr/local/bin so
either you (or someone else) installed fish from source to
/usr/local/bin or your are giving the wrong path to chsh. If it is the
latter, then you should be telling chsh to use /usr/bin/fish.
--
Cannot set fish as default
.
** Changed in: fish (Ubuntu)
Assignee: (unassigned) = James Vega (jamessan)
Status: Incomplete = Invalid
--
output of time badly formatted in fish
https://bugs.launchpad.net/bugs/71677
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
55 matches
Mail list logo
