From owner-freebsd-questions@freebsd.org Mon Jul 9 20:28:28 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D71E102BA9C for ; Mon, 9 Jul 2018 20:28:28 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CCF484FE2 for ; Mon, 9 Jul 2018 20:28:27 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.57.160]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0MYLUv-1fXvmj3Ujh-00VAHG; Mon, 09 Jul 2018 22:28:24 +0200 Date: Mon, 9 Jul 2018 22:28:24 +0200 From: Polytropon To: mayuresh@kathe.in Cc: freebsd-questions@freebsd.org Subject: Re: backspace not working with mg Message-Id: <20180709222824.74761578.freebsd@edvax.de> In-Reply-To: <01ae8d96e55aefbd96312bd36717baa6@kathe.in> References: <01ae8d96e55aefbd96312bd36717baa6@kathe.in> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:I0YeWBnqFVQEIUdsGdGt4PPN6i/1ZPKviGO1oXY/3ZFlg/kS7cQ RGr0va+a+5+eRBnDvadLZqJJkMrYiJfpxqcVZcAF0rcrjVjxDs1ngZbRwvBydAIxrPxIJiV K1gKN4MhwckoShX2qtrNSRkLacquGrDes9Wk8D9kMTqa89K9lJ5mepU55zvUW3JYyTKEY6z zZh+IFfjSSliLSOsZAo0Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:kkBN57cl+9Q=:ARRChIhp1qxJnoXjWHOq2z fHHdqQ5lst4wjEupLEq6+7ES+UVcsPQaah/GmCvgWJJ8wKIA6/URdkJ7E/Ohxa5t50o4sWi7t qJ0qQshFadGD3/f246RhAQeiotfV7JT9k24QL7/6jm8N2jauIieKnbkFj7Rx5OFtEFlZqMYwI iXT82Qz9cCWV7AhTbCShIzEENykotNeMnVr5ILKtTRQvM2x9uDbc88eOunzQa47Tr126MEIe4 Z/uMNgrx5+yPlKZJeYAUqmNcBqq3CFb9NnlUbCmd6s/datxF8WjXZULJ0hZB8Kf94NwGPSbbZ mTsdI4jx6XEfYPa+5pc0MwsjUpGvPUBGPTDnGGYtz35z1tXelMfm2liWwXol5khZQyXu+61i+ vXDCWQbvArcjA1K7DaJED3kC8Lz349zqMkn1paeXzP62kP66pzcLbBkkwuvXuwO2As+uoUeM+ dTwQVs/aX4wJMnuCqkTeUhCEozT50tYRPc055XJbhtDMlq7+JwJYxvfIGmPzOziciNNwYiLrw k89x9x6QITSbVStJ/zd9va5L9gWq9SsBLVf4jXhR0zRVKxu+jJJXwFhdypLIRSQjuaAHvTh6w SaLpv84IikidOLvnat17TMHxoyxvt99ObUEb+IZkZAGFp2NhdLadYyMltKLkkkcde8am9sz22 bcesSHtIDBG/dnQRD7cjRcwKE4I3EOzlj0GDG9xcb9+zcTvkww9zoWTAe6nwlPqLVdzOmv4/6 hjFqrZxFCn+myl17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2018 20:28:28 -0000 On Mon, 09 Jul 2018 06:45:15 +0000, Mayuresh Kathe wrote: > my backspace key functions just right with 'ee' but not under "mg". > the system just beeps and the cursor just sits where it was. > i am a "vi" guy, but now am migrating to "mg" because the nature > of work for me going forward would involve a "lisp-1" system and > "mg" provides nice parentheses matching feature without the bloat > i would have to tolerate if using "gnu emacs". If parentheses matching for lips is your goal, and you're already a "vi person", why not use vim? It has support for syntax highlighting and will clearly show you the parentheses counterpart. You can also use gvim if you wish to run it on X. Both programs share the same configuration, so it doesn't matter if you're using it locally as gvim on X, or vim via SSH. And you don't have to learn emacs. ;-) Regarding a non-working backspace key: First check if it sends the correct code, it should be ASCII 8, or ^H (Ctrl+H). That is the default on FreeBSD, of course. The command % stty -a will tell you the currently active configuration for the control characters, look for "erase". Then of course check your mg configuration if it overrides something. I don't think this is the default, but it could still be. For testing, load a file with mg, and press Ctrl+H instead of backspace. Does it do what it is supposed to do? Also check your terminal configuration. While xterm usually applies the FreeBSD OS defaults, terminals primarily for use with Linux (and therefore integrated in a voluminous desktop environment) may be configured differently. So if the terminal emulator you're using can be configured, check its options as well. PS. Please don't assume I'm an "anti-emacs person". In fact, I'm a "vi person" being too stupid to understand the magic and the power of emacs, that's why the decision. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...