Re: general questions/problems
- FBSD4/latest ME.
> 1. how can you bind C-@?ok, thanks.
> i tried "\x00" "0x00" "C-@" "C- " "C-space"
> etc, and none works ...
> (search for $recent-keys).
> 2. i think if OVERWRITE mode is ON, rectangle blocksetc) but
> should "paste" OVER text ... as of now it appears
> ME just "inserts" blocks regardless of OVERWRITE mode.
> This is not a common way of doing things (Emacs, MicroEMACS, Word
> could be implemented in a macro using @y. But there are issues whenthe yank
> buffer contains a new-line char ('\n'), typically these areinserted, if so
> what happens to any remaining chars on the original line?? etc.For example, given the following yank buffer:
World and all that"
And the following buffer with the cursor at the '^'
This is the ^ point of
The following are all legitimate results from an overwrite yank:
This is the Hello
World and all thatt of
This is the Hello
World and all that
This is the Hello
World and all that
> So how this would behave is fair less well defined hence thestandard of
> inserting blocks (I think I would favour the middle result but muchprefer
> the simple insertion as I know what I'm going to get).i think it should end up as (as in Qedit 3.0 and Joe 2.8):
This is the Hello point of
insertion World and all that
pastes after EOL's should have spaces inserted.
rectangular selections should have all newlines stripped.
it should be treated like a rectangle block
being dropped into a grid.
> 3. is there a way to insert "literal" control chars?ok, i'll try it thanks.
> ie, instead of ^B, i'd like a smilie face,
> instead of ^F, i'd like to see a diamond.
> normal PC charset.
> set-char-mask "dp" "\CB\CF"
> 4. is there a limit on keybindings? i have over a 100that goes
> and although i haven't tracked the problem down
> specifically, certain bindings seems to disappear
> when i add more, and they come back when i reduce the
> amount. there is no consistency in regards to the order
> so it will take me a while to figure out what is going on.
> Yes there is a limit, 384, there are a 181 burnt in default ones,
> up to 209 when me.emf is run and when I use ME a further 34 areadded (due
> to the mouse and MSShift support etc - I only add 4 of my ownbindings)
> getting the total to 243, leaving ~140 left.odd keys
> So the question has to be why are you using so many? With only 50
> on a keyboard this is like adding 2 new prefixes and binding everykey on
> the keyboard to it. It suggest to me that you are completelyreconfiguring
> the key-bindings in which case you should unbind the ones you don'twant
> first (use '-1 global-unbind-key "y"' to unbind the lot or use '0all
> global-unbind-key "esc"' etc to get rid of the main prefix keys and
> their bindings).i have that many bindings because like like to complement my CTRL
bindings with ESC in case i am on a tty that "eats" some CTRL chars.
i do unbind all initial bindings as described. the problem was
with binding "esc g" to "abort" - that causes problems and i
have a me.emf file that will prove it.
> 5. is there a way to keep the *scratch* buffer from appearing?(see docs
> if i want a scratch buffer, i can make one and it's kind of
> annoying to always have "*scratch*" in my buffers when i
> never wanted it or asked for one. it's just always
> nagging to be deleted. i thought of using hooks, and
> deleting "*scratch*" when a hook executes, but that seems
> kinda dirty, since it will end up trying to delete "*scratch*"
> even though it will be gone after the first delete.
> Or define a start-up macro to delete the initial *scratch* buffer
> on start-up) - ME must have at least one buffer so when you deletethe last
> buffer the *scratch* buffer will be created again, I don't see a wayaround
> this.if no files are given as arguments, *scratch* pops up as the default
otherwise it does not pop up ... that would seem like a nice way,
> 6. is there a way to detect if a mark is set? i want to markproblem
> an entire buffer if it is unset, and leave it set if it is.
> ... for use in user-defined macros.
> define-macro Test-mark
> !force exchange-point-and-mark
> !if $status
> ml-write "Mark is set"
> ml-write "Mark is not set"
> I can't stop the 'not set' case from ringing the bell - not such a
> if you use quiet mode. I will fix this.thanks :) i will try it :)
> 7. i think this is a known bug - the rectangle highlightingthis, I
> still highlights in line mode, not block mode. it is functional
> in rectangle modes however, just not the marking. how about
> a mark highlights rectangularly if the 1st key is left/right
> and not if the 1st key after a set-mark is up/down?
> or a rectangle "mode" as in wrap/overwrite/etc...
> I don't think that rectangle regions are used enough to warrant
> certainly don't want to have to move the cursor down to get thenormal
> region hilight.left-to-right selections are the same in rectangle and line modes ...
> If the cursor moving region hilight does not do thefeature. ME is
> rectangle region then the only time it would be used is on the
> yank-rectangle command and thats a lot of code for one minor
> a careful balance between power and size, we have added the abilityto do
> rectangle regions but I don't think the hilighting of the region canbe
> justified, sorry.ok :)
> 8. "quote" should allow decimal/hex numbers, not justok :)
> literal keystrokes ... ? i'd like to be able to generate
> any ascii char, not just typable ones.
> A simple macro could be written to do this.
> 9. looking forward to a system() macro that throws ME into thesystem so
> background allowing an interactive program to be used
> (such as Ispell for example) on ME buffer data.
> The filter-buffer command should be able to do this as it uses
> there is nothing to stop the command being run from opening a windowetc.
well - filter-buffer jsut dumps stdout to a buffer, i am askingF
how to spawn an interactive program from "me". one requiring
user input, one that doesn't dump stdout to a buffer, but
merely spawns a process. and when the process exits,
"me" returns to the foreground.
> great editor!i don't just like it - it's really all there is.
> Glad you like it,
what else is there? vim? kinda big, kinda crazy.
emacs? way too big. there simply is *NO* otherF
editor with termcap based syntax highlighting
of reasonable size (small enough to fit on a floppy).