Good morning Predrag. Predrag Punosevac <[email protected]> wrote: |[email protected] wrote: .. |>> Can anybody help me understand what am I seeing. Namely I am trying to |>> send an e-mail using S-nail 14.8.12 (the last one which cleanly compiles |>> on OpenBSD). Actual package is 14.8.9. Ever since I upgraded to 6.1 I
I still have not found the time to back OPT_ALWAYS_UNICODE_LOCALE (true on OpenBSD) with real functionality, iconv(3) will remain a dependency of IMAP in v14.9 (i promised you to try hard to reinstantiate the IMAP code). Sorry. |>> noticed that if I try to use ~v in order to load my e-mail into vi from |>> the base for editing I have normal behaviour if the existing message is |>> empty but if I had started typing I see |>> |>> |>> ~v [LogLevel VERBOSE] |>> ~v [LogLevel DEBUG] ... |> It's coming from ssh. If you type an escape sequence immediately after |> a newline ssh might recognize it. Type return followed by ~? in ssh for |> more information. ... |> ~. will kill a stuck session. ... |> In short, type ~~v for vi when running mail in ssh. | |Works for me! I only run mail in ssh when I am away from my home to |bypass worning messages from my mail providers. I have never seen this |before. I (finally) set the *escape* variable to ! to avoid this (after having been disconnected quite some times after typing ~., and having to reload all the SSH keys): set escape=! and then type !v in compose mode (it is !e or truly now F1 due to !:bind compose bind compose :kf1 !e for me). --steffen
