* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
@ 2009-02-20 18:39 era eriksson
2009-02-21 0:15 ` Ilya Zakharevich
0 siblings, 1 reply; 18+ messages in thread
From: era eriksson @ 2009-02-20 18:39 UTC (permalink / raw)
To: 1621; +Cc: Ilya Zakharevich
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
How about a slight refactoring to make it more obvious where to look for
the startup information?
Please find attached a proposed patch. This is just a quick proof of
concept; perhaps there is more startup-related information which could
be moved to the new variable.
(Cc:ing Ilya as I don't know whether he subscribes to this bug report.)
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: cperl-mode-el.patch --]
[-- Type: text/x-patch; name="cperl-mode-el.patch", Size: 2467 bytes --]
--- emacs-snapshot-20090207/lisp/progmodes/cperl-mode.el~ 2009-02-20 09:44:54.000000000 +0200
+++ emacs-snapshot-20090207/lisp/progmodes/cperl-mode.el 2009-02-20 09:43:09.000000000 +0200
@@ -28,6 +28,9 @@
;;; Commentary:
+;; To use this mode instead of perl-mode for Perl files, see the
+;; documentation for the variable `cperl-setup'
+
;; You can either fine-tune the bells and whistles of this mode or
;; bulk enable them by putting
@@ -37,8 +40,8 @@
;; correct to make whistles enabled by default.)
;; DO NOT FORGET to read micro-docs (available from `Perl' menu) <<<<<<
-;; or as help on variables `cperl-tips', `cperl-problems', <<<<<<
-;; `cperl-praise', `cperl-speed'. <<<<<<
+;; or as help on variables `cperl-setup', `cperl-tips', <<<<<<
+;; `cperl-problems',`cperl-praise', `cperl-speed'. <<<<<<
;; The mode information (on C-h m) provides some customization help.
;; If you use font-lock feature of this mode, it is advisable to use
@@ -700,6 +703,12 @@
;;; Short extra-docs.
+(defvar cperl-setup 'please-ignore-this-line
+ "If your Emacs does not default to `cperl-mode' on Perl files, and you
+want it to: put the following into your .emacs file:
+
+ (defalias 'perl-mode 'cperl-mode)"
+
(defvar cperl-tips 'please-ignore-this-line
"Get maybe newer version of this package from
http://ilyaz.org/software/emacs
@@ -721,11 +730,6 @@
Note that to enable Compile choices in the menu you need to install
mode-compile.el.
-If your Emacs does not default to `cperl-mode' on Perl files, and you
-want it to: put the following into your .emacs file:
-
- (defalias 'perl-mode 'cperl-mode)
-
Get perl5-info from
$CPAN/doc/manual/info/perl5-old/perl5-info.tar.gz
Also, one can generate a newer documentation running `pod2texi' converter
@@ -1369,6 +1373,7 @@
["Memorize Current" (cperl-set-style "Current") t]
["Memorized" (cperl-set-style-back) cperl-old-style])
("Micro-docs"
+ ["Setup" (describe-variable 'cperl-setup) t]
["Tips" (describe-variable 'cperl-tips) t]
["Problems" (describe-variable 'cperl-problems) t]
["Speed" (describe-variable 'cperl-speed) t]
@@ -1688,7 +1693,7 @@
with no args.
DO NOT FORGET to read micro-docs (available from `Perl' menu)
-or as help on variables `cperl-tips', `cperl-problems',
+or as help on variables `cperl-setup', `cperl-tips', `cperl-problems',
`cperl-praise', `cperl-speed'."
(interactive)
(kill-all-local-variables)
^ permalink raw reply [flat|nested] 18+ messages in thread* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-02-20 18:39 bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file era eriksson
@ 2009-02-21 0:15 ` Ilya Zakharevich
2009-02-21 10:54 ` era eriksson
0 siblings, 1 reply; 18+ messages in thread
From: Ilya Zakharevich @ 2009-02-21 0:15 UTC (permalink / raw)
To: era eriksson; +Cc: 1621
On Fri, Feb 20, 2009 at 08:39:37PM +0200, era eriksson wrote:
> How about a slight refactoring to make it more obvious where to look for
> the startup information?
>
> Please find attached a proposed patch. This is just a quick proof of
> concept; perhaps there is more startup-related information which could
> be moved to the new variable.
Again, I see no point in moving this information from the mode help.
Why would one think it is an improvement?
Yours,
Ilya
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-02-21 0:15 ` Ilya Zakharevich
@ 2009-02-21 10:54 ` era eriksson
2009-02-21 22:53 ` Ilya Zakharevich
0 siblings, 1 reply; 18+ messages in thread
From: era eriksson @ 2009-02-21 10:54 UTC (permalink / raw)
To: Ilya Zakharevich; +Cc: 1621
On Fri, 20 Feb 2009 16:15:34 -0800, "Ilya Zakharevich"
<ilya@Math.Berkeley.EDU> said:
> On Fri, Feb 20, 2009 at 08:39:37PM +0200, era eriksson wrote:
> > How about a slight refactoring to make it more obvious where to
> > look for the startup information?
> >
> > Please find attached a proposed patch. This is just a quick proof
> > of concept; perhaps there is more startup-related information which
> > could be moved to the new variable.
>
> Again, I see no point in moving this information from the mode help.
> Why would one think it is an improvement?
This information is currently not in the mode help proper at all. I
thought that this was by design. I agree that moving it to the
`cperl-mode' documentation string from the `cperl-tips' documentation
would already be an improvement.
The name of `cperl-tips' I think suggests that it explains how to use
some slightly esoteric features, and by and large this holds true. I
have been looking for the startup information on numerous occasions, and
more often than not ignored `cperl-tips' based on my interpretation of
what the name means.
Breaking out the setup / invocation information into its own clearly
labelled micro-doc would have the benefit of making it easy to refer to
it directly from e.g. the Commentary (as requested by the original
reporter) and other places (Info, Customize, etc) and separating it into
one coherent, rather short topic for those who are only looking for this
specific information. The `cperl-tips' "micro-doc" has a rather oblique
label and covers a lot of different topics, making it rather long, in
spite of the "micro".
Especially for a feature which is likely to be the first and possibly
only time a new user tries to get to know cperl-mode, usability is of
critical importance. If it's not blindingly obvious how to enable
cperl-mode by default, many potential users will simply give up on it.
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-02-21 10:54 ` era eriksson
@ 2009-02-21 22:53 ` Ilya Zakharevich
2009-03-16 2:10 ` era eriksson
0 siblings, 1 reply; 18+ messages in thread
From: Ilya Zakharevich @ 2009-02-21 22:53 UTC (permalink / raw)
To: era eriksson; +Cc: 1621
On Sat, Feb 21, 2009 at 12:54:41PM +0200, era eriksson wrote:
> > > Please find attached a proposed patch. This is just a quick proof
> > > of concept; perhaps there is more startup-related information which
> > > could be moved to the new variable.
> >
> > Again, I see no point in moving this information from the mode help.
> > Why would one think it is an improvement?
>
> This information is currently not in the mode help proper at all. I
> thought that this was by design. I agree that moving it to the
> `cperl-mode' documentation string from the `cperl-tips' documentation
> would already be an improvement.
Oups, did not realize this; sorry! I agree; >> TODO.
Thanks,
Ilya
P.S.
> Breaking out the setup / invocation information into its own clearly
> labelled micro-doc would have the benefit of making it easy to refer to
> it directly from e.g. the Commentary (as requested by the original
> reporter) and other places (Info, Customize, etc) and separating it into
> one coherent, rather short topic for those who are only looking for this
> specific information. The `cperl-tips' "micro-doc" has a rather oblique
> label and covers a lot of different topics, making it rather long, in
> spite of the "micro".
I expect that most people would explore Micro-docs from the mode menu.
So putting this info there would be chicken-and-egg problem: to access
the info on enabling the mode, they would need to enable the mode.
If this info is clearly visible in the mode help, do you think it
still makes sense to duplicate it in the micro-docs? Like
What is this mode you are using? I did not see it before... How to
enable it? Oh, it has a mode menu...
;-)
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-02-21 22:53 ` Ilya Zakharevich
@ 2009-03-16 2:10 ` era eriksson
2009-03-16 4:03 ` Ilya Zakharevich
0 siblings, 1 reply; 18+ messages in thread
From: era eriksson @ 2009-03-16 2:10 UTC (permalink / raw)
To: Ilya Zakharevich; +Cc: 1621
On Sat, 21 Feb 2009 14:53:49 -0800, "Ilya Zakharevich"
<ilya@Math.Berkeley.EDU> said:
> On Sat, Feb 21, 2009 at 12:54:41PM +0200, era eriksson wrote:
> > > > Please find attached a proposed patch. This is just a quick
> > > > proof of concept; perhaps there is more startup-related
> > > > information which could be moved to the new variable.
> > >
> > > Again, I see no point in moving this information from the mode
> > > help. Why would one think it is an improvement?
> >
> > This information is currently not in the mode help proper at all. I
> > thought that this was by design. I agree that moving it to the
> > `cperl-mode' documentation string from the `cperl-tips'
> > documentation would already be an improvement.
<...>
> P.S.
>
> > Breaking out the setup / invocation information into its own clearly
> > labelled micro-doc would have the benefit of making it easy to
> > refer to it directly from e.g. the Commentary (as requested by the
> > original reporter) and other places (Info, Customize, etc) and
> > separating it into one coherent, rather short topic for those who
> > are only looking for this specific information. The `cperl-tips'
> > "micro-doc" has a rather oblique label and covers a lot of
> > different topics, making it rather long, in spite of the "micro".
>
> I expect that most people would explore Micro-docs from the mode menu.
> So putting this info there would be chicken-and-egg problem: to access
> the info on enabling the mode, they would need to enable the mode.
>
> If this info is clearly visible in the mode help, do you think it
> still makes sense to duplicate it in the micro-docs? Like
>
> What is this mode you are using? I did not see it before... How to
> enable it? Oh, it has a mode menu...
>
> ;-)
Sorry for this late reply; missed your PS originally.
I do think it makes sense to keep it in the micro-docs. If nothing
else, it's easy to refer newcomers to it, and even if you did manage to
somehow set it up on your own, you might want to review the "official"
way to do it, perhaps while idly browsing the micro-docs looking for
neat stuff you didn't originally understand how to set up.
Another thing I've been meaning to propose would be for cperl-mode to
offer to install itself into your .emacs when you invoke it for the
first time, sort of like how (put 'dangerous-command 'disabled nil)
occasionally gets added to your .emacs after asking for permission.
(IIRC narrow-to-region is one of these "dangerous" commands, and some of
the horizontal scrolling commands which I never use except by mistake.)
Do you think it would be appropriate to remove the +wontfix tag from
this bug? (Not sure whether or not this bug applies to upstream Emacs
or your code at this point, and how the two are being coordinated, if at
all.)
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-03-16 2:10 ` era eriksson
@ 2009-03-16 4:03 ` Ilya Zakharevich
2009-03-16 8:48 ` era eriksson
0 siblings, 1 reply; 18+ messages in thread
From: Ilya Zakharevich @ 2009-03-16 4:03 UTC (permalink / raw)
To: era eriksson; +Cc: 1621
On Mon, Mar 16, 2009 at 04:10:57AM +0200, era eriksson wrote:
> I do think it makes sense to keep it in the micro-docs. If nothing
> else, it's easy to refer newcomers to it, and even if you did manage to
> somehow set it up on your own, you might want to review the "official"
> way to do it, perhaps while idly browsing the micro-docs looking for
> neat stuff you didn't originally understand how to set up.
>
> Another thing I've been meaning to propose would be for cperl-mode to
> offer to install itself into your .emacs when you invoke it for the
> first time, sort of like how (put 'dangerous-command 'disabled nil)
> occasionally gets added to your .emacs after asking for permission.
> (IIRC narrow-to-region is one of these "dangerous" commands, and some of
> the horizontal scrolling commands which I never use except by mistake.)
Myself, I would hate it if it were like this: supposed I'm annoyed by
this "feature" - should it also ask whether to put a command into
.emacs which would disable this question? ;-)
> Do you think it would be appropriate to remove the +wontfix tag from
> this bug?
I do not know what "the +wontfix" means. The situation is as in "I
considered your suggestions, I appreciated your suggestions, and I
even mentioned possibly reconsidering your suggestions in my TODO
files". ;-)
Yours,
Ilya
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-03-16 4:03 ` Ilya Zakharevich
@ 2009-03-16 8:48 ` era eriksson
2009-03-16 9:12 ` Ilya Zakharevich
0 siblings, 1 reply; 18+ messages in thread
From: era eriksson @ 2009-03-16 8:48 UTC (permalink / raw)
To: Ilya Zakharevich; +Cc: 1621
On Sun, 15 Mar 2009 21:03:14 -0700, "Ilya Zakharevich"
<ilya@Math.Berkeley.EDU> said:
> On Mon, Mar 16, 2009 at 04:10:57AM +0200, era eriksson wrote:
> > Another thing I've been meaning to propose would be for cperl-mode
> > to offer to install itself into your .emacs when you invoke it for
> > the first time, sort of like how (put 'dangerous-command 'disabled
> > nil) occasionally gets added to your .emacs after asking for
> > permission. (IIRC narrow-to-region is one of these "dangerous"
> > commands, and some of the horizontal scrolling commands which I
> > never use except by mistake.)
>
> Myself, I would hate it if it were like this: supposed I'm annoyed by
> this "feature" - should it also ask whether to put a command into
> .emacs which would disable this question? ;-)
The 'disabled logic is fairly unobtrusive IMHO. My suggestion would be
to (defvar 'cperl-mode-install-setup-flag 'ask) and then either add
(setq 'cperl-mode-install-setup-flag nil) or 't to the user's .emacs if
the user doesn't specifically select "continue to ask me" instead of
"yes" or "no".
The main logic would simply inspect the value during load and do or do
not (there is no try :-) depending on what it says.
To my uneducated $self this sounds like it would need to go in a
separate .el file which would have some sort of ;;;###autoload but maybe
there is a more elegant way.
> > Do you think it would be appropriate to remove the +wontfix tag from
> > this bug?
>
> I do not know what "the +wontfix" means. The situation is as in "I
> considered your suggestions, I appreciated your suggestions, and I
> even mentioned possibly reconsidering your suggestions in my TODO
> files". ;-)
I'm talking about the bug's status in the Emacs Bug Tracking System at
http://emacsbugs.donarmstrong.com/1621 -- if Emacs maintainers don't
object, I'll change it to "forwarded <ilya@Math.Berkeley.EDU>" and take
away the wontfix tag. I hope it's not too far of a stretch to interpret
your answer to mean that you don't really care about the Emacs BTS
status of this bug report.
(The bug tracking system is an installation of the Debian BTS which by
design doesn't ever obfuscate email addresses. I really hate this
"feature" because it's a regular fly paper for spam. Maybe you would
prefer if I put something else than your email address in the
"forwarded" field, although I guess by and large the damage is already
done.)
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-03-16 8:48 ` era eriksson
@ 2009-03-16 9:12 ` Ilya Zakharevich
2009-03-16 20:00 ` era eriksson
0 siblings, 1 reply; 18+ messages in thread
From: Ilya Zakharevich @ 2009-03-16 9:12 UTC (permalink / raw)
To: era eriksson; +Cc: 1621
On Mon, Mar 16, 2009 at 10:48:40AM +0200, era eriksson wrote:
> I'm talking about the bug's status in the Emacs Bug Tracking System at
> http://emacsbugs.donarmstrong.com/1621 -- if Emacs maintainers don't
> object, I'll change it to "forwarded <ilya@Math.Berkeley.EDU>" and take
> away the wontfix tag. I hope it's not too far of a stretch to interpret
> your answer to mean that you don't really care about the Emacs BTS
> status of this bug report.
>
> (The bug tracking system is an installation of the Debian BTS which by
> design doesn't ever obfuscate email addresses. I really hate this
> "feature" because it's a regular fly paper for spam. Maybe you would
> prefer if I put something else than your email address in the
> "forwarded" field, although I guess by and large the damage is already
> done.)
Thanks, Era, I would prefer obfuscation, and not of berkeley address,
but of ilyaz@cpan.org...
Yours,
Ilya
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-03-16 9:12 ` Ilya Zakharevich
@ 2009-03-16 20:00 ` era eriksson
2009-03-16 23:50 ` Ilya Zakharevich
0 siblings, 1 reply; 18+ messages in thread
From: era eriksson @ 2009-03-16 20:00 UTC (permalink / raw)
To: Ilya Zakharevich; +Cc: 1621
On Mon, 16 Mar 2009 02:12:05 -0700, "Ilya Zakharevich"
<ilya@Math.Berkeley.EDU> said:
> On Mon, Mar 16, 2009 at 10:48:40AM +0200, era eriksson wrote:
> > I'm talking about the bug's status in the Emacs Bug Tracking System at
> > http://emacsbugs.donarmstrong.com/1621 -- if Emacs maintainers don't
> > object, I'll change it to "forwarded <ilya@Math.Berkeley.EDU>" and
> > take away the wontfix tag. I hope it's not too far of a stretch to
> > interpret your answer to mean that you don't really care about the
> > Emacs BTS status of this bug report.
> >
> > (The bug tracking system is an installation of the Debian BTS which by
> > design doesn't ever obfuscate email addresses. I really hate this
> > "feature" because it's a regular fly paper for spam. Maybe you would
> > prefer if I put something else than your email address in the
> > "forwarded" field, although I guess by and large the damage is already
> > done.)
>
> Thanks, Era, I would prefer obfuscation, and not of berkeley address,
> but of ilyaz@cpan.org...
Done now, but you should be aware that the whole conversation is being
archived at the URL quoted above, in mbox format and various other
renderings. I apologize if this was not sufficiently clear earlier.
(It's the Cc: which does it.)
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2009-03-16 20:00 ` era eriksson
@ 2009-03-16 23:50 ` Ilya Zakharevich
0 siblings, 0 replies; 18+ messages in thread
From: Ilya Zakharevich @ 2009-03-16 23:50 UTC (permalink / raw)
To: era eriksson; +Cc: 1621
On Mon, Mar 16, 2009 at 10:00:31PM +0200, era eriksson wrote:
> > Thanks, Era, I would prefer obfuscation, and not of berkeley address,
> > but of ilyaz@cpan.org...
>
> Done now, but you should be aware that the whole conversation is being
> archived at the URL quoted above, in mbox format and various other
> renderings. I apologize if this was not sufficiently clear earlier.
> (It's the Cc: which does it.)
Oups! And I wondered why spam started to arrive directly to berkeley
address... The major problem is that this Cc-address does not follow
the conventions for maillist addresses. (My emailing setup tries to
recognize mailing lists, and uses a "logical" From-address in such
cases. I reconfigured it now; checking.... Yes, it does recognize
this Cc address as a mailing list now...)
Thanks,
Ilya
^ permalink raw reply [flat|nested] 18+ messages in thread
[parent not found: <20070401035915.3121.73126.malonedeb@gangotri.ubuntu.com>]
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
[not found] <20070401035915.3121.73126.malonedeb@gangotri.ubuntu.com>
@ 2008-12-18 5:14 ` Jason A. Spiro
2008-12-18 21:39 ` Stefan Monnier
2020-10-15 15:11 ` Lars Ingebrigtsen
0 siblings, 2 replies; 18+ messages in thread
From: Jason A. Spiro @ 2008-12-18 5:14 UTC (permalink / raw)
To: bug-gnu-emacs
Package: emacs
Severity: wishlist
Feature request forwarded from https://launchpad.net/bugs/99634 :
---------- Forwarded message ----------
From: Jason Spiro <jasonspiro3@gmail.com>
Date: 2007/3/31
Subject: [Bug 99634] Please move cperl micro-docs to top of the
cperl-mode.el file
To: jasonspiro3@gmail.com
Public bug reported:
Binary package hint: emacs-snapshot
I wanted to set Emacs to use cperl-mode instead of perl-mode, but I
didn't know how. It turns out the answer was in the cperl-tips section
on line 710 of the file.
Please move the cperl micro-docs from the middle of the cperl-mode.el
Elisp file to the top of the file. This will make more people see them.
^ permalink raw reply [flat|nested] 18+ messages in thread* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2008-12-18 5:14 ` Jason A. Spiro
@ 2008-12-18 21:39 ` Stefan Monnier
2008-12-19 2:28 ` Glenn Morris
2008-12-19 6:06 ` Jason A. Spiro
2020-10-15 15:11 ` Lars Ingebrigtsen
1 sibling, 2 replies; 18+ messages in thread
From: Stefan Monnier @ 2008-12-18 21:39 UTC (permalink / raw)
To: Jason A. Spiro; +Cc: 1621, bug-gnu-emacs
> Please move the cperl micro-docs from the middle of the cperl-mode.el
> Elisp file to the top of the file. This will make more people see them.
I suggest we add some text in the Commentary that point people to the
docstrings below. Moving the docstrings wholesale will increase the
merge burden when syncing with Ilya's version.
Stefan
^ permalink raw reply [flat|nested] 18+ messages in thread* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2008-12-18 21:39 ` Stefan Monnier
@ 2008-12-19 2:28 ` Glenn Morris
2008-12-19 6:06 ` Jason A. Spiro
1 sibling, 0 replies; 18+ messages in thread
From: Glenn Morris @ 2008-12-19 2:28 UTC (permalink / raw)
To: Stefan Monnier; +Cc: 1621, Jason A. Spiro
tags 1621 wontfix
stop
Stefan Monnier wrote:
>> Please move the cperl micro-docs from the middle of the cperl-mode.el
>> Elisp file to the top of the file. This will make more people see them.
>
> I suggest we add some text in the Commentary that point people to the
> docstrings below.
There already is such text, indicated with capital letters and "<<<<<"
signs, no less.
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2008-12-18 21:39 ` Stefan Monnier
2008-12-19 2:28 ` Glenn Morris
@ 2008-12-19 6:06 ` Jason A. Spiro
2008-12-20 22:53 ` Ilya Zakharevich
1 sibling, 1 reply; 18+ messages in thread
From: Jason A. Spiro @ 2008-12-19 6:06 UTC (permalink / raw)
To: cpan; +Cc: 1621, bug-gnu-emacs
2008/12/18 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Please move the cperl micro-docs from the middle of the cperl-mode.el
>> Elisp file to the top of the file. This will make more people see them.
>
> I suggest we add some text in the Commentary that point people to the
> docstrings below. Moving the docstrings wholesale will increase the
> merge burden when syncing with Ilya's version.
Ilya, could you too please move the micro-docs from the middle of the
your cperl-mode.el Elisp file to the top of the file? This will make
more people see the micro-docs. And then I hope the GNU Emacs
maintainers will adopt your change downstream.
Please Reply to All. By the way, I sent mail to this address
@ilyaz.org because I could not find any non-Perl-related address to
write to.
--
Jason Spiro: software/web developer, packager, trainer, IT consultant.
I support Linux, UNIX, Windows, and more. Contact me to discuss your needs.
+1 (416) 992-3445 / www.jspiro.com
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2008-12-19 6:06 ` Jason A. Spiro
@ 2008-12-20 22:53 ` Ilya Zakharevich
2008-12-20 23:41 ` Jason A. Spiro
0 siblings, 1 reply; 18+ messages in thread
From: Ilya Zakharevich @ 2008-12-20 22:53 UTC (permalink / raw)
To: Jason A. Spiro; +Cc: 1621, bug-gnu-emacs
On Fri, Dec 19, 2008 at 01:06:44AM -0500, Jason A. Spiro wrote:
> Ilya, could you too please move the micro-docs from the middle of the
> your cperl-mode.el Elisp file to the top of the file? This will make
> more people see the micro-docs.
Could you please explain to me the mental model of people who would
read the code of CPerl, but not the mode help, and would not explore
the mode menu?
Thanks,
Ilya
^ permalink raw reply [flat|nested] 18+ messages in thread
* bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
2008-12-18 5:14 ` Jason A. Spiro
2008-12-18 21:39 ` Stefan Monnier
@ 2020-10-15 15:11 ` Lars Ingebrigtsen
1 sibling, 0 replies; 18+ messages in thread
From: Lars Ingebrigtsen @ 2020-10-15 15:11 UTC (permalink / raw)
To: Jason A. Spiro; +Cc: 1621
"Jason A. Spiro" <jasonspiro4@gmail.com> writes:
> I wanted to set Emacs to use cperl-mode instead of perl-mode, but I
> didn't know how. It turns out the answer was in the cperl-tips section
> on line 710 of the file.
I've now added a more explicit reference in the comments in cperl-mode
as to where to find the microdocs in Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2020-10-15 15:11 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-20 18:39 bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file era eriksson
2009-02-21 0:15 ` Ilya Zakharevich
2009-02-21 10:54 ` era eriksson
2009-02-21 22:53 ` Ilya Zakharevich
2009-03-16 2:10 ` era eriksson
2009-03-16 4:03 ` Ilya Zakharevich
2009-03-16 8:48 ` era eriksson
2009-03-16 9:12 ` Ilya Zakharevich
2009-03-16 20:00 ` era eriksson
2009-03-16 23:50 ` Ilya Zakharevich
[not found] <20070401035915.3121.73126.malonedeb@gangotri.ubuntu.com>
2008-12-18 5:14 ` Jason A. Spiro
2008-12-18 21:39 ` Stefan Monnier
2008-12-19 2:28 ` Glenn Morris
2008-12-19 6:06 ` Jason A. Spiro
2008-12-20 22:53 ` Ilya Zakharevich
2008-12-20 23:41 ` Jason A. Spiro
[not found] ` <20081221000241.GA17638@powdermilk.math.berkeley.edu>
2008-12-21 0:13 ` Jason A. Spiro
2020-10-15 15:11 ` 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).