Can I prevent from quiting gvim when click the close bottom on title bar?
anhnmncb
bottom, can I configure it from inside gvim?
--
Regards,
anhnmncb
gpg key: 44A31344
Tony Mechelynck
> I'm on windows, so I can't configure the behavior of titlebar close
> bottom, can I configure it from inside gvim?
I don't think you can. Inside gvim, you should teach yourself to quit by
means of ":q" or ":qa" (which will refuse to quit if there is a
'modified' file), or ":x" or ":xa" (which will write modified files to
disk, unless they have [No Name])
This assumes 'autowriteall' is not set. If it is set, ":q" behaves like
":x".
Best regards,
Tony.
--
FIRST HEAD: Oh! quick! get the sword out I want to cut his head off.
THIRD HEAD: Oh, cut your own head off.
SECOND HEAD: Yes - do us all a favour.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
anhnmncb
file has saved.
anhnmncb
buffers have saved.
Actually, I want map it to a key, so when I'm away, I can call it to
prevent someone from closing my gvim by accident.
I know mksession is a better solution, but I still want a function like
that :)
Tony Mechelynck
> Yes, I still want to have a function that can let me confirm when quiting even all
> buffers have saved.
>
> Actually, I want map it to a key, so when I'm away, I can call it to
> prevent someone from closing my gvim by accident.
>
> I know mksession is a better solution, but I still want a function like
> that :)
hm, can't you lock your screensaver (or something) so that when you've
been away, you must type your password before you can use the computer?
Then other people could do nothing "by accident", except of course pull
the AC plug from the wall, but I guess you can't forbid that (except
maybe by locking the door to the room with your computer). ;-)
anhnmncb
touch my gvim :)
Tony Mechelynck
Hm, then I think you have a problem.
Maybe you should create distinct usernames (login names) so that each
user won't clobber the others' work. But I suppose you'll tell me that
that isn't what you want either.
Best regards,
Tony.
--
A Plan for the Improvement of English Spelling
by Mark Twain
For example, in Year 1 that useless letter "c" would be dropped
to be replased either by "k" or "s", and likewise "x" would no longer
be part of the alphabet. The only kase in which "c" would be retained
would be the "ch" formation, which will be dealt with later. Year 2
might reform "w" spelling, so that "which" and "one" would take the
same konsonant, wile Year 3 might well abolish "y" replasing it with
"i" and Iear 4 might fiks the "g/j" anomali wonse and for all.
Jenerally, then, the improvement would kontinue iear bai iear
with Iear 5 doing awai with useless double konsonants, and Iears 6-12
or so modifaiing vowlz and the rimeining voist and unvoist konsonants.
Bai Iear 15 or sou, it wud fainali bi posibl tu meik ius ov thi
ridandant letez "c", "y" and "x" -- bai now jast a memori in the maindz
ov ould doderez -- tu riplais "ch", "sh", and "th" rispektivli.
Fainali, xen, aafte sam 20 iers ov orxogrefkl riform, wi wud
hev a lojikl, kohirnt speling in ius xrewawt xe Ingliy-spiking werld.
anhnmncb
> On 24/11/08 08:42, anhnmncb wrote:
>> Tony Mechelynck<antoine.m...@gmail.com> writes:
>>
>>> On 24/11/08 05:32, anhnmncb wrote:
>>>> Yes, I still want to have a function that can let me confirm when quiting even all
>>>> buffers have saved.
>>>>
>>>> Actually, I want map it to a key, so when I'm away, I can call it to
>>>> prevent someone from closing my gvim by accident.
>>>>
>>>> I know mksession is a better solution, but I still want a function like
>>>> that :)
>>> hm, can't you lock your screensaver (or something) so that when you've
>>> been away, you must type your password before you can use the computer?
>>> Then other people could do nothing "by accident", except of course pull
>>> the AC plug from the wall, but I guess you can't forbid that (except
>>> maybe by locking the door to the room with your computer). ;-)
>>
>> Haha~ But I want other people can use my computer, just not let them
>> touch my gvim :)
>>
>>>
>>
>
> Hm, then I think you have a problem.
>
> Maybe you should create distinct usernames (login names) so that each
> user won't clobber the others' work. But I suppose you'll tell me that
> that isn't what you want either.
right, I know this way, but not what I want either :)
>
>
> Best regards,
> Tony.
Teemu Likonen
> Haha~ But I want other people can use my computer, just not let them
> touch my gvim :)
You seem to have written similar request for GNU Emacs developers two
days ago:
http://article.gmane.org/gmane.emacs.devel/105936
It makes me wonder what other applications you would like to prevent
others from touching. :-) I don't need the answer, but from my
experience applications don't usually provide such features. The desktop
session in general can be locked, as Tony suggested. In Linux and Unix
environments it's also possible to lock a text terminal session,
including one launched under a graphical desktop environment.
anhnmncb
(let ((inhibit-quit t))
I don't know if gvim has something like this?
Actually, I live most time on gvim (emacs just does email stuff :), so my
request is just for them.
Teemu Likonen
> Yes, but I find the anwser for emacs:
>
> (let ((inhibit-quit t))
>
> I don't know if gvim has something like this?
The syntax for setting this variable in Emacs Lisp is one of these:
(setq inhibit-quit t)
(set 'inhibit-quit t)
The "let" form only binds local variables which are available only
within that particular form: (let (BINDINGS...) FORMS...)
But are you sure that inhibit-quit does what you need? It is about C-g
(keyboard-quit) which quits an Emacs command. It's not about quitting
the whole Emacs (nor Gnus) session.
Sorry for being off-topic but you also asked if gvim has "something like
this" so this is pretty confusing.
anhnmncb
too when click close bottom, nevermind.
Seems you familiar with elisp a bit :)
Ben Schmidt
> Yes, I still want to have a function that can let me confirm when quiting even all
> buffers have saved.
>
> Actually, I want map it to a key, so when I'm away, I can call it to
> prevent someone from closing my gvim by accident.
>
> I know mksession is a better solution, but I still want a function like
> that :)
I think the only way you could do it would be to compile your own Vim
and make some changes to the source code to disable or ignore the close
button. It's quite probably not hard--just have to find the spot where
the close event is handled and ignore it instead, so the close button
does nothing. Then always quit Vim using :q or the menus. So if you
really want this feature, I'd say that's the way to go.
Ben.
anhnmncb
>
> Ben.
Tony Mechelynck
I suspect that in that case the OS might (like mine does) pop an alert:
Program "gvim" is not responding. Do you want to terminate it?
[[ Terminate ]] [ Continue ]
giving the option to the user to _kill_ gvim. All unsaved data will be
lost, the viminfo won't be saved, etc.
Best regards,
Tony.
--
Issawi's Laws of Progress:
The Course of Progress:
Most things get steadily worse.
The Path of Progress:
A shortcut is the longest distance between two points.
John Beckett
> Ben Schmidt <BEN'S FULL EMAIL ADDRESS> writes:
While I am in mother-mode, what do people think about quoting email addresses?
I know that I can't hide my address when sending mail, but why tempt fate? Most
people manage to reply without quoting addresses, and that makes sense to me.
John
Matt Wozniski
Not terribly on-topic, but... I intentionally snip them. On the
cygwin mailing lists, you're likely to get many nasty flames for doing
anything else.
~Matt
anhnmncb
no time to see how to configure it ...
Tony Mechelynck
Mine (SeaMonkey) doesn't quote the email address by default. I think I
could find where to add it if I tried, but why bother? (And I believe
Thunderbird does the same. FYI, SeaMonkey and Thunderbird are not only
open-source and free-software but also cross-platform, maybe not as much
as Vim but certainly more than Emacs.)
Best regards,
Tony.
--
Microsoft's definition of a boolean: TRUE, FALSE, MAYBE
"Embrace and extend"...?
Teemu Likonen
> "John Beckett" writes:
>> While I am in mother-mode, what do people think about quoting email
>> addresses?
> Don't blame me, that's my mail client setting(emacs' gnus), and I have
> no time to see how to configure it ...
If you want just an attribution like "[person] wrote:" where [person] is
the user name (or if it isn't defined then her email address) then add
to following lines to your Gnus' init file (.gnus.el):
(setq message-citation-line-function 'my-message-insert-citation-line)
(defun my-message-insert-citation-line ()
"Insert citation line (attribution) to message.
This function inserts attribution line to the beginning of quoted
message."
(when message-reply-headers
(let* ((fullname (cdr (mail-header-parse-address
(mail-header-from message-reply-headers))))
(address (car (mail-header-parse-address
(mail-header-from message-reply-headers))))
(name (cond (fullname) (address) (t "Anonymous"))))
(insert (format "%s wrote:" name))
(newline 2))))
You can evaluate the code for your current Emacs session with "M-x
eval-region" when the code is inside a region.
Here's the code I use; it insert also international date string:
(setq message-citation-line-function 'my-message-insert-citation-line)
(defun my-message-insert-citation-line ()
"Insert citation line (attribution) to message.
This function inserts attribution line to the beginning of quoted
message."
(when message-reply-headers
(let* ((fullname (cdr (mail-header-parse-address
(mail-header-from message-reply-headers))))
(address (car (mail-header-parse-address
(mail-header-from message-reply-headers))))
(name (cond (fullname) (address) (t "Anonymous")))
(citation-date-list (parse-time-string
(mail-header-date message-reply-headers)))
(year (nth 5 citation-date-list))
(month (nth 4 citation-date-list))
(day (nth 3 citation-date-list))
(hour (nth 2 citation-date-list))
(min (nth 1 citation-date-list))
(timezone-min-total (/ (nth 8 citation-date-list) 60))
(timezone-hour (/ timezone-min-total 60))
(timezone-min (% (abs timezone-min-total) 60))
(timezone (format "%+2.2d%2.2d"
timezone-hour timezone-min)))
(insert (format "%s (%4.4d-%2.2d-%2.2d %2.2d:%2.2d %s) wrote:"
name year month day hour min timezone))
(newline 2))))
Teemu Likonen
> Don't blame me, that's my mail client setting(emacs' gnus), and I have
> no time to see how to configure it ...
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (windows-nt)
I see you are using Gnus 5.13, newer than my 5.11. If I remember
correctly in 5.13 version it's also possible to customize the
attribution line with %-type format strings. It's probably here:
M-x customize-group RET message-insertion RET
(With Gnus you should be able to just mouse-click on the above line.)
Raúl Núñez
On Tue, 25 Nov 2008 15:38:13 +0800, anhnmncb dixit:
> "John Beckett" writes:
> > I know that I can't hide my address when sending mail, but why
> > tempt fate? Most people manage to reply without quoting addresses,
> > and that makes sense to me.
>
> Don't blame me, that's my mail client setting(emacs' gnus), and I have
> no time to see how to configure it ...
But surely you have time to manually delete the email addresses, so
please do it ;)
Raúl "DervishD" Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
We are waiting for 13 Feb 2009 23:31:30 +0000 ...
anhnmncb
>
>
Ben Schmidt
> anhnmncb wrote:
>> Ben Schmidt <BEN'S FULL EMAIL ADDRESS> writes:
>
> While I am in mother-mode, what do people think about quoting email addresses?
I don't think it matters. The web interface mangles them when it
displays them anyway.
Though I prefer real names. How on earth am I to interpret anhnmncb?!
Ben.
Ben Schmidt
>> and make some changes to the source code to disable or ignore the close
>> button. It's quite probably not hard--just have to find the spot where
>> the close event is handled and ignore it instead, so the close button
>> does nothing. Then always quit Vim using :q or the menus. So if you
>> really want this feature, I'd say that's the way to go.
>>
>> Ben.
>
> I suspect that in that case the OS might (like mine does) pop an alert:
>
> Program "gvim" is not responding. Do you want to terminate it?
No, I don't mean for Vim to ignore a request from the OS to quit, such
as at shutdown time, but ignore the pressing of the close box widget;
and when I say ignore, I don't mean that from the OS' point of view.
Rather, it should accept the message like normal and just not do the
traditional window-closing thing on receiving it, but rather, just
discard it, similar to what happens if you click the button and get a
Save Changes dialog to which you reply 'Cancel', except without the need
to actually press 'Cancel'.
It should definitely respond as usual to a quit request, or yes, it
would become dangerous. But having a different behaviour for pressing
the close box widget is harmless.
Cheers,
Ben.
John Beckett
>>> Ben Schmidt <BEN'S FULL EMAIL ADDRESS> writes:
>>
>> While I am in mother-mode, what do people think about
>> quoting email addresses?
>
> I don't think it matters. The web interface mangles them
> when it displays them anyway.
I can live with top posting, but I am irritated by the lazy quoting of full email
addresses. It's just so pointless and naive.
What you say (that the web interface mangles addresses) may be true, but:
1. All these messages are archived in a few different places (I don't know how it
happens, but I've noticed this a few times when using Google).
2. Rarely, someone will quote a message in a blog or whatever. The quote will
probably include the full address if it was in the original.
3. Who knows what spammers will turn to next. Extrapolating from past behaviour,
it's inevitable that more serious harvesting of mailing lists will occur.
While it's impossible to protect your email address if you post to a public mailing
list, there is absolutely no reason to quote an address when replying.
John
Teemu Likonen
> SeaMonkey and Thunderbird are not only open-source and free-software
> but also cross-platform, maybe not as much as Vim but certainly more
> than Emacs.)
Your knowledge about different platforms is likely greater than mine and
I'm curious about this question of "being more cross-platform". How is
it measured in the open-source world? Is it about supporting different
operating systems? Or about different CPU architectures? Or officially
distributing more different ready-to-run builds?
Let's take SeaMonkey, Vim and Emacs as an example. First about CPU
architectures, Debian GNU/Linux builds and officially distributes all of
them for 12 different architectures:
alpha amd64 arm armel hppa i386 ia64 mips mipsel powerpc s390 sparc
Regardless of the architecture these are all Debian GNU/Linux systems so
I guess it counts as a single operating system. (SeaMonkey is called
Iceape in Debian.)
From the projects' web sites I gathered the following information. I'm
not sure how to compare them but it looks like they are all pretty well
cross-platform.
SeaMonkey
=========
http://www.seamonkey-project.org/releases/
Official builds:
Windows (32bit)
Mac OS X
Linux (x86)
Unofficial builds:
Linux/x86_64 [only a different architecture]
OS/2
Solaris 10 (SPARC)
AIX 5L
Also, a quote from Wikipedia:
Unofficial ports exist for FreeBSD, OpenBSD, NetBSD, IRIX, OS/2,
Solaris and BeOS / magnussoft ZETA.
http://en.wikipedia.org/wiki/SeaMonkey#Portability
Vim
===
http://www.vim.org/download.php
Systems:
Unix
MS-DOS
MS-Windows
Amiga
OS/2
Macintosh
QNX
Agenda
Sharp Zaurus
HP Jornada
MS-Windows CE
Compaq Tru64 Unix on Alpha
Open VMS
RISC OS
MorphOS
[Cygwin (console)]
[Cygwin (with GTK GUI)]
Emacs
=====
http://www.gnu.org/software/emacs/#Platforms
Supported platforms:
GNU/Linux
FreeBSD
AIX 4.3.3 and higher
Mac OS X
MS DOS
MS Windows
NetBSD
OpenBSD
Solaris
SunOS
Ultrix
Berkeley Unix (BSD) 4.1-4.4
Esix
Microport
SCO Unix
System V releases 0 to 4.0.4
Uniplus 5.2
Xenix
Andy Wokula
> Ben Schmidt <mail_ben...@yahoo.com.au> writes:
>
>> anhnmncb wrote:
>>> Yes, I still want to have a function that can let me confirm when quiting even all
>>> buffers have saved.
>>>
>>> Actually, I want map it to a key, so when I'm away, I can call it to
>>> prevent someone from closing my gvim by accident.
>>>
>>> I know mksession is a better solution, but I still want a function like
>>> that :)
>> I think the only way you could do it would be to compile your own Vim
>> and make some changes to the source code to disable or ignore the close
>> button. It's quite probably not hard--just have to find the spot where
>> the close event is handled and ignore it instead, so the close button
>> does nothing. Then always quit Vim using :q or the menus. So if you
>> really want this feature, I'd say that's the way to go.
>
> ok.. I think I should give up
that is too early
>> because I know nothing about C. Thank you :)
>
>> Ben.
you can check out vimtweak
http://vim.sourceforge.net/scripts/script.php?script_id=687
the following command hides the title bar, thus it cannot be clicked by
accident:
:call libcallnr("vimtweak.dll", "EnableCaption", 0)
--
Andy
anhnmncb
>
> anhnmncb schrieb:
>> Ben Schmidt writes:
>>
>>> anhnmncb wrote:
>>>> Yes, I still want to have a function that can let me confirm when quiting even all
>>>> buffers have saved.
>>>>
>>>> Actually, I want map it to a key, so when I'm away, I can call it to
>>>> prevent someone from closing my gvim by accident.
>>>>
>>>> I know mksession is a better solution, but I still want a function like
>>>> that :)
>>> I think the only way you could do it would be to compile your own Vim
>>> and make some changes to the source code to disable or ignore the close
>>> button. It's quite probably not hard--just have to find the spot where
>>> the close event is handled and ignore it instead, so the close button
>>> does nothing. Then always quit Vim using :q or the menus. So if you
>>> really want this feature, I'd say that's the way to go.
>>
>> ok.. I think I should give up
>
> that is too early
>
>>> because I know nothing about C. Thank you :)
>>
>>> Ben.
>
> you can check out vimtweak
> http://vim.sourceforge.net/scripts/script.php?script_id=687
Why does it not work here? windows 2000 sp4, have you tested?
Ben Schmidt
> Tony Mechelynck (2008-11-25 09:00 +0100) wrote:
>
>> SeaMonkey and Thunderbird are not only open-source and free-software
>> but also cross-platform, maybe not as much as Vim but certainly more
>> than Emacs.)
>
> Your knowledge about different platforms is likely greater than mine and
> I'm curious about this question of "being more cross-platform". How is
> it measured in the open-source world? Is it about supporting different
> operating systems? Or about different CPU architectures?
I think it's all of the above. But it's not about what you list on your
website: it's about what actually works. In effect, it becomes about
working on systems that are different enough to require programmer
effort, and within the context of the type of software being discussed.
It's about how many systems, out of all those in existence, the user can
compile and run the code on without having to know how to hack it.
I.e. For much software, different architectures are not an issue--you
just run it through a different compiler and it works. Though code that
relies on the endianness of the architecture will be less cross-platform
than code that doesn't. For things like compilers, many more aspects of
the architectures need to be considered!
Similarly, getting many things to work on an Amiga as well as Unix
requires a lot of effort, so that distinction needs to be considered
when evaluating 'cross-platform-ness'. But not necessarily for all code:
for a simple filter, the distinction simply may not be relevant.
> Or officially distributing more different ready-to-run builds?
I don't think it's that. It's a property of the codebase, not a measure
of the community's level of support for different systems.
> SeaMonkey
> =========
> Windows (32bit), Mac OS X, Linux (x86), Linux/x86_64, OS/2,
> Solaris 10 (SPARC), AIX 5L, FreeBSD, OpenBSD, NetBSD, IRIX,
> Solaris and BeOS / magnussoft ZETA
>
> Vim
> ===
> Unix, MS-DOS, MS-Windows, Amiga, OS/2, Macintosh, QNX, Agenda, Sharp Zaurus,
> HP Jornada, MS-Windows CE, Compaq Tru64 Unix on Alpha, Open VMS, RISC OS,
> MorphOS, Cygwin (console), Cygwin (with GTK GUI)
>
> Emacs
> =====
> GNU/Linux, FreeBSD, AIX 4.3.3 and higher, Mac OS X, MS DOS,
> MS Windows, NetBSD, OpenBSD, Solaris, SunOS, Ultrix,
> Berkeley Unix (BSD) 4.1-4.4, Esix, Microport, SCO Unix,
> System V releases 0 to 4.0.4, Uniplus 5.2, Xenix
So...how to compare? Well, Vim lists very broadly 'Unix', which quite
probably covers the BSDs, Solaris, System V, SCO, Linux, and others.
They're not different enough for Vim to list them separately. But notice
that Vim has Amiga and Macintosh which the others don't go near.
Seamonkey has BeOS which the others don't touch. Emacs probably works in
Cygwin, though it isn't listed separately, but doesn't go near OS/2.
You could get better lists to compare by going through each and if that
platform actually works for either of the other pieces of software,
adding it to their lists. It's not without difficulties, either, but it
would help.
Looking at the lists myself, and having a fairly limited knowledge of
OSes and architectures, I'd say to me it looks like Vim is most
cross-platform, followed a fair way behind by SeaMonkey, closely
followed by Emacs.
Ben.
anhnmncb
hmm, works when using ole version, thank you!
>
Tony Mechelynck
SeaMonkey's "MacOsX" distribution is a "Universal Binary" (including
separate machine code for both PPC and Intel Macs). Unlike Vim and Emacs
(both of which can run on a raw-text console), SeaMonkey is of course
GUI-only, which means some systems (such as MS-Dos) are irrelevant.
> Seamonkey has BeOS which the others don't touch. Emacs probably works in
> Cygwin, though it isn't listed separately, but doesn't go near OS/2.
>
> You could get better lists to compare by going through each and if that
> platform actually works for either of the other pieces of software,
> adding it to their lists. It's not without difficulties, either, but it
> would help.
>
> Looking at the lists myself, and having a fairly limited knowledge of
> OSes and architectures, I'd say to me it looks like Vim is most
> cross-platform, followed a fair way behind by SeaMonkey, closely
> followed by Emacs.
>
> Ben.
Best regards,
Tony.
--
Fuch's Warning:
If you actually look like your passport photo, you aren't well
enough to travel.