unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>,
	Tino Calancha <tino.calancha@gmail.com>
Subject: Re: [Emacs-diffs] master 75d9a55: Fix bug 32543
Date: Wed, 19 Sep 2018 07:03:28 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1809190653590.30724@calancha-pc.dy.bbexcite.jp> (raw)
In-Reply-To: <jwvtvmma536.fsf-monnier+emacsdiffs@gnu.org>



On Tue, 18 Sep 2018, Stefan Monnier wrote:

>>> - why store this info in text-properties rather than in
>>>   buffer-local variables?
>> I realized the buffer was already saved there with property
>> `occur-title'; I didn't wanted to scatter around related info.
>
> Hmmm... do you happen to have some intuition about why the buffer was
> saved in a text-property rather than in a buffer-local var?
> It's a really odd choice (less efficient, more work for the coder, with
> various side-problems like "on which char should I put it", etc...).
I think the favourite answer of my ex-boss fits well here:
For historical reasons.
> [ Also, why is it saved under a name like `occur-title` rather
>  than, say `occur-buffer`?  ]
Ditto.

>>>> +      (with-current-buffer buffer
>>>> +        (when (wholenump orig-line)
>>>> +          (goto-char 1)
>>>
>>> I'd recommend `point-min` instead of 1 here.
>> OK.  I always remember the discussion at
>> https://lists.gnu.org/archive/html/emacs-devel/2009-08/msg00520.html
>> but I forgot which was the encouraged practice there: in these cases
>> I follow the 50% rule to reject 0% success ratio (I know, it brings
>> 50% failure ratio: life is full of injustice).
>
> I just always recommend `point-min`.  Hard-coded constants are always
> weird in source code, whereas `point-min` clearly says what this
> constant is (and in terms of efficiency, it's a wash, or `point-min`
> might even be marginally more efficient).
I have a private library to autocomplete `point-min' (not just that!);
I just type
(pmin) <Super> a
and I get
(point-min)

During prototyping I sometimes write things like:
(goto-char 1)

I replace those `1' with `point-min' once I get
something ready.  I forgot this time.



  reply	other threads:[~2018-09-18 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180918123203.24597.514@vcs0.savannah.gnu.org>
     [not found] ` <20180918123205.8BE9B204DF@vcs0.savannah.gnu.org>
2018-09-18 12:56   ` [Emacs-diffs] master 75d9a55: Fix bug 32543 Stefan Monnier
2018-09-18 17:37     ` Tino Calancha
2018-09-18 21:11       ` Stefan Monnier
2018-09-18 22:03         ` Tino Calancha [this message]
2018-09-19 13:34           ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1809190653590.30724@calancha-pc.dy.bbexcite.jp \
    --to=tino.calancha@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).