Loading ...
Sorry, an error occurred while loading the content.

enhancement to ME 04

Expand Messages
  • salmankhilji
    I have finally upgraded to 04 RC4 release on Linux. I am using the ME Server feature where in KDE File Manager I double click on a file and have an existing
    Message 1 of 6 , Feb 14, 2004
    • 0 Attachment
      I have finally upgraded to 04 RC4 release on Linux.

      I am using the ME Server feature where in KDE File Manager I double
      click on a file and have an existing instance of ME open the file up.
      The problem is that once this happens, ME does not come to the
      foreground.

      After I double-clicked on the file, for a moment I thought that
      nothing had happened. So I tried again. When nothing happened the
      second time, then it came back to my mind that oh---I have enabled the
      server feature and should bring the window to foreground manually.

      I think from a users point of view, ME should automatically bring
      itself to foreground when the server launches the file.

      BTW, I personally prefer that ME does a vertical split instead of a
      horizontal split when the server opens the new file. Can someone tell
      me which entry in the emf files I have to modify to do this?

      Salman
    • Phillips, Steven
      ... This is how it is supposed to work and how it does work on windows. The server works via a *server* buffer which effectively gets pumped with new commands
      Message 2 of 6 , Feb 15, 2004
      • 0 Attachment
        > -----Original Message-----
        > From: salmankhilji [mailto:salmankhilji@...]
        > Sent: 14 February 2004 20:17
        > To: jasspa@yahoogroups.com
        > Subject: [jasspa] enhancement to ME 04
        >
        >
        > I have finally upgraded to 04 RC4 release on Linux.
        >
        > I am using the ME Server feature where in KDE File Manager I double
        > click on a file and have an existing instance of ME open the file up.
        > The problem is that once this happens, ME does not come to the
        > foreground.
        >
        > After I double-clicked on the file, for a moment I thought that
        > nothing had happened. So I tried again. When nothing happened the
        > second time, then it came back to my mind that oh---I have enabled the
        > server feature and should bring the window to foreground manually.
        >
        > I think from a users point of view, ME should automatically bring
        > itself to foreground when the server launches the file.

        This is how it is supposed to work and how it does work on windows. The server works via a *server* buffer which effectively gets pumped with new commands via other processes (e.g. me -o foo.c) so if you swap to this buffer you will see that it simply lists the commands to be run. The last command will typically be '2 popup-window' which means popup the frame. On a console version of ME there is not a lot ME can do to achieve this, however there probably is on an X-Term version but the meFrameXTermMakeCur function in unixterm.c is some what lacking. Hopefully we can address this for the release.

        > BTW, I personally prefer that ME does a vertical split instead of a
        > horizontal split when the server opens the new file. Can someone tell
        > me which entry in the emf files I have to modify to do this?

        The macro file you need to play with is meserver.emf, I would suggest adding a vertical split to just before the window-popup if there's only one window.

        Steve
      • Jon Green
        ... This will be fixed in the next release. The fix is defined as follows if you want to patch it yourself. (line number will not match 20040206 release as
        Message 3 of 6 , Feb 17, 2004
        • 0 Attachment
          salmankhilji wrote:
          > I have finally upgraded to 04 RC4 release on Linux.
          >
          > I am using the ME Server feature where in KDE File Manager I double
          > click on a file and have an existing instance of ME open the file up.
          > The problem is that once this happens, ME does not come to the
          > foreground.
          >
          > After I double-clicked on the file, for a moment I thought that
          > nothing had happened. So I tried again. When nothing happened the
          > second time, then it came back to my mind that oh---I have enabled the
          > server feature and should bring the window to foreground manually.

          This will be fixed in the next release. The fix is defined
          as follows if you want to patch it yourself.

          (line number will not match 20040206 release as there
          have been some other fixes to X ishell).

          Jon.

          Index: unixterm.c
          ===================================================================
          RCS file: /export/cvs/cvsroot/me/src/unixterm.c,v
          retrieving revision 2.38
          diff -c -w -r2.38 unixterm.c
          *** unixterm.c 14 Feb 2004 17:43:22 -0000 2.38
          --- unixterm.c 17 Feb 2004 20:49:32 -0000
          ***************
          *** 3087,3092 ****
          --- 3087,3093 ----
          void
          meFrameXTermMakeCur(meFrame *frame)
          {
          + XRaiseWindow(mecm.xdisplay, meFrameGetXWindow(frame)) ;
          }

          /* Heres the xterm equivalent, note that its done in two stages */
          [EXIT 1]


          >
          > I think from a users point of view, ME should automatically bring
          > itself to foreground when the server launches the file.
          >
          > BTW, I personally prefer that ME does a vertical split instead of a
          > horizontal split when the server opens the new file. Can someone tell
          > me which entry in the emf files I have to modify to do this?
          >
          > Salman
          >
        • Jon Green
          ... Attached is a solution. Copy this file to your user directory and it will shaddow the released file and will be executed in preference. The split is only
          Message 4 of 6 , Feb 17, 2004
          • 0 Attachment
            Phillips, Steven wrote:
            >
            >>-----Original Message-----
            >>From: salmankhilji [mailto:salmankhilji@...]
            >>Sent: 14 February 2004 20:17
            >>To: jasspa@yahoogroups.com
            >>Subject: [jasspa] enhancement to ME 04
            >>
            >>
            >>I have finally upgraded to 04 RC4 release on Linux.
            >>
            >>I am using the ME Server feature where in KDE File Manager I double
            >>click on a file and have an existing instance of ME open the file up.
            >> The problem is that once this happens, ME does not come to the
            >>foreground.
            >>
            >>After I double-clicked on the file, for a moment I thought that
            >>nothing had happened. So I tried again. When nothing happened the
            >>second time, then it came back to my mind that oh---I have enabled the
            >>server feature and should bring the window to foreground manually.
            >>
            >>I think from a users point of view, ME should automatically bring
            >>itself to foreground when the server launches the file.
            >
            >
            > This is how it is supposed to work and how it does work on windows. The server works via a *server* buffer which effectively gets pumped with new commands via other processes (e.g. me -o foo.c) so if you swap to this buffer you will see that it simply lists the commands to be run. The last command will typically be '2 popup-window' which means popup the frame. On a console version of ME there is not a lot ME can do to achieve this, however there probably is on an X-Term version but the meFrameXTermMakeCur function in unixterm.c is some what lacking. Hopefully we can address this for the release.
            >
            >
            >>BTW, I personally prefer that ME does a vertical split instead of a
            >>horizontal split when the server opens the new file. Can someone tell
            >>me which entry in the emf files I have to modify to do this?
            >
            >
            > The macro file you need to play with is meserver.emf, I would suggest adding a vertical split to just before the window-popup if there's only one window.
            >

            Attached is a solution. Copy this file to your user
            directory and it will shaddow the released file
            and will be executed in preference. The split is
            only performed if this is the ONLY window.

            Jon.
          • first last
            What about opening a new selected buffer without splitting with a new window? I have been trying to do it myself but the ME macro language is completely alien
            Message 5 of 6 , Feb 18, 2004
            • 0 Attachment
              What about opening a new selected buffer without splitting with a new
              window? I have been trying to do it myself but the ME macro language is
              completely alien to me. Could the no split/horizontal split/vertical
              split be chosen in the configuration menu?

              Is there any tutorial or easy way to learn it? I want to do a "auto
              complete" (kinda hippie expand but instead of looking back it looks
              inside the syntax highlight file for expansion words).

              If I get this right, the next step is to be able to read trough
              library/included files (initially PHP) to enable auto completion of
              function/methods in included libraries.

              After testing Eclipse I find myself really missing that feature.

              Gabriel

              --- Jon Green <jon@...> wrote:
              ---------------------------------
              Phillips, Steven wrote:
              >
              >>-----Original Message-----
              >>From: salmankhilji [mailto:salmankhilji@...]
              >>Sent: 14 February 2004 20:17
              >>To: jasspa@yahoogroups.com
              >>Subject: [jasspa] enhancement to ME 04
              >>
              >>
              >>I have finally upgraded to 04 RC4 release on Linux.
              >>
              >>I am using the ME Server feature where in KDE File Manager I double
              >>click on a file and have an existing instance of ME open the file up.
              >> The problem is that once this happens, ME does not come to the
              >>foreground.
              >>
              >>After I double-clicked on the file, for a moment I thought that
              >>nothing had happened. So I tried again. When nothing happened the
              >>second time, then it came back to my mind that oh---I have enabled
              the
              >>server feature and should bring the window to foreground manually.
              >>
              >>I think from a users point of view, ME should automatically bring
              >>itself to foreground when the server launches the file.
              >
              >
              > This is how it is supposed to work and how it does work on windows.
              The server works via a *server* buffer which effectively gets pumped
              with new commands via other processes (e.g. me -o foo.c) so if you swap
              to this buffer you will see that it simply lists the commands to be
              run. The last command will typically be '2 popup-window' which means
              popup the frame. On a console version of ME there is not a lot ME can
              do to achieve this, however there probably is on an X-Term version but
              the meFrameXTermMakeCur function in unixterm.c is some what lacking.
              Hopefully we can address this for the release.
              >
              >
              >>BTW, I personally prefer that ME does a vertical split instead of a
              >>horizontal split when the server opens the new file. Can someone
              tell
              >>me which entry in the emf files I have to modify to do this?
              >
              >
              > The macro file you need to play with is meserver.emf, I would suggest
              adding a vertical split to just before the window-popup if there's only
              one window.
              >

              Attached is a solution. Copy this file to your user
              directory and it will shaddow the released file
              and will be executed in preference. The split is
              only performed if this is the ONLY window.

              Jon.



              __________________________________________________________________________

              This is an unmoderated list. JASSPA is not responsible for the content
              of
              any material posted to this list.

              To unsubscribe, send a mail message to

              mailto:jasspa-unsubscribe@yahoogroups.com

              or visit http://groups.yahoo.com/group/jasspa and
              modify your account settings manually.






              ---------------------------------
              Yahoo! Groups Links

              To visit your group on the web, go to:
              http://groups.yahoo.com/group/jasspa/

              To unsubscribe from this group, send an email to:
              jasspa-unsubscribe@yahoogroups.com

              Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
              > ; -!- emf -!-
              > ; This is part of the JASSPA MicroEmacs macro files
              > ; Copyright (C) 1998-2004 JASSPA (www.jasspa.com)
              > ; See the file me.emf for copying and conditions.
              > ;
              > ; Created: Thu Dec 31 1998
              > ; Synopsis: Server input handling routines.
              > ; Authors: steven phillips
              > ;
              > 0 define-macro server-input
              > goto-alpha-mark "I"
              > !if &equ $window-line :last-line
              > !return
              > !endif
              > set-variable #l0 $window-line
              > set-variable #l1 $buffer-bname
              > goto-line :last-line
              > !while &gre #l0 $window-line
              > set-variable #l5 &add $window-line 1
              > !if &seq @wc "C"
              > set-variable #l2 &lget &rig @wl 1 1
              > set-variable #l3 &rig @wl &add 3 &len #l2
              > !if ¬ &lfind :client-list #l2
              > set-variable :client-list &lin :client-list -1 #l2
              > set-variable &ind &spr ":%s-buffer" #l2 ""
              > !endif
              > ; Make a vertical window.
              > set-variable #l8 $window-id
              > set-position "\x90"
              > next-window
              > !if &equ #l8 $window-id
              > !force split-window-horizontally
              > !endif
              > goto-position "\x90"
              > ;
              > popup-window ""
              > set-variable #l4 &ind &spr ":%s-buffer" #l2
              > !if ¬ &seq #l4 ""
              > !force 0 find-buffer #l4
              > !endif
              > !force execute-line #l3
              > !if ¬ &seq $buffer-bname #l1
              > set-variable #l4 $buffer-bname
              > popup-window #l1
              > set-variable &ind &spr ":%s-buffer" #l2 #l4
              > !endif
              > !endif
              > goto-line #l5
              > !done
              > goto-alpha-mark "I"
              > set-variable :last-line $window-line
              > !emacro
              >

              ________________________________________________________________________
              Yahoo! Messenger - Communicate instantly..."Ping"
              your friends today! Download Messenger Now
              http://uk.messenger.yahoo.com/download/index.html
            • Jon Green
              ... I guess it could be, a good suggestion. ... Not at the moment - are considering it. Everything is documented, there just is not a nice introduction to get
              Message 6 of 6 , Feb 18, 2004
              • 0 Attachment
                first last wrote:

                > What about opening a new selected buffer without splitting with a new
                > window? I have been trying to do it myself but the ME macro language is
                > completely alien to me. Could the no split/horizontal split/vertical
                > split be chosen in the configuration menu?

                I guess it could be, a good suggestion.

                >
                > Is there any tutorial or easy way to learn it? I want to do a "auto
                > complete" (kinda hippie expand but instead of looking back it looks
                > inside the syntax highlight file for expansion words).

                Not at the moment - are considering it. Everything
                is documented, there just is not a nice introduction
                to get you going.

                >
                > If I get this right, the next step is to be able to read trough
                > library/included files (initially PHP) to enable auto completion of
                > function/methods in included libraries.

                You can define a "php-expand-abbrev" macro in your
                "myphp.emf" file to do the expansion, this is then
                used as part of the abbreviation expansion. There is
                an example of a private expander in "hkemf.emf".

                >
                > After testing Eclipse I find myself really missing that feature.
                >
                > Gabriel
                >
              Your message has been successfully submitted and would be delivered to recipients shortly.