Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

David Wright wrote: ... > One of the most pleasurable times in my career was when our Research > Computing Advisor thrust a copy of the Green Book into my hands. > http://www.math.bas.bg/bantchev/place/snobol/gpp-2ed.pdf > After years of Fortran, this was my first experience of a designed > compute

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On Sun 19 Jul 2020 at 11:35:31 (+), Ajith R wrote: > > > First, there is a somewhat specific question about unspecified > > substitutions. For all I know about these substitutions, you might > > actually need XSLT to do them properly. > > The substitution that I had in mind requires referring

Re: Using .XCompose

On Mon 20 Jul 2020 at 13:20:19 (+), Ajith R wrote: [> Someone else wrote:] > > Try again, for firefox-esr (and with a ~/.XCompose file that is not > > befouled with nonbreaking spaces). > >  > > But make one change to the procedure. When you launch firefox-esr, do > > so like this: > >  > > $ e

Re: Using .XCompose

On Mon, Jul 20, 2020 at 01:20:19PM +, Ajith R wrote: > I tried to start firefox using the command above. Fire fox gave the error  > (firefox-esr:1554): Gtk-WARNING **: 15:05:11:541 : GTK+ suports to output one > char only: "a long substitution": : "a long substitution" > What next steps do y

Re: Using .XCompose

Hi, > Try again, for firefox-esr (and with a ~/.XCompose file that is not > befouled with nonbreaking spaces). >  > But make one change to the procedure. When you launch firefox-esr, do > so like this: >  > $ env GTK_IM_MODULE=xim firefox-esr >  > Let us know how that goes. I made a fresh instal

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On 2020-07-19 09:32, to...@tuxteam.de wrote: On Sat, Jul 18, 2020 at 10:20:00PM +0100, mick crane wrote: [...] >Of course, hacking oneliners (with some measure) can be fun and >help in the language's mastery [...] they do work tho' and can be astonishingly quick ? Quick in typing? In thi

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

One last point I missed in my previous post -- big files. Many Perl functions and/or libraries expect to do everything in RAM. This becomes a problem when I want to compress, encrypt, save, and checksum 14 GiB system drive images using a live drive and a Perl program in computers without larg

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

Hello Ajith, Tom Browder suggests taking a look at Raku (née Perl6), and I concur. While I don't know Malayalam at all, I can write the regex code below with ease: > #all code below using the Raku REPL: > say '0123456789'.chars; 10 > say $/ if '0123456789' ~~ / \d+ /; ｢0123456789｣ > #now with B

Re: how u mine 4 utf8 [was Re: Using .XCompose]

Hi, Thanks for the suggestion. No, I don't do unicode scripting regularly.  My requirment was a one time requirment to analyse frequency of Malayalam text to design a keyboard layout. But sure, I will keep your suggestion in mind if such requirment comes up frequently. ajith

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

Hi, > First, there is a somewhat specific question about unspecified > substitutions. For all I know about these substitutions, you might > actually need XSLT to do them properly. The substitution that I had in mind requires referring to characters based on their unicode properties like script,

Re: Fw: how u mine 4 utf8 [was Re: Using .XCompose]

On Sun, Jul 19, 2020 at 05:47 Ajith R wrote: > Hi, > > Mapping unicode to UTF-8 Ajith, if you deal with unicode scripting you really should look into Raku. One of its many strengths is it is unicode (utf8) by default and has many aids built-in for unicode grapheme handling including regexes and

Re: how u mine 4 utf8 [was Re: Using .XCompose]

Hi, > These two too: > RFC 3629 - UTF-8, a transformation format of ISO 10646 (14 pages) > https://tools.ietf.org/html/rfc3629 >  > The Unicode Consortium. The Unicode Standard. > http://www.unicode.org/versions/latest/ >  > In present version 13.0.0 of the latter, >   * A brief feature summary

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

Hi, > I seem to recall that he puts Perl at the top of the  > heap, and notes that Perl compatible regular expressions (PCRE) are > available via libraries in other programming languages. Thanks for confirming that I didn't make a wrong choice. Programs that claim to use PCRE don't support ever

Fw: how u mine 4 utf8 [was Re: Using .XCompose]

Hi, > Mapping unicode to UTF-8 Thanks for the explanation and the references. I am starting to understand the idea. Hopefully, after going through the references everyone has given, I will understand it clearly. > Example 2. Don't know the name of this one. I tell myself it > represents a

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On Sat, Jul 18, 2020 at 10:20:00PM +0100, mick crane wrote: [...] > >Of course, hacking oneliners (with some measure) can be fun and > >help in the language's mastery [...] > they do work tho' and can be astonishingly quick ? Quick in typing? In thinking? In compile time? In run time? There's

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On 2020-07-18 02:59, davidson wrote: On Thu, 16 Jul 2020 Ajith R wrote: On Thursday 16 July 2020 4:54:09 AM IST davidson wrote: [snip]    $ sed 'y/\xc2\xa0/%/' somefile An off topic question: of sed, awk and perl, if I am to chose one to learn, which would you suggest. I wanted to do some s

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On 2020-07-18 22:08, to...@tuxteam.de wrote: On Sat, Jul 18, 2020 at 09:31:29PM +0100, mick crane wrote: [...] You see perl one liners and sed mentioned loads more than awk on the interweb. Don't know why that is. ISTR Perl had a bout of onelineritis back in its youth. This tends to be somew

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On Sat, Jul 18, 2020 at 09:31:29PM +0100, mick crane wrote: [...] > You see perl one liners and sed mentioned loads more than awk on the > interweb. > Don't know why that is. ISTR Perl had a bout of onelineritis back in its youth. This tends to be somewhat detrimental to a language, because peop

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On 2020-07-18 14:56, to...@tuxteam.de wrote: On Sat, Jul 18, 2020 at 09:59:46AM +, davidson wrote: On Thu, 16 Jul 2020 Ajith R wrote: >On Thursday 16 July 2020 4:54:09 AM IST davidson wrote: [snip] >>   $ sed 'y/\xc2\xa0/%/' somefile > >An off topic question: of sed, awk and perl, if I am t

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On Sat, Jul 18, 2020 at 3:40 AM Zenaan Harkness wrote: > # simple version: > perl -p -i[.bak] -e 's/xxx/yyy/[g];' $(readlink somefile) # readlink is > necessary do not clobber symlinks Speaking as not-an-expert on Raku (née Perl6), you'd write the above something like: user@mbook:~$ # One-liner

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

Andrei POPESCU wrote: > On Sb, 18 iul 20, 09:59:46, davidson wrote: >>=20 >> But first of all, I should reiterate that I lack expertise. >>=20 >> I lack expertise. >>=20 >> Second, I have no useful knowledge about real programming languages >> (such as perl) to declare. > > Same disclaimers apply t

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On Sat, Jul 18, 2020 at 09:59:46AM +, davidson wrote: > On Thu, 16 Jul 2020 Ajith R wrote: > >On Thursday 16 July 2020 4:54:09 AM IST davidson wrote: > > [snip] > >>   $ sed 'y/\xc2\xa0/%/' somefile > > > >An off topic question: of sed, awk and perl, if I am to chose one to > >learn, which wou

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On Sb, 18 iul 20, 09:59:46, davidson wrote: > > But first of all, I should reiterate that I lack expertise. > > I lack expertise. > > Second, I have no useful knowledge about real programming languages > (such as perl) to declare. Same disclaimers apply to me. > But as a peer, albeit a thick

Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

I use perl as a "slightly better sed", in particular the following commands I just cut and paste and modify for use, for many years now, to do (multi-)file search and replace: ``` # simple version: perl -p -i[.bak] -e 's/xxx/yyy/[g];' $(readlink somefile) # readlink is necessary do not clobber

sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose]

On Thu, 16 Jul 2020 Ajith R wrote: On Thursday 16 July 2020 4:54:09 AM IST davidson wrote: [snip]    $ sed 'y/\xc2\xa0/%/' somefile An off topic question: of sed, awk and perl, if I am to chose one to learn, which would you suggest. I wanted to do some substitutions. I read about them and de

Re: how u mine 4 utf8 [was Re: Using .XCompose]

On Sat, 18 Jul 2020 davidson wrote: On Thu, 16 Jul 2020 Ajith R wrote: On Thursday 16 July 2020 4:54:09 AM IST davidson wrote: [snip] I recommend two references I found helpful, though I didn't read either one especially carefully. I mostly just stared at the templates (the UTF-8 fighters bel

UTF-8 Everywhere -- Re: how u mine 4 utf8 [was Re: Using .XCompose]

Just in case anyone missed the memo, essential reading [significantly beautified since last I looked, looks like some of the structure intent from the link at bottom has been usefully incorporated]: UTF-8 Everywhere Manifesto http://utf8everywhere.org/ Found in this dark and dingy

how u mine 4 utf8 [was Re: Using .XCompose]

On Thu, 16 Jul 2020 Ajith R wrote: On Thursday 16 July 2020 4:54:09 AM IST davidson wrote: [snip]    $ sed 'y/\xc2\xa0/%/' somefile An off topic question: of sed, awk and perl, if I am to chose one to learn, which would you suggest. I wanted to do some substitutions. I read about them and de

Re: Using .XCompose

On Thursday 16 July 2020 5:27:16 AM IST davidson wrote: > ie, see whether there are nonbreaking spaces in the message body. > I attach ajith_msgbody_replace_nbsp.txt, which contains a '%' > character wherever a nonbreaking space was in the original. Thanks. So, the non-breaking spaces ar

Re: Using .XCompose

On Thursday 16 July 2020 4:54:09 AM IST davidson wrote: > And so you have set up known environmental conditions for subsequent > tests of that mechanism. Yes, that was my intention > which permits me to toggle my keyboard layout between two alternatives > ("us" and "ru") by striking caps

Re: Using .XCompose

On Mon, 13 Jul 2020 Greg Wooledge wrote: On Sat, Jul 11, 2020 at 08:32:34PM +, davidson wrote: '!' marks the spot of nonbreaking spaces that made it into OP's first report of odd behavior, upon testing the white scissors XCompose rule: $ grep "WHITE SCISSORS" d-u_xcompose_2020-07-08.nbsp

Re: Using .XCompose

On Wed, 15 Jul 2020 davidson wrote: [snip] If you have both the package called "info" and sed installed, like I do $ dpkg-query -l Yes, that is correct. I somehow manage to run a system with just three packages installed... I'm *that* good. $ dpkg-query -l info sed texinfo-doc-nonfree # Corr

Re: Using .XCompose

On Sun, 12 Jul 2020 Ajith R wrote: Could you please see if any of the lines in this message too behaves similarly ie, see whether there are nonbreaking spaces in the message body. ? The message body --of the message to which I reply-- I saved in the file ajith_msgbody.txt, which features i

Re: Using .XCompose

Hi All, I will start with what I did in sequence Using Konsole from my home directory 1)executed setxkbmap -layout us Naturally, since it is after all the topic of your thread, you are primarily interested in troubleshooting the XCompose mechanism. And so you have set up known environmental

Re: Using .XCompose

On Tue 14 Jul 2020 at 11:19:30 (+), Ajith R wrote: > On Sun 12 Jul 2020 at 22:50:23 (-0500), David Wright wrote: > > > OK. I wonder whether the problem you're having with using XCompose > > is that although those three characters > > look independent o

Fw: Using .XCompose

This is the third part - the layout file is comprssed and attached ajith in.tar.gz Description: application/gzip

Fw: Using .XCompose

This is the second part of my email.  > Note that the whitespace in your *attached* file (mixed tabs and > saces) matched my own, whereas the file here in your post does not. > That suggests that the 0xc2 0xa0 sequences may be a result of your > copy/paste operation. By "the file here in your pos

Fw: Using .XCompose

I was trying to send this mail for the past few days. It was not getting distributed probably because it is lengthy. So, I am trying to send it as two emails. This first part is being continued in the next email  Hi David, > OK. I wonder whether the problem you're having wi

Re: Using .XCompose

Hi David, > And I assume they're not in the files that you wrote from scratch, > like .XCompose. Would that be right? Yes, I couldn't find any in my XCompose file and in the layout file. > Kate appears to be a normal text editor. The third sentence of its > official description (https://kate-ed

Re: Using .XCompose

On Mon 13 Jul 2020 at 18:45:45 (+), Ajith R wrote: > Hi Greg, > > > In it, there is a brief mention of some option you can toggle called > > "Show Non-Printable Spaces", whose description is "Show/hide bounding > > box around non-printable spaces." > > Yes, though not very obvious, Kate does

Re: Using .XCompose

Hi Greg, > In it, there is a brief mention of some option you can toggle called > "Show Non-Printable Spaces", whose description is "Show/hide bounding > box around non-printable spaces." Yes, though not very obvious, Kate does show the non breaking sapces with an open box after selecting the op

Re: Using .XCompose

On Mon, Jul 13, 2020 at 06:24:58PM +, Ajith R wrote: > I was trying to find if NBSP are getting added in my .XCompose file > > I am using Kate. How can I accomplish that in Kate? I googled . The first result didn't talk about them at all. The second result was to a PDF which is apparently t

Re: Using .XCompose

Hi Greg, > I would imagine you were trying to pass a Unicode character.  If that's > the case, you need the \u or \U form instead. >  > grep $'\u00A0' .XCompose >  > Unicode character 00A0 is a non-breaking space.  It's not clear whether > that was your intention or not. Yes, that was my intent

Re: Using .XCompose

On Sat, Jul 11, 2020 at 08:32:34PM +, davidson wrote: > '!' marks the spot of nonbreaking spaces that made it into OP's first > report of odd behavior, upon testing the white scissors XCompose rule: > > $ grep "WHITE SCISSORS" d-u_xcompose_2020-07-08.nbsp | tr $'\xc2\xa0' \! > !

Re: Using .XCompose

On Sun, Jul 12, 2020 at 02:51:33PM +, Ajith R wrote: > 5) execute grep $'\x00A0' .XCompose. All lines from the .XCompose file were > listed. Bash's $'...' quoting allows several different forms, and you've used the wrong one. The \x is followed by *two* hex digits, to give a single byte. Yo

Re: Using .XCompose

with < U0D4D> . The display of this sequence as > a ligated conjunct or as three different symbols is dependant on the font the > user has. Whether this sequence is displayed as the ligated conjunct or as > three different charcters, it would be read the same. So, there isn't &

Re: Using .XCompose

Hi All, I will start with what I did in sequence Using Konsole from my home directory 1)executed setxkbmap -layout us 2)executed xmodmap which gave the following output xmodmap:  up to 4 keys per modifier, (keycodes in parentheses): shift       Shift_L (0x32),  Shift_R (0x3e) lock        Caps_

Re: Using .XCompose

On Sat, 11 Jul 2020 David Wright wrote: I would attempt to back out of the changes made. Removing/hiding .XCompose is an obvious first step. Yes. '!' marks the spot of nonbreaking spaces that made it into OP's first report of odd behavior, upon testing the white scissors XCompose rule: $ gr

Re: Using .XCompose

On Sat, 11 Jul 2020 davidson wrote: On Fri, 10 Jul 2020 Ajith R wrote: [snip] So, as Zeenan says, there is something fundamentally wrong in my system. I have to find that and correct it or reinstall everything. Is the situation still as you describe here? 8 July 2020 Ajith R to debian-use

Re: Using .XCompose

On Sat 11 Jul 2020 at 08:39:26 (+), davidson wrote: > On Fri, 10 Jul 2020 Ajith R wrote: > > Thanks for your experiment. The fact that it works atleast in some > > applications gives hope. > > […] > > Curious parties (like myself) wishing to understand the orthographic > peculiarities at issu

Re: Using .XCompose

On Sat, 11 Jul 2020 davidson wrote: On Fri, 10 Jul 2020 Ajith R wrote: Hi, Thanks for your experiment. The fact that it works atleast in some applications gives hope. There remains the strange fact that in no application (yet) have we seen *both* properties: 1. application produces multiple

Re: Using .XCompose

On Fri, 10 Jul 2020 Ajith R wrote: Hi, Thanks for your experiment. The fact that it works atleast in some applications gives hope. There remains the strange fact that in no application (yet) have we seen *both* properties: 1. application produces multiple characters in accordance with XC

Re: Using .XCompose

On Thu, 9 Jul 2020 davidson wrote: I have conducted an experiment with the following ~/.XCompose file, and tried to document it relatively thoroughly below. [snip] %% THREE XCOMPOSE RULES to test $ cat ~/.XCompose include "%L" : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D

Using .XCompose

Hi, Thanks for your experiment. The fact that it works atleast in some applications gives hope.  I copied your exact sentences to my compose file.  In Konsole the command cat ~/.XCompose gives the result: include "%L"    : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) (U0D19)

Re: Using .XCompose

On Wed, 8 Jul 2020 Ajith R wrote: Hi Zenaan, > Under the "Layout" tab, I have the option for "Compose key" - this > is a drop down list, and I chose the "Scroll Lock" key as my > compose key. Similar options are there for KDE too. I tried setting the Compose key from the KDE settings menu aft

Re: Using .XCompose [resend of xev_output_annotated.txt]

On Thu, 9 Jul 2020 davidson wrote: [snip] Finally, in case it is of interest to anyone, in the attached file "xev_output_annotated.txt" is some xev(1) output with commentary that gives a detailed close-up of performing steps 4 through 6 in an xterm. (As with the system synopsis, if it happens to

Re: Using .XCompose

On 2020-07-09 at 20:38, Zenaan Harkness wrote: > `apt-get` seems to have a `reinstall` subcommand, but I could not > find the same in the `apt` manpage for some reason. It's there, in the fourth subheading under DESCRIPTION: >>install, reinstall, remove, purge (apt-get(8)) >>

Re: Using .XCompose

On Thu, Jul 09, 2020 at 07:10:42PM +, Ajith R wrote: > > > It sounds like something is fundamentally wrong with your keymap. > > I started first by making a new layout file 'mal' and loading it using > setkbmap. Once I was sure the layout was working ok, I copied the layout to > the symbol

Re: Using .XCompose

I have conducted an experiment with the following ~/.XCompose file, and tried to document it relatively thoroughly below. It is my hope that OP and/or others may find some of this (unfortunately rather voluminous) information helpful or at least somewhat interesting, though it is difficult for me

Re: Using .XCompose

On Wed, Jul 08, 2020 at 07:14:33PM -0500, David Wright wrote: > > I was just trying to find out the reason why the 'composting' was > > not working. I tried including the modifier name and also without > > it. I tried moving the key to the first layer of keyboard layout > > (without shift or other

Re: Using .XCompose

On Wed, Jul 08, 2020 at 04:37:19PM +, Ajith R wrote: > Hi Zenaan, > > > Under the "Layout" tab, I have the option for "Compose key" - this is a > > drop down list, and I chose the "Scroll Lock" key as my compose key. > > > Similar options are there for KDE too. I tried setting the Compose k

Re: Using .XCompose

Sorry if the format looks a mess, but it's a consequence of replying to HTML. On Tue 07 Jul 2020 at 09:44:38 (+), Ajith R wrote: > I was looking at XCompose(3). Thanks for pointing out the mistake. It wasn't a mistake on your part. It was pointed out to me that section 3 has an alias redirec

Re: Using .XCompose

Hi Zenaan, > Under the "Layout" tab, I have the option for "Compose key" - this is a drop > down list, and I chose the "Scroll Lock" key as my compose key. Similar options are there for KDE too. I tried setting the Compose key from the KDE settings menu after trying xmodmap -e "keysym Caps_Loc

Re: Using .XCompose

Hi Greg, > Does your Caps Lock key work for Compose if you set it with: xmodmap -e "keysym Caps_Lock = Multi_key" > I tried this and found that the test definition in .XCopose file is working. However, when I change the .XCompose definition to <ങ>                     : "✄" or to <ങ> <

Re: [offlist] Re: Using .XCompose

On Wed, 8 Jul 2020 Zenaan Harkness wrote: On Wed, Jul 08, 2020 at 02:59:20AM +, Ajith R wrote: Hi David, As a rule, send replies to the listserv address:     debian-user@lists.debian.org 2. In-Line replies, instead of Top-Posting 3. I apologise for being a Terrible Person Hey! I tho

Re: [not-so-offlist] posting style [was Re: Using .XCompose]

On Wed, 8 Jul 2020 Ajith R wrote: Hi David, Debian conformant style looks like this instead: Do I understand the style correctly now? LOL. Probably not. Maybe I should have allowed your discovery of the mailing list's quoting conventions to take its natural course. It was maybe silly

Re: [offlist] posting style [was Re: Using .XCompose]

On Mi, 08 iul 20, 02:52:02, Ajith R wrote: > > Do I understand the style correctly now? Mostly. Think of it as "conversational" style, with the reply following the portion of text it addresses. Other text should be removed, unless it provides useful context (would your message make sense if re

Re: [offlist] Re: Using .XCompose

On Wed, Jul 08, 2020 at 02:59:20AM +, Ajith R wrote: > Hi David, > > >>> > As a rule, send replies to the listserv address: > >     debian-user@lists.debian.org > > 2. In-Line replies, instead of Top-Posting > 3. I apologise for being a Terrible Person Hey! I thought I had a patent, trade

Re: [offlist] Re: Using .XCompose

On Wed, 8 Jul 2020 Ajith R wrote: Hi David, As a rule, send replies to the listserv address:     debian-user@lists.debian.org 2. In-Line replies, instead of Top-Posting 3. I apologise for being a Terrible Person I didn't pay attention to the fact that the from address in the email was

Fw: Using .XCompose

Hi Zenaan, I'm not sure if it's been asked or stated by you, but which desktop are you using?   I am using KDE Thanks, ajith

Re: [offlist] Re: Using .XCompose

Hi David, >>> As a rule, send replies to the listserv address:     debian-user@lists.debian.org 2. In-Line replies, instead of Top-Posting 3. I apologise for being a Terrible Person >>> I didn't pay attention to the fact that the from address in the email was yours and not that of the list se

Re: [offlist] posting style [was Re: Using .XCompose]

Hi David, >>> Debian conformant style looks like this instead: >>> Do I understand the style correctly now? BTW, a query about how the original message is quoted with '<'. Is it done by hand or does any email clients do it automatically?  Is it necessary that each line s marked with '<'? Or

Re: Using .XCompose

On Wed, 8 Jul 2020 Zenaan Harkness wrote: I'm not sure if it's been asked or stated by you, but which desktop are you using? Elsewhere in the thread, https://lists.debian.org/msgid-search/885539452.3315628.1594115314...@mail.yahoo.com OP mentions using Konsole and Kate, to test changes ma

Re: Using .XCompose

I'm not sure if it's been asked or stated by you, but which desktop are you using? If you're new to Debian, perhaps just the default. I am using XFCE and in the menu: Applications → Settings → Keyboard there are three tabs "Behaviour", "Application Shortcuts" and "Layout". Under the "Layou

Re: Using .XCompose

Hi, From the above, it sounds to me that you are saying you would like a *single* keypress to result in entry of the above geminate form. Do I understand you correctly?Yes, perfectly. And if so, are you setting aside the question of how to enter the simple glyph   ങ (U+0D19) as an ex

Re: Using .XCompose

Hi, I test it by typing the letter from the keyboard (using shift / without it based on the layout specification) from the same terminal (Konsole) that i use setxkbmap to change to my layout. Then I run another terminal using the desktop link and try tying it. Then I try in Kate. And finally I

Re: Using .XCompose

On Tue, Jul 07, 2020 at 09:44:38AM +, Ajith R wrote: > I copied one line from your keyboard configuration file and  my keyboard file > looks like this now :# KEYBOARD CONFIGURATION FILE > > XKBMODEL="pc105" > XKBLAYOUT="in" > XKBVARIANT="eng" > XKBOPTIONS="lv3:ralt_switch,compose:caps,termina

Re: Using .XCompose

Hi David, Thanks for your reply.I presume XCompose(3) is a typo for 5, the file format section. There you will find that you don't use the XK_ prefix here. I was looking at XCompose(3). Thanks for pointing out the mistake. As I understand .XCompose, it is designed for "compositing",

Re: Using .XCompose

On Mon, 6 Jul 2020 davidson wrote: On Mon, Jul 06, 2020 at 05:34:59AM +, Ajith R wrote: [snip] The problem I am trying to tackle: One of the Malayalam letters, ങ (U+0D19), is used much more commonly in its geminate form which is composed of three unicode charcters ങ ്ങ (U+0D19 U+0D4D

Re: tangent on man page locations [was Re: Using .XCompose]

On Mon 06 Jul 2020 at 23:08:29 (+), davidson wrote: > On Mon, 6 Jul 2020 David Wright wrote: > > > I presume XCompose(3) is a typo for 5, the file format section. > > Probably not. Here we have > […] > and hence > > $ man -w 3 XCompose > /usr/share/man/man5/Compose.5.gz > > $ man -w 5

tangent on man page locations [was Re: Using .XCompose]

On Mon, 6 Jul 2020 David Wright wrote: I presume XCompose(3) is a typo for 5, the file format section. Probably not. Here we have $ zcat /usr/share/man/man3/XCompose.3.gz .so man5/Compose.5 $ realpath /usr/share/man/man5/XCompose.5.gz /usr/share/man/man5/Compose.5.gz and hence $

Re: Using .XCompose

On Mon 06 Jul 2020 at 05:34:59 (+), Ajith R wrote: > My .XCompose file in my home directory is-include "%L" > : "ങ്ങ" > : "ങ്ങ" > ങ : "ങ്ങ"- > I found the name XK_Shift_L in keysymdef.h file. I tried the unicode > character and its code as well to i

Re: Using .XCompose

On Mon, 6 Jul 2020 davidson wrote: On Mon, Jul 06, 2020 at 05:34:59AM +, Ajith R wrote: [snip] I am trying to build a custom layout for my mother tongue Malayalam (India, Kerala). [snip] The problem I am trying to tackle: One of the Malayalam letters, ങ (U+0D19), is used much more comm

Re: Using .XCompose

On Mon, Jul 06, 2020 at 05:34:59AM +, Ajith R wrote: Hi, I am new to Linux and Debian. That is good news. Welcome. I am trying to build a custom layout for my mother tongue Malayalam (India, Kerala). That sounds like an interesting challenge. Your original message appears to be in html

Re: Using .XCompose

On Mon, Jul 06, 2020 at 05:34:59AM +, Ajith R wrote: > Hi, > I am new to Linux and Debian.I am trying to build a custom layout for my > mother tongue Malayalam (India, Kerala). > The problem I am trying to tackle: > One of the Malayalam letters, ങ (U+0D19), is used much more commonly in its >

Re: Using .XCompose

On Mon, Jul 06, 2020 at 05:34:59AM +, Ajith R wrote: > I am new to Linux and Debian.I am trying to build a custom layout for my > mother tongue Malayalam (India, Kerala). Sadly, I know almost nothing about Asian languages. Does help you? If it's just a han

Using .XCompose

Hi, I am new to Linux and Debian.I am trying to build a custom layout for my mother tongue Malayalam (India, Kerala). The problem I am trying to tackle: One of the Malayalam letters, ങ (U+0D19), is used much more commonly in its geminate form which is composed of three unicode charcters ങ ് ങ (U+