Re: [isabelle] Remaining reasons for Proof General
Using a compose key is definitely a good way to just ignore jEdit's
completion. I have a customised .XCompose file that allows me to write
∀, ∃, ∈, ⟹, ⊆ and so on using the Compose key; this solution has the
advantage that it also works the same way outside of jEdit. I only just
realised that I could simply use my Compose key to solve the whole
Unicode token issue for me, maybe I should give jEdit another try.
On 12/11/13 16:30, Joachim Breitner wrote:
> Am Dienstag, den 12.11.2013, 16:13 +0100 schrieb bnord:
>> I find the "not" case still unpleasant.
>> - I can't use "~<TAB>" because it's a composing key so I have to type
> do you really mean “composing”, in the sense of the Compose key, or
> rather “dead” key?
> For a dead key i would expect that <~><space> will print "~", not "~ " –
> why do you need Ctrl-B? What OS by the way?
> I have disabled dead keys and use the Compose Key
> (https://en.wikipedia.org/wiki/Compose_key) so that <Compose><~><n>
> yiels ñ. But that might not be an option if you have to enter a lot of
> accents. In that case, you might want to customize jEdit, as suggested
> by René¹².
> ¹ Yes, that is <R><e><n><Compose><´><e>.
> ² No, ¹ is not <Compose><^><1>, although that works as well, but
> ³ My <Compose> key is <Print>, which Thinkpads have for some reason
> between the right AltGr and String. I enable that with
> keycode 107 = Multi_key
> in my ~/.Xmodmap.
This archive was generated by a fusion of
Pipermail (Mailman edition) and