Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #224422 > unrolled thread
| Started by | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| First post | 2020-07-06 07:40 +0200 |
| Last post | 2020-07-10 05:00 +0200 |
| Articles | 7 on this page of 87 — 14 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-06 07:40 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-06 14:30 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-06 14:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-06 21:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-06 22:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-07 17:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-07 08:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-07 17:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-09 23:50 +0200
Re: Using .XCompose [resend of xev_output_annotated.txt] davidson <davidson@freevolt.org> - 2020-07-10 03:40 +0200
Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-10 10:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 10:40 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 12:30 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-12 17:00 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-13 06:00 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-13 14:00 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-13 20:30 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-13 20:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-13 20:50 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-13 21:50 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-14 05:40 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-15 16:50 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-15 17:10 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-15 17:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 01:30 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 02:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-16 20:40 +0200
how u mine 4 utf8 [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-18 03:20 +0200
UTF-8 Everywhere -- Re: how u mine 4 utf8 [was Re: Using .XCompose] Zenaan Harkness <zenaan@freedbms.net> - 2020-07-18 07:40 +0200
Re: how u mine 4 utf8 [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-18 09:20 +0200
Re: how u mine 4 utf8 [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 13:00 +0200
Fw: how u mine 4 utf8 [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 12:50 +0200
Re: Fw: how u mine 4 utf8 [was Re: Using .XCompose] Tom Browder <tom.browder@gmail.com> - 2020-07-19 13:10 +0200
Re: how u mine 4 utf8 [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 13:50 +0200
sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-18 12:10 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Zenaan Harkness <zenaan@freedbms.net> - 2020-07-18 12:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] William Michels <wjm1@caa.columbia.edu> - 2020-07-18 22:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-18 13:20 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] songbird <songbird@anthive.com> - 2020-07-18 21:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] <tomas@tuxteam.de> - 2020-07-18 16:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] mick crane <mick.crane@gmail.com> - 2020-07-18 22:40 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] <tomas@tuxteam.de> - 2020-07-18 23:10 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] mick crane <mick.crane@gmail.com> - 2020-07-18 23:30 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] <tomas@tuxteam.de> - 2020-07-19 10:40 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] mick crane <mick.crane@gmail.com> - 2020-07-20 13:20 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] David Christensen <dpchrist@holgerdanske.com> - 2020-07-19 01:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 12:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] David Christensen <dpchrist@holgerdanske.com> - 2020-07-19 23:30 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-19 13:40 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] William Michels <wjm1@caa.columbia.edu> - 2020-07-19 21:50 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] David Wright <deblis@lionunicorn.co.uk> - 2020-07-23 04:00 +0200
Re: sed:awk:perl::rock:paper:chainsaw [was Re: Using .XCompose] songbird <songbird@anthive.com> - 2020-07-23 12:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 02:00 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-16 20:40 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-11 17:00 +0200
Tex characters Teemu Likonen <tlikonen@iki.fi> - 2020-07-11 18:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 22:40 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-13 14:00 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-16 07:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-11 18:10 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 15:30 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-20 15:30 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 18:20 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-10 12:50 +0200
Re: [offlist] posting style [was Re: Using .XCompose] Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 05:00 +0200
Re: [offlist] posting style [was Re: Using .XCompose] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-08 07:00 +0200
Re: [not-so-offlist] posting style [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-08 07:10 +0200
Re: [offlist] Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 05:00 +0200
Re: [offlist] Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-08 05:20 +0200
Re: [offlist] Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-08 05:40 +0200
Re: [offlist] Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-08 08:00 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-07 00:40 +0200
tangent on man page locations [was Re: Using .XCompose] davidson <davidson@freevolt.org> - 2020-07-07 01:10 +0200
Re: tangent on man page locations [was Re: Using .XCompose] David Wright <deblis@lionunicorn.co.uk> - 2020-07-07 03:50 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-07 11:50 +0200
Re: Using .XCompose Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-07 13:40 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 16:30 +0200
Re: Using .XCompose David Wright <deblis@lionunicorn.co.uk> - 2020-07-09 02:20 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-09 04:20 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-08 01:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-08 02:30 +0200
Fw: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 05:10 +0200
Re: Using .XCompose Ajith R <ajithramayyan@yahoo.co.in> - 2020-07-08 18:40 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-09 04:00 +0200
Re: Using .XCompose Zenaan Harkness <zenaan@freedbms.net> - 2020-07-10 02:40 +0200
Re: Using .XCompose The Wanderer <wanderer@fastmail.fm> - 2020-07-10 02:50 +0200
Re: Using .XCompose davidson <davidson@freevolt.org> - 2020-07-10 05:00 +0200
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-08 02:30 +0200 |
| Message-ID | <Aq68h-7Xm-5@gated-at.bofh.it> |
| In reply to | #224545 |
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.1594115314827@mail.yahoo.com OP mentions using Konsole and Kate, to test changes made to ~/.XCompose. So KDE would be my guess. Only a guess, of course. OP will probably tell us the facts. But if you want my speculation in the meantime, there you are. [rest snipped]
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-08 05:10 +0200 |
| Message-ID | <Aq8D8-1bl-3@gated-at.bofh.it> |
| In reply to | #224545 |
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
[toc] | [prev] | [next] | [standalone]
| From | Ajith R <ajithramayyan@yahoo.co.in> |
|---|---|
| Date | 2020-07-08 18:40 +0200 |
| Message-ID | <AqlgZ-dW-7@gated-at.bofh.it> |
| In reply to | #224545 |
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_Lock = Multi_key" suggested by Greg. My .XCompose file is: include "%L" <Multi_key> <s> <x> : "✄" U2704 # WHITE SCISSORS Now, things are even more strange. When I press the Caps Lock, a strange character appears. (I copy pasted it, searched the net and found it to be unicode compose character.) Then when I type s, the Caps Lock light gets switched on and the character S (caps) appears on screen. Then when I type X, the compose character and S become invisible and x/X doesn't appear. When I change focus to another window, the terminal in which I was typing shows the compose character and S. This behaviour has not changed after I unchecked the settings through KDE settings menu, after restarting computer, re-issuing xmodmap command or changing the layout to us. The same sequence is seen with typing in Kate as well. Even when I use Scroll Lock as the compose key, the situation is only different in that the s is not capitalised. Any idea what might be wrong? Thanks, ajith
[toc] | [prev] | [next] | [standalone]
| From | Zenaan Harkness <zenaan@freedbms.net> |
|---|---|
| Date | 2020-07-09 04:00 +0200 |
| Message-ID | <Aqu0V-5nY-7@gated-at.bofh.it> |
| In reply to | #224608 |
On Wed, Jul 08, 2020 at 04:37:19PM +0000, 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 after trying xmodmap -e "keysym Caps_Lock = Multi_key" suggested by Greg. My .XCompose file is: > include "%L" > <Multi_key> <s> <x> : "✄" U2704 # WHITE SCISSORS > > Now, things are even more strange. When I press the Caps Lock, a strange character appears. (I copy pasted it, searched the net and found it to be unicode compose character.) Then when I type s, the Caps Lock light gets switched on and the character S (caps) appears on screen. Then when I type X, the compose character and S become invisible and x/X doesn't appear. When I change focus to another window, the terminal in which I was typing shows the compose character and S. > > This behaviour has not changed after I unchecked the settings through KDE settings menu, after restarting computer, re-issuing xmodmap command or changing the layout to us. The same sequence is seen with typing in Kate as well. Even when I use Scroll Lock as the compose key, the situation is only different in that the s is not capitalised. > > Any idea what might be wrong? It sounds like something is fundamentally wrong with your keymap. I suggest starting again, resetting everything back to your chosen defaults at install - reset your modified keymap file back to whatever you copied to begin the exercise, and test that compose is working as it should. Then, make no more than a single change, apply and test that single change. Don't move forward till the one change is working. That's what I did (although it's been a 2 or 3 years since I dabbled) - I had one tiny little brace missing at one stage, and when you don't see it, you just don't see it, so after that I brutally realigned everything with obnoxious spaces, so that all tha braces, and commas, lined up - THAT solved the accidental missing brace which never bit me again :/
[toc] | [prev] | [next] | [standalone]
| From | Zenaan Harkness <zenaan@freedbms.net> |
|---|---|
| Date | 2020-07-10 02:40 +0200 |
| Message-ID | <AqPf3-1s3-5@gated-at.bofh.it> |
| In reply to | #224616 |
On Thu, Jul 09, 2020 at 07:10:42PM +0000, 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 file 'in'. Now, to check for the .XCompose, I load the us layout (which I haven't modified). I have changed the keyboard file as well ( using dpkg-reconfigure keyboard-configuration ) > > > > I suggest starting again, resetting everything back to your chosen defaults at install - reset your modified keymap file back to whatever you copied to begin the exercise, and test > > that compose is working as it should. > > I have reset everything back to the original as far as I can recollect, but COmpose is not working. Is there a way to reset the system other than by reinstalling? I don't know sorry. But it sounds like you've made an important discovery that something is not quite right about your current /etc or etc. To reset without reinstalling, others will probably need to jump in and assist with specifics, but the gist of it is this: Work out which package contains the file you've modified, make a backup of the file you've modified, reinstall the package. `apt-get` seems to have a `reinstall` subcommand, but I could not find the same in the `apt` manpage for some reason. Good luck,
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2020-07-10 02:50 +0200 |
| Message-ID | <AqPoK-1vr-13@gated-at.bofh.it> |
| In reply to | #224664 |
[Multipart message — attachments visible in raw view] — view raw
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)) >> Performs the requested action on one or more packages specified via >> regex(7), glob(7) or exact match. The requested action can be >> overridden for specific packages by appending a plus (+) to the >> package name to install this package or a minus (-) to remove it. Plus a couple more paragraphs. Basically the same behavior as the apt-get version, and they even point you to apt-get(8) for more. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2020-07-10 05:00 +0200 |
| Message-ID | <AqRqy-2MH-1@gated-at.bofh.it> |
| In reply to | #224608 |
[Multipart message — attachments visible in raw view] — view raw
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 after trying > > xmodmap -e "keysym Caps_Lock = Multi_key" > > suggested by Greg. My .XCompose file is: > > include "%L" > <Multi_key> <s> <x> : "✄" U2704 # WHITE SCISSORS > > Now, things are even more strange. When I press the Caps Lock, a > strange character appears. (I copy pasted it, searched the net and > found it to be unicode compose character.) Incidentally, I have sometimes found that attempting to copy-paste strange characters can result in even *stranger* characters. (This has the potential to lead to more confusion, instead of less.) Since the character of interest is one you are typing yourself, you might try this: $ xxd - # and then type whatever you want to examine When you're done entering what you want to examine, type Ctrl-d. Type it once if you're at the beginning of a new line. Type it twice if you aren't. (Somebody smart might explain to us why this is so.) If you don't have xxd installed, you could use the following line as a poor man's xxd: $ od -Ax -tx1z -v - # type whatever, do Ctrl-d to end it, as above the "od" program is in coreutils, which "apt-cache show coreutils" says is an "Essential: yes" package. So you probably have it for sure. Replace the last "-" with "> somefilename" (in either command above) if you want to put the output into a file to show somebody else, or to treasure it always as a keepsake. But make sure that "somefilename" isn't already a file containing stuff you want to keep (because you will lose that stuff forever, instantly). > Then when I type s, the Caps Lock light gets switched on and the > character S (caps) appears on screen. Then when I type X, the > compose character and S become invisible and x/X doesn't > appear. When I change focus to another window, the terminal in which > I was typing shows the compose character and S. IT'S ALIVE! Sorry, this is probably a very frustrating development. (I'm sure I'd be pretty upset in your shoes.) I wonder if the output from either $ xmodmap # with no arguments, just the bare command or $ xmodmap -pk would be illuminating. The output from the first command (the bare command with no arguments) will probably not be too overwhelming. It ought to summarise your current modifier keys. The output from the second is your keymap table, and will likely be of considerable size. If you want to review it in the moment, I would suggest doing $ xmodmap -pk | less -S so you can examine it in a pager. The "-S" option keeps the pager from wrapping long lines, and there could be some pretty long lines when you print your current keymap table. This way you can get some semblance of columns, and use the arrow keys to scroll left/right to view those long lines, instead of having trying to disentangle a bunch of wraparound garbage. If you want to share the output with us here (and I hope that you do), you can put the output into a pair of files like so: $ xmodmap > somefilename.pm $ xmodmap -pk > somefilename.pk And then import them into a message body, however one does that in your email setup. As always, these commands all have manual pages, and you have these pages installed if you have the commands. You can read them over if you are at all curious, at least to reassure yourself that I'm not telling you to do something evil that you don't want done. $ man command # read the command manual in a pager $ man -f command # see super-brief description of command $ man -k commandliketerm # search for pertinent commands But you came here with a manual page referenced in your original post at the top of this thread, didn't you? So you don't need me telling you this. > this behaviour has not changed after I unchecked the settings > through KDE settings menu, after restarting computer, re-issuing > xmodmap command or changing the layout to us. The same sequence is > seen with typing in Kate as well. Even when I use Scroll Lock as the > compose key, the situation is only different in that the s is not > capitalised. > > Any idea what might be wrong? Well, I can't really say. I haven't quite followed the progression here as closely as I would have liked to. And I don't have a whole lot of experience with many of the tools that you've been playing with. This is all a learning experience for me, too. But I am looking forward to seeing what we can sort out once we see your modifier table and keymap table. I hope your week has gone well, all things considered. -- You won't feel the collar if you don't go anywhere.
[toc] | [prev] | [standalone]
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
Back to top | Article view | linux.debian.user
csiph-web