#36 macro menu and language-specific items

open
nobody
None
5
2004-07-15
2002-10-25
No

In the macro menu, macros can be bound to a
specific language by appending "@language" to
their name. This doesn't seem to work for the
"plain" mode.

Discussion

  • Nobody/Anonymous

    Logged In: NO

    "Plain" is not a language mode (as documented). This is no
    bug, maybe a feature request.

    --Joerg

     
  • Tony Balinski

    Tony Balinski - 2003-04-16

    Logged In: YES
    user_id=618141

    What about using the * language specifier? If you define a
    macro entry with that, you get it appearing in all languages
    (including Plain) except those where a macro of the same
    name has been defined. I believe this to be more useful than
    having a Plain language macro specifier.

     
  • Philipp Lehman

    Philipp Lehman - 2003-04-17

    Logged In: YES
    user_id=635642

    There are cases in which you want a macro to appear in plain
    mode only. Think of macros that format, say, an email reply.
    No harm will be done if they show up in HTML or C++ mode, but
    it's not terribly useful.

     
  • Nobody/Anonymous

    Logged In: NO

    FYI there is patch number 559814.

    (Plain mode was intended as plain. For mail create a
    language mode. )

    --Joerg

     
  • Philipp Lehman

    Philipp Lehman - 2003-04-17

    Logged In: YES
    user_id=635642

    > FYI there is patch number 559814.

    Thanks for the pointer.

    > (Plain mode was intended as plain. For mail create a
    > language mode. )

    Fair point!

     
  • Tom Heathcote

    Tom Heathcote - 2003-05-01

    Logged In: YES
    user_id=523342

    I find it useful to have the ability to add Plain-mode-only menu
    items. Which is why I wrote patch 559814. The patch is
    fairly trivial, and still applies cleanly to the CVS source.

    I tend to use this functionality for general operations like Sort
    and Number Lines, which are not at all appropriate for source
    code (in any language).

    It is also very useful to change the behaviour of the Spell and
    ispell entries on my shell menu, for most language modes I
    want these menu items to operate only on a selection - after
    all it makes no sense to spell check an entire source file.
    But in plain mode I want them to act on either the selection or
    the whole file.

    This could be done by having a Spell@* with command input
    set to "either", and then overriding this in every language
    mode with Spell@this_mode with command input set
    to "selection".

    But with the patch, there is a much easier way: have the
    standard Spell@* entry work on "selection", and then override
    just once with a Spell@Plain entry with a command input
    of "either".

    Since I wrote the patch, it is perhaps no surprise that I am in
    favour of adding this functionality as standard.

    I do agree that the @* feature is more useful than an @Plain
    feature. But would it not be more useful still to have both?

     
  • Thorsten Haude

    Thorsten Haude - 2003-11-26

    Logged In: YES
    user_id=119143

    Could this be recategorized as Feature Request?
    (What does this 'RFE' mean anyway?)

     
  • Thorsten Haude

    Thorsten Haude - 2004-07-15

    Logged In: YES
    user_id=119143

    Could this please be recategorized as Feature Request?

     
  • Thorsten Haude

    Thorsten Haude - 2004-07-15
    • priority: 5 --> 2
     
  • Nathan Gray

    Nathan Gray - 2004-07-15

    Logged In: YES
    user_id=121553

    Changing to a feature request.

    RFE = Request for enhancement

     
  • Thorsten Haude

    Thorsten Haude - 2004-07-15

    Logged In: YES
    user_id=119143

    I obviously cannot work on RFEs. Could you please bring the
    priority back to the usual 5? I only lowered it because I
    couldn't move it from the bug box. Thanks.

     
  • Nathan Gray

    Nathan Gray - 2004-07-15
    • priority: 2 --> 5
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks