unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#43294: 28: Combine name-spaces hi-lock and hl-line
@ 2020-09-09 17:38 Boruch Baum
  2020-10-16  7:05 ` Lars Ingebrigtsen
  0 siblings, 1 reply; 2+ messages in thread
From: Boruch Baum @ 2020-09-09 17:38 UTC (permalink / raw)
  To: 43294


Here a duplicate posting of several messages from the emacs-devel list so the
request doesn't get lost thereq. Should the project
decide to approve this and choose which to alias, I could do the
coding...

----- Forwarded message from Boruch Baum <boruch_baum@gmx.com> -----

Date: Sun, 6 Sep 2020 13:51:47 -0400
From: Boruch Baum <boruch_baum@gmx.com>
To: Emacs-Devel List <emacs-devel@gnu.org>
Subject: name-space consistency
User-Agent: NeoMutt/20180716

Slightly apropos the current thread opening discussion of things that
could be done for emacs v28...

Here's an example of an annoying and persistently vexing name-space
inconsistency: to highlight based upon a regexp in a buffer, one uses
functions from package hi-lock (that a lower-case 'i', not an 'ell') and
to highlight the current line within a buffer one uses functions from
package hl-line (that's an 'ell', not a lower-case 'i').

Unless you use both often (or have a memory superior to mine), you're
bound to mis-type hl-lock or hi-line.

Would the project consider aliasing and deprecating one of those
name-spaces? Or breaking backward-compatibility and just refactoring
one?

----- End forwarded message -----


On 2020-09-06 21:04, Eli Zaretskii wrote:
> > Date: Sun, 6 Sep 2020 13:51:47 -0400
> > From: Boruch Baum <boruch_baum@gmx.com>
> >
> > Unless you use both often (or have a memory superior to mine), you're
> > bound to mis-type hl-lock or hi-line.
> >
> > Would the project consider aliasing and deprecating one of those
> > name-spaces? Or breaking backward-compatibility and just refactoring
> > one?
>
> The latter is out of the question.  The former can be done if there's
> enough support for it (but expect some dispute regarding which
> variant to prefer ;-).

----- End forwarded message -----

On 2020-09-06 14:50, Boruch Baum wrote:
> At this point, the 'measured' support on the list is 100%. If you accept
> and wait for the mail-in ballots, the final results could take months...
>

----- End forwarded message -----

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0





^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#43294: 28: Combine name-spaces hi-lock and hl-line
  2020-09-09 17:38 bug#43294: 28: Combine name-spaces hi-lock and hl-line Boruch Baum
@ 2020-10-16  7:05 ` Lars Ingebrigtsen
  0 siblings, 0 replies; 2+ messages in thread
From: Lars Ingebrigtsen @ 2020-10-16  7:05 UTC (permalink / raw)
  To: Boruch Baum; +Cc: 43294

Boruch Baum <boruch_baum@gmx.com> writes:

> Here a duplicate posting of several messages from the emacs-devel list so the
> request doesn't get lost thereq. Should the project
> decide to approve this and choose which to alias, I could do the
> coding...

[...]

>> The latter is out of the question.  The former can be done if there's
>> enough support for it (but expect some dispute regarding which
>> variant to prefer ;-).

There didn't seem to be much enthusiasm for this, and it seems to me
it'd be a lot of code churn for little gain.  So I'm closing this bug
report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-10-16  7:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-09 17:38 bug#43294: 28: Combine name-spaces hi-lock and hl-line Boruch Baum
2020-10-16  7:05 ` Lars Ingebrigtsen

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).