Re: [vile] How to use map! to enter 'special' UTF8 characters?

On 17 March 2017 at 19:55, Chris Green wrote: >> Try mapping it to ^Vu2714. That worked for me. >> > That's *exactly* what I have done, it shows correctly (as above) in > .vilerc but when I hit F4 in insert mode while editing I see the > string â\u009C\0094. I can insert a ✔ by

Re: [vile] auto-filtered text?

On 1 July 2017 at 01:30, wrote: > Let's say I input 10 lines of text, and then I need to filter that text > through a specific command. So I go to the top line and do this > > :,+9!command > > Is there a way that I can save a step -- some kind of special "i" or "o"

Re: [vile] Possible locations for vile.keywords

Tracing the execution of opening a file in cmode via "vile @filters.rc foo.c" shows that the following files are attempted in order: ./.vile.keywords ~/.vile.keywords ~/.vile/vile.keywords /usr/share/vile/vile.keywords ./.c.keywords ~/.c.keywords ~/.vile/c.keywords

Re: iclower

On Wed, Dec 18, 2019 at 05:55:25PM -0500, Thomas Dickey wrote: >On Wed, Dec 18, 2019 at 11:00:44AM -0800, Marc Simpson wrote: >> One nice nvi feature that I miss in vile is the `iclower' setting: >> >> iclower [off] >> The iclower edit option makes all Regular Expressions >>

Re: set bcolor to grey85?

On Sun, 15 Mar 2020 at 14:55, Steven Lembark wrote: > Catch: ";set bcolor grey85" (or "gray85") gives me nada, it won't > take the argument. Similarly #f0f0f0 doesn't give me anything. For vile in the terminal, colours are set with escape codes. Historically most terminals supported a limited

Re: Fonts for xvile in linux - where to find some nice ones?

There is quite a bit of difference in how traditional X11 bitmap fonts and freetype fonts are selected and rendered (https://utcc.utoronto.ca/~cks/space/blog/unix/XFontTypes gives a reasonable summation) but the main thing is that from the API level they are not interchangeable. XTerm has

Re: The vileget calling code in .vilerc

On Mon, 8 Feb 2021 at 02:45, Chris Green wrote: > In my .vilerc that I use on several systems I have the following > towards the end:- [snip] > I only looked at this just recently because I got an unexpected > vileget running on a little Beaglebone SBC where it took a noticeable > amount of time

Re: Further to the perl/vileget/vileserv saga

On Mon, Feb 08, 2021 at 01:46:11PM -0600, J. Chris Coppick wrote: >Do not think the "use Vileserv" replaces those other lines. It does ring a >bell. I'd have to dig up the docs and code to check what was required for >what. It does, you can pretty easily test it: $ echo 'perl "use Vileserv"'

Re: Further to the perl/vileget/vileserv saga

On Mon, Feb 08, 2021 at 01:29:13PM +, Chris Green wrote: >I *think* I'm beginning to understand all this, I suspect there's some >bits of very old history of mine (and of vile) in all this. > >Firstly I don't quite know from where I got the following code (which is in >my .vilerc):- > >

Re: Further to the perl/vileget/vileserv saga

On Tue, 9 Feb 2021 at 10:09, Brendan O'Dea wrote: > The difference in `.pl' vs `.pm' is that Perl will use the latter as a default > when `require' is given a bare work (as opposed to a quoted string). [...] That would be "bare *word*", damnit. --bod

Re: scrolling/paging question

On Tue, Mar 02, 2021 at 07:00:04PM -0500, Thomas Dickey wrote: >On Tue, Mar 02, 2021 at 04:28:33PM +, Wayne wrote: >> I can use move-window-down/move-window-up with a count but it still >> seems in some cases, which I don't quite fully understand yet, the >> cursor is positioned back at the

[PATCH 2/2] Perl6 is now known as raku.

Update modes and filters to use "raku" over "perl6". Extensions as per: https://github.com/Raku/problem-solving/blob/master/solutions/language/Path-to-Raku.md#extensions are matched, as are the previous ".p6", ".pl6", etc. Note renames: mv filters/pl6filt.c filters/raku-filt.c mv

[PATCH 1/2] Apply some changes from pl-filt.c to pl6filt.c

It appears that a leak of `marker' was fixed in the former which didn't make it to the latter. --- filters/pl6filt.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/filters/pl6filt.c b/filters/pl6filt.c index 7148eb3..7cd5580 100644 --- a/filters/pl6filt.c +++

Re: How to access vile variables in : command?

Not sure about variables in general, but you should be able to use % for the current filename here (and # for the alternate filename). On Thu, 9 Nov 2023 at 02:52, Chris Green wrote: > > I'm sure this should be obvious but at the moment it's not obvious to > me! :-) > > I want to do something

[PATCH] Fix build failure with Perl 5.36

Fix a build failure for Perl 5.36 caused by a namespace conflict of the symbol `regexp' (http://bugs.debian.org/1014289). diff --git a/perl.xs b/perl.xs index 86c04e3..ee658d2 100644 --- a/perl.xs +++ b/perl.xs @@ -118,20 +118,20 @@ /* for vile */ #define MARK vile_MARK +#define regexp

[PATCH] Remove obsolete gcc pragma

Remove a pragma from perl.xs which gcc no longer recognises. This pragma was meant to reduce noise, but now adds more. Compiling with gcc 11 produces: ../../perl.xs:24:32: warning: unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas] 24 | #pragma GCC diagnostic ignored

Re: UTF8 has stopped working in vile after OS upgrade

Testing the vile 9.8v-2 package on my Debian machine I get some decidedly odd behaviour: The following sequence: l- e' c, is rendered in vile as: \?A3\?E9\?E7 outside of vile, in the same terminal that appears fine: £éç which would suggest that vile doesn't handle UTF-8 at all,

[PATCH] fix uxvile font, and update xvile to match

The font specification in /etc/X11/app-defaults/UXVile is being overridden by the one in XVile. Additionally update the xvile font to use the Latin-1 equivalent (9x18 instead of 8x13). Pushed to salsa.debian.org/debian/vile as 52d1fe2a and 18f244bc respectively. diff --git a/macros/UXVile.ad

Re: UTF8 has stopped working in vile after OS upgrade

I've pushed a rollback of that change to Debian as 0d1f060a. Relevant patch attached. --bod On Sat, 30 Jul 2022 at 00:00, Chris Green wrote: > On Fri, Jul 29, 2022 at 04:27:05AM -0400, Thomas Dickey wrote: > > On Fri, Jul 29, 2022 at 03:40:12PM +1000, Brendan O'Dea wrote: > &g

Re: Vileserv on macOS issue

On Wed, 21 Dec 2022 at 09:33, Robert Sturrock wrote: > read(0x4, "/Users/rns/tmp/fortune-cookie.txt\n\n\0", 0x2000) = 35 > 0 > write(0x1, "/Users/rns/tmp/fortune-cookie.txt\n\n\n\0", 0x24)= 36 > 0 That looks pretty much what I would expect vileserv to do: it reads from

Re: Build errors at link time - what am I missing?

On Thu, 1 Dec 2022 at 07:26, Chris Green wrote: > > However, later on in configure I get:- > > configure: WARNING: Cannot find -ltermlib, -lcurses, or -ltermcap > > and then at link time there are loads of undefined references to > > tputs, tgoto, and a lot of other tx symbols. > > > > So

Re: Can one build a static vile easily?

On Wed, 12 Jul 2023 at 19:44, Chris Green wrote: > Is there any way to build a 'static' version of vile fairly easily? This is a pretty easy one to answer: easily? no. Part of this is because the current configure is not set up for it, so you would need to muck about with the generated

Re: Weird problem in xvile - I can't enter a '>' character

On Tue, 12 Mar 2024 at 02:28, Chris Green wrote: > > If I comment out the line:- > > keysym period = period rightcaret U25B6 NoSymbol > > then the > key works again in xvile. However I really don't see why > the above line breaks xvile, no other programs (or none I can find > anyway) are

Re: macro question

On Fri, 5 Apr 2024 at 16:09, david sowerby wrote: > Hi, in Vim/Neovim I can save a copy of the file when I exit. The copy is > renamed file-$(date +%s).bak. This gives me a file with an increasing number > plus .bak. It looks like "date+%s" and "" do the same thing. Is this > possible in