Control: tags -1 + unreproducible
Hi Toni,
On Thu, Feb 19, 2026 at 07:35:01PM +0000, Toni Mueller wrote:
>
> On Thu, Feb 19, 2026 at 03:24:47PM -0300, Carlos Henrique Lima Melara wrote:
> > Ok, I did the reply (hit "r"), edit something, saved (I use vim as the
> > editor) and
>
> I use neovim as the editor.
My bad, I said vim, but it's actually neovim, though my nvim
configuration is pretty small and barebones (will attach here, maybe you
can try it or set EDITOR to nano and see if it still truncates).
> > postponed it. Then I pressed "m" and answered yes to the prompts to
> > recall the postponed message and I did get the correct
> >
> > Subject: Re: Bug#1128408: Subject mangled for postponed messages
>
> Sounds good!
Just had the time to test in trixie today and the procedure here doesn't
truncate the Subject header.
> > I also tried to quit (hit "q") and then open neomutt again to recall the
> > postponed message and it shows the correct subject. It's saved in my
> > Draft folder with the correct subject too.
>
> Hmmm, weird. I tried with neovim and with vim.nox, the latter without
> much configuration, and get the same result both times.
>
> I also just saw that the subject gets mangled as soon as I leave the
> editor and get back to the menu where I can edit the headers, send the
> message, or eg. postpone it.
Hum, could it be the editor doing stuff behind neomutt's back?
> > If you have the time, you can try to neomutt -d 2 (or up to 5 for
>
> I've done that, but there is a whole lot of private information in
> there that I don't want to send out.
Oops, sorry, forget to say there would be a lot of personal/confidential
info in there.
> > maximum debug output) to enable debugging and have it written to
> > ~/.neomuttdebug0. This will be specially useful if I can't reproduce the
> > problem.
>
> Maybe you can tell me what to look out for?
Maybe you can grep by the message subject, id or the trucated subject
and send only that part.
> > > I have created a sanitized version of the config. Not using it is not an
> > > option, as I need to specify where my mailboxen are, how to login etc.
> >
> > Are you saying that you have cleaned up your config to attach (and
> > forgot to attach to the mail) or that, yes, you do have a custom config
> > and that's all?
>
> Ugh. I think I forgot to attach the sanitized config.
Hehehehehe it happens. I'm looking at your configs but nothing pops up
to my eyes as being the root cause for this weird behaviour.
So TLDR is I can't reproduce it on sid or trixie :-( Though I have
uploaded yesterday testing's version to backports, it's waiting in the
NEW queue and should be available soon.
Cheers,
Charles
" Comments in Vimscript start with a `"`.
" Autoindent
set autoindent
" If you open this file in Vim, it'll be syntax highlighted for you.
" Vim is based on Vi. Setting `nocompatible` switches from the default
" Vi-compatibility mode and enables useful Vim functionality. This
" configuration option turns out not to be necessary for the file named
" '~/.vimrc', because Vim automatically enters nocompatible mode if that file
" is present. But we're including it here just in case this config file is
" loaded some other way (e.g. saved as `foo`, and then Vim started with
" `vim -u foo`).
set nocompatible
" Turn on syntax highlighting.
syntax on
" Disable the default Vim startup message.
set shortmess+=I
" Show line numbers.
set number
" This enables relative line numbering mode. With both number and
" relativenumber enabled, the current line shows the true line number, while
" all other lines (above and below) are numbered relative to the current line.
" This is useful because you can tell, at a glance, what count is needed to
" jump up or down to a particular line, by {count}k to go up or {count}j to go
" down.
set relativenumber
" Always show the status line at the bottom, even if you only have one window
open.
set laststatus=2
" The backspace key has slightly unintuitive behavior by default. For example,
" by default, you can't backspace before the insertion point set with 'i'.
" This configuration makes backspace behave more reasonably, in that you can
" backspace over anything.
set backspace=indent,eol,start
" By default, Vim doesn't let you hide a buffer (i.e. have a buffer that isn't
" shown in any window) that has unsaved changes. This is to prevent you from "
" forgetting about unsaved changes and then quitting e.g. via `:qa!`. We find
" hidden buffers helpful enough to disable this protection. See `:help hidden`
" for more information on this.
set hidden
" This setting makes search case-insensitive when all characters in the string
" being searched are lowercase. However, the search becomes case-sensitive if
" it contains any capital letters. This makes searching more convenient.
set ignorecase
set smartcase
" Enable searching as you type, rather than waiting till you press enter.
set incsearch
" Unbind some useless/annoying default key bindings.
nmap Q <Nop> " 'Q' in normal mode enters Ex mode. You almost never want this.
" Disable audible bell because it's annoying.
set noerrorbells visualbell t_vb=
" Enable mouse support. You should avoid relying on this too much, but it can
" sometimes be convenient.
set mouse+=a
" Try to prevent bad habits like using the arrow keys for movement. This is
" not the only possible bad habit. For example, holding down the h/j/k/l keys
" for movement, rather than using more efficient movement commands, is also a
" bad habit. The former is enforceable through a .vimrc, while we don't know
" how to prevent the latter.
" Do this in normal mode...
nnoremap <Left> :echoe "Use h"<CR>
nnoremap <Right> :echoe "Use l"<CR>
nnoremap <Up> :echoe "Use k"<CR>
nnoremap <Down> :echoe "Use j"<CR>
" ...and in insert mode
inoremap <Left> <ESC>:echoe "Use h"<CR>
inoremap <Right> <ESC>:echoe "Use l"<CR>
inoremap <Up> <ESC>:echoe "Use k"<CR>
inoremap <Down> <ESC>:echoe "Use j"<CR>
" Show hidden chars
set listchars=eol:¬,tab:>·,trail:·,extends:>,precedes:<
set list
set expandtab
" Search down into subfolders
set path+=**
" Display all matching files
set wildmenu
" Create the tags file in the cwd
command! MakeTags !ctags -R .
