Skip to main content
Post Locked by Robert Cartaino
Notice added Historical significance by Robert CartainoStaff
added 269 characters in body
Source Link

NOTICE:

Since this site is now in beta, it is time to have these conversations with the folks who are actually building this site. Please bring your comments and discussions to this site's 'meta' support forum so not to split these conversations. Thanks.

The emacs mentality encourages everyone to solve the problem they have, scratch their own itches. So there's a lot of existing user-written solutions out there.

Should we mark a preference for built-in emacs solutions? What do you think?

Proposal: Emacs

The emacs mentality encourages everyone to solve the problem they have, scratch their own itches. So there's a lot of existing user-written solutions out there.

Should we mark a preference for built-in emacs solutions? What do you think?

Proposal: Emacs

NOTICE:

Since this site is now in beta, it is time to have these conversations with the folks who are actually building this site. Please bring your comments and discussions to this site's 'meta' support forum so not to split these conversations. Thanks.

The emacs mentality encourages everyone to solve the problem they have, scratch their own itches. So there's a lot of existing user-written solutions out there.

Should we mark a preference for built-in emacs solutions? What do you think?

Proposal: Emacs

Source Link
Trevoke
  • 616
  • 3
  • 4

How do we (if at all) draw the line between built-in emacs features and user-written packages?

The emacs mentality encourages everyone to solve the problem they have, scratch their own itches. So there's a lot of existing user-written solutions out there.

Should we mark a preference for built-in emacs solutions? What do you think?

Proposal: Emacs