From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: 2 ideas (Was: Re: bug#31518: [PATCH 10/21] gnu: Add emacs-google-translate.) Date: Sat, 09 Jun 2018 11:12:13 +0200 Message-ID: <8C242137-C737-4814-9367-6C90F5E96CD2@riseup.net> References: <20180518184910.9987-21-ambrevar@gmail.com> <20180601075112.28494-1-ambrevar@gmail.com> <87vaatjptt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----BNWUHWJPVTBHKT3K39X5TW83C9AJO8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fRaWx-00082w-At for guix-devel@gnu.org; Sat, 09 Jun 2018 05:51:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fRaWu-0006wF-8r for guix-devel@gnu.org; Sat, 09 Jun 2018 05:51:31 -0400 In-Reply-To: <87vaatjptt.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: ludo@gnu.org, Pierre Neidhardt Cc: Guix-devel ------BNWUHWJPVTBHKT3K39X5TW83C9AJO8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi On June 8, 2018 4:49:34 PM GMT+02:00, ludo@gnu=2Eorg wrote: >Hi Pierre, > >Pierre Neidhardt skribis: > >> * gnu/packages/emacs=2Escm (emacs-google-translate): New variable=2E > >[=2E=2E=2E] > >> + (home-page "https://github=2Ecom/atykhonov/google-translate") >> + (synopsis "Emacs interface to Google Translate") >> + (description >> + "Setup: >> +@code{ >> +(require 'google-translate) >> +(require 'google-translate-default-ui) >> +(global-set-key \"\\C-ct\" 'google-translate-at-point) >> +(global-set-key \"\\C-cT\" 'google-translate-query-translate)} >> + >> +or >> + >> +@code{(require 'google-translate) >> +(require 'google-translate-smooth-ui) >> +(global-set-key \"\\C-ct\" 'google-translate-smooth-translate)} [=2E=2E=2E]=20 >> + (license license:gpl3+)))) > >Applied but I removed the documentation: I don=E2=80=99t think it=E2=80= =99s the right >place to document the package=2E=20 In Arch there is a post-install hook that enables informing the user of ad= ditional steps needed to actually use the software as intended=2E=20 I find that useful=2E Is there a guix alternative?=20 If not is this something we should implement?=20 Also pacman logs all messages about packages installed to a logfile in /va= r/log which is very very useful if you missed a message while installing mu= ltiple packages and it no longer is in the scrollbuffer or just high up=2E= =20 Maybe the need for this is much smaller with Guix because we have no break= ing changes that the user must act on as here sometimes is in arch=2E=20 Idea of changing the way we handle emacs add on packages: ---------------------------------------- In the example above we might want to modify the emacs packages to have tw= o =2Eemacs-files in total: 1) The usual =2Eemacs where the user puts in changes and where we by default = load =2Eemacs-guix-packages=2E=20 2) =2Eemacs-guix-packages where the setup information for add ons installed i= s automatically added=2E=20 In the example above this would be added to the botten of =2Eemacs-guix-pa= ckages: "(require 'google-translate) (require 'google-translate-default-ui) (global-set-key \"\\C-ct\" 'google-translate-at-point) (global-set-key \"\\C-cT\" 'google-translate-query-translate)" What do you think? This would enable us to create an out of the box working emacs experience = with loads of add ons that by default do not collide with each other e=2Eg= =2E by cleverly choosing the default key bindings for the add ons=2E --=20 Cheers Swedebugia ------BNWUHWJPVTBHKT3K39X5TW83C9AJO8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi
--
Cheers Swedebugia ------BNWUHWJPVTBHKT3K39X5TW83C9AJO8--