From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?UTF-8?B?6Lev5a6i?= Newsgroups: gmane.emacs.devel Subject: Re: [elpa] master 74818d5: Brief Mode v5.86 release. Date: Sun, 21 Oct 2018 00:01:30 +0800 Message-ID: References: <20181018141131.22680.53035@vcs0.savannah.gnu.org> <20181018141132.6E8BA208EC@vcs0.savannah.gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000004ca92a0578ab24ee" X-Trace: blaine.gmane.org 1540051326 26132 195.159.176.226 (20 Oct 2018 16:02:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 20 Oct 2018 16:02:06 +0000 (UTC) To: Stefan Monnier , Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 20 18:02:02 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gDthM-0006bV-IB for ged-emacs-devel@m.gmane.org; Sat, 20 Oct 2018 18:01:56 +0200 Original-Received: from localhost ([::1]:55896 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gDtjS-0004DR-Vk for ged-emacs-devel@m.gmane.org; Sat, 20 Oct 2018 12:04:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34033) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gDtha-0002OP-Al for emacs-devel@gnu.org; Sat, 20 Oct 2018 12:02:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gDthZ-0007ot-CX for emacs-devel@gnu.org; Sat, 20 Oct 2018 12:02:10 -0400 Original-Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]:46503) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gDthZ-0007oX-5H for emacs-devel@gnu.org; Sat, 20 Oct 2018 12:02:09 -0400 Original-Received: by mail-ed1-x52b.google.com with SMTP id v22-v6so1114926eds.13 for ; Sat, 20 Oct 2018 09:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=AV4xxpzODLh0NTeC9zPBs7fHg0i9jGl3YSu8cty9rv0=; b=DJcl3ADt5lTkxDuXv+wQCs11hn4Fi/t1vNJGlOrfzzfeOyBKVNtUjVMFaL1a4v1ceN Ys/SQVnMgNXj2zapNI71zpOZe5LIcPB9y5NZmGmHAcHfImu07sD9foGngTbw0BCALk50 xJdxlWxAqcxzfXUnB3EDtN3yy3h4Ub1cKQtO5wl1m7raKA7zBU7Rl+U4YU+sMjocC7Lp L2rxW+85mNEHc2gdmfZoLfrLlbuvgd6k1SwF42QUUSpt00BTwbTh0WL3dD9OzCrFaCOz M0N+Cb05jxos39qqp8+BmMo1ifAgwkozPOtHx3jOK7KmWuwsxJ35ZHKk0CdswjEwqrtm N4AA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=AV4xxpzODLh0NTeC9zPBs7fHg0i9jGl3YSu8cty9rv0=; b=O8HIPXfRoLUuWLqACw4hO2CKmSXPXo77YnBdJt6oo5LsSl8d+FxUii9o+PtV5w7wmn 1K6tA5Rf9SkmqhpKjFyT4QSvkMm104X5RbQY4qjEmDEEwXqlPf32KhpmQqo5GweQv9bK Fu/46lxvCPpoXtp9H0osCej+JWpxwHqglBPsenfQdtj1rhra4joSGoDAekJfGwbuXzxa OHIzwgGmAaomN87BhzIbsMiN/xC6nmPm+/P7j3uH6jyyUOukyogpb3fSssH5CPByay+A eA3kfWmgC5JYvoS5mtoHVXbn8nHCnmw2cFNiWfpG48ZLGcIQ8iiElEX3RbQ+KKUhBxbc i3ng== X-Gm-Message-State: ABuFfoj8a4h25YM6DV5GbrI2vhmnjGK+ruXFlcZzrekqG/kibPvddjJQ 6knwZbJKRBgJIfczzG0ZFO9rlmM82/tCs7ifynNYhuOz X-Google-Smtp-Source: AJdET5cO5jxqWcrcE5AhBdQlznlOiTc+XtrTSqYoDppB9IayUb9mnUsUjiZzRmp6ygKgkRHwjMX3v4AT7J7t5VFuvLQ= X-Received: by 2002:a17:906:f6cc:: with SMTP id jo12-v6mr938283ejb.28.1540051327296; Sat, 20 Oct 2018 09:02:07 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::52b X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:230525 Archived-At: --0000000000004ca92a0578ab24ee Content-Type: text/plain; charset="UTF-8" > Not sure what you mean exactly, here: `b` is a script that's part of the > `brief` GNU ELPA package. So to get this script, they've had to > "install" (at the very least download and unpack) that package already. > The easiest way to install it is with `M-x package-install RET`, AFAIK In EmacsWiki page (or "README.org") I suggest this command line: $ emacs -Q -eval "(progn (package-initialize) (package-refresh-contents) \ (package-install 'brief) (save-buffers-kill-emacs))" so basically a new user only need to copy&paste this command... > (regarding other discussions about 'b'...) However I am facing another more basic problem that I can't make either 'b' or 'README.org' packed into brief package. I read thru all the multi-file related info but they seems only applies to .el files. I am still trying, if I still can't even pack 'b' or README.org I will just put them in github and modify EmacsWiki and README.org about the above command line without even using package. Of course the 'b' would need to be modified accordingly. > > Yes, quite a few bash specific things. > I find it difficult to find those, but I usually find it easy to change > the code not to use them, so if you can point them out I can try and > see if I can remove this dependency without making the code worse. Mainly about the array things. I would like to get rid of the possibility that white space exists in some argument (like file name or directory with white space) so bash arrays are more convenient to me. There must be 'sh' ways to achieve this but maybe later when I have time. Maybe 'b' need to be revised for github anyway. > Are they likely to dig into the code of `b` to find that? Or look for > a b.el file in the package (e.g. if they installed it via package.el > they may not even know where to look to find b.el)? > ... > Maybe you could advertise those in a different way, e.g. in the README, Once users find the behavior of launching 'b' and of Emacs+briefpkg differs, they will findout in the 'b' script. Surely better be in README.org. > I don't follow: the above definition already defines the > `brief-auto-backup-mode` command which toggles. Arg, you're right, will do that later. Best regards, Luke Lee --0000000000004ca92a0578ab24ee Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Not sure what you mean exactly, here= : `b` is a script that's part of the
> `brief` GNU ELPA package.= =C2=A0 So to get this script, they've had to
> "install"= ; (at the very least download and unpack) that package already.
> The= easiest way to install it is with `M-x package-install RET`, AFAIK

= In EmacsWiki page (or "README.org") I suggest this command line:<= br>
$ emacs -Q -eval "(progn (package-initialize) (package-refresh-= contents) \
(package-install 'brief) (save-buffers-kill-emacs))"= ;

so basically a new user only need to copy&paste this command..= .

> (regarding other discussions about 'b'...)

How= ever I am facing another more basic problem that I can't make
eithe= r 'b' or 'README.org' packed into brief package.=C2=A0 I re= ad thru all
the multi-file related info but they seems only applies to = .el files.=C2=A0
I am still trying, if I still can't even pack '= ;b' or README.org I will just
put them in github and modify EmacsWik= i and README.org about the above
command line without even using packag= e.=C2=A0 Of course the 'b' would need
to be modified accordingly= .

> > Yes, quite a few bash specific things.
> I find it= difficult to find those, but I usually find it easy to change
> the = code not to use them, so if you can point them out I can try and
> se= e if I can remove this dependency without making the code worse.

Mai= nly about the array things.=C2=A0 I would like to get rid of the
possib= ility that white space exists in some argument (like file name
or directory with white space) so bash arrays are more convenient= to
me.=C2=A0 There must be 'sh' ways to= achieve this but maybe later when
I have time.= =C2=A0 Maybe 'b' need to be revised for github anyway.

> = Are they likely to dig into the code of `b` to find that?=C2=A0 Or look for=
> a b.el file in the package (e.g. if they installed it via package.= el
> they may not even know where to look to find b.el)?
> ...<= br>> Maybe you could advertise those in a different way, e.g. in the REA= DME,

Once users find the behavior of launching 'b' and of Em= acs+briefpkg
differs, they will findout in the 'b' script.=C2= =A0 Surely better be in
README.org.

> I don't follow: the= above definition already defines the
> `brief-auto-backup-mode` comm= and which toggles.

Arg, you're right, will do that later.
Best regards,
Luke Lee

--0000000000004ca92a0578ab24ee--