June 2009 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [Fwd: footnote-init] 14 years, 10 months

Uwe Brauer

>>>>> "Andreas" == Andreas Röhler <andreas.roehler(a)easy-emacs.de> writes: > Hi Uwe, > have rewritten commented footnotes again, in order to make > its behaviour congruent to footnote.el > I.e. just go to the place where a fn should be inserted, then call the > command. > You will easily advice or change this to your needs if necessary. > It works now with tex and other languages. > Cheers > Andreas please have a look on the two examples I have attached in both cases fi-Footnote-add-footnote failed: one is with the numeric style the other with numeric-latin style. Sorry for all this hazzle. Uwe _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

2 participants
13 comments

[PATCH] Re: coding system oddity 14 years, 10 months

Aidan Kehoe

Ar an seachtú lá de mí Meitheamh, scríobh Stephen J. Turnbull: > Aidan Kehoe writes: > > Ar an seachtú lá de mí Meitheamh, scríobh Stephen J. Turnbull: > > > > Ben's original concept for the new detection mechanism was to assign > > > likelihoods and pick the best of the matching coding systems. > > > However, it's possible that there would be no match or a tie > > > (depending on how the algorithm is tuned), in which case it might be > > > natural for the result to be undecided. > > > > > > What do you think, Aidan? > > > It may be that coding_stream_detected_coding_system *should* never > > give undecided, even if no data have been seen, in which case the > > correct thing to do to fix this bug is to change > > coding_stream_detected_coding_system to do that. > > I guess it's fair to say your answer is "I'm not ready to say yet", then? ‘Yet’ is perhaps a bit strong. Ben might be able to answer the question, if he remembers. He may not, and he may not answer the question if we ask for reasons independent of that. If either of these is the case, the thing is unanswerable, and the decision as to the semantics of c_s_d_c_s is ours. > My personal take is that it is a good idea to allow c_s_d_c_s to > return undecided, because the final decision should be made at the > Lisp level, not in C. I think your fix is in the right place, even if > it's not the final version. > > > It may also be that undecided is a reasonable value there. It’s just > > not clear, and my patch as written is minimally invasive and fixes the > > issue. > > > Your warning below risks having people think that autodetection > > succeeding means that the characters in the buffer reflect what > > whoever wrote the octets to disk meant them to mean, which is not > > true, our autodetection gets things wrong all the time. > > That's always true, though. Ie, AFAIK currently autodetection will > always return a system that can save all the characters in the buffer > at the time, if it returns a coding system. No; this used to be especially not true. It’s less not true now, but it is still the case that the autodetection code may well return a coding system that will lose data if that coding system is used to decode and then encode the entire file. Consider that the UTF-8 coding systems used to lose data in this context all the time, despite that the autodetection code correctly recognised UTF-8; and that the ISO-2022-1 coding systems do not preserve some distinct error sequences on decoding followed by encoding. > [...] That's why I want the warning. OK; I disagree with you, but the downside from doing it your way is not that significant, let’s go with that. -- ¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir precipitadamente de la aldea por culpa de la escasez de rinocerontes? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

[PATCH] Re: coding system oddity 14 years, 10 months

Aidan Kehoe

Ar an seachtú lá de mí Meitheamh, scríobh Stephen J. Turnbull: > Aidan Kehoe writes: > > > + ;; If the file was zero-length, used-codesys is undecided. Set it to > > + ;; a more sane value. > > + (if (eq 'undecided (coding-system-type coding-system)) > > + (setq coding-system (default-value 'buffer-file-coding-system))) > > Ben's original concept for the new detection mechanism was to assign > likelihoods and pick the best of the matching coding systems. > However, it's possible that there would be no match or a tie > (depending on how the algorithm is tuned), in which case it might be > natural for the result to be undecided. > > While this is quite unsafe currently (since our coding systems > currently allow you to save in an incompatible coding system), > combined with appropriate checks at save time (which we need anyway), > a detection algorithm which produces 'undecided wouldn't be too bad. > > What do you think, Aidan? The coding system value in question is set in #'insert-file-contents-internal like so: if (!NILP (used_codesys)) { Fset (used_codesys, XCODING_SYSTEM_NAME (coding_stream_detected_coding_system (XLSTREAM (stream)))); } It may be that coding_stream_detected_coding_system *should* never give undecided, even if no data have been seen, in which case the correct thing to do to fix this bug is to change coding_stream_detected_coding_system to do that. It may also be that undecided is a reasonable value there. It’s just not clear, and my patch as written is minimally invasive and fixes the issue. Your warning below risks having people think that autodetection succeeding means that the characters in the buffer reflect what whoever wrote the octets to disk meant them to mean, which is not true, our autodetection gets things wrong all the time. > If that logic is reasonable, then changing the comment above to "Some > buffers may remain 'undecided (eg, zero-length files). Set it to a > more sane value." would be a good idea. > > If it isn't, the code should look like > > (when (eq 'undecided (coding-system-type coding-system)) > (unless (= 0 (buffer-size)) > (warn "Autodetection failed: setting to default.")) > (setq coding-system (default-value 'buffer-file-coding-system))) -- ¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir precipitadamente de la aldea por culpa de la escasez de rinocerontes? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

coding system oddity 14 years, 10 months

Richard

Hello, is this expected behaviour? Tested with 21.5.28 and 21.5.29 rm -f xx.txt; gnuclient xx.txt # -> coding system UTF8 rm -f xx.txt; touch xx.txt ;gnuclient xx.txt # -> coding system Auto/undecided rm -f xx.txt; echo " " >xx.txt ;gnuclient xx.txt # -> coding system UTF8 0-sized files are in my configuration always read with an Auto/undecided coding system. Worse yet, upon saving no sensible coding is selected - texts with accents or foreign chars get munged. My settings are this: custom.el: '(buffer-file-coding-system 'utf-8 t) '(buffer-file-coding-system-for-read 'utf-8 t) '(buffer-process-coding-system 'utf-8) '(default-buffer-file-coding-system 'utf-8 t) '(default-file-coding-system 'utf-8) '(edict-default-coding-system 'utf-8) '(file-coding-system 'utf-8 t) '(file-coding-system-for-read 'utf-8 t) init.el: (set-coding-priority-list '(utf-8)) (set-coding-category-system 'utf-8 'utf-8) (set-default-file-coding-system 'utf-8) (prefer-coding-system 'utf-8) (set-default-buffer-file-coding-system 'utf-8) (setq buffer-file-coding-system-for-read 'utf-8) In my (very) old .xemacs/init.el I also had an additional (set-default-coding-systems 'utf-8) which does no longer exist but apparently cured the problem. Afaicr 0-sized files caused me some coding system related trouble even in 21.4.8 which was fixed with the above setting. Regards Richard _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

3 participants
3 comments

Re: [Fwd: footnote-init] 14 years, 10 months

Uwe Brauer

>>>>> "Andreas" == Andreas Röhler <andreas.roehler(a)easy-emacs.de> writes: > Hi Uwe, > have rewritten commented footnotes again, in order to make > its behaviour congruent to footnote.el > I.e. just go to the place where a fn should be inserted, then call the > command. > You will easily advice or change this to your needs if necessary. > It works now with tex and other languages. Thanks again but there are some problems now. - I have (add-hook 'message-mode-hook 'turn-on-my-footnote-mode) but now when I tried to answer you mail I can't and the reason is the function turn-on-my-footnote-mode, I obtain a bugtrace which I attach. - more serious: it seems that there is a problem with the scanning of the regular expressions. I tried to use (fi-Footnote-add-commented-footnote) on the very same file footnote-init.el namely just before the line ;;; footnote-init.el ends but the footnote gets placed in strange place namely: then two footnotes get inserted one at the position I expect it the other in the fi-Footnote-add-commented-footnote after (setq footnote-section-tag (concat comment-start " Footnotes:"))) I presume he thinks that is the right place. Wouldn't it be better to have first end-of-buffer and then a backward search for this string! Like if on wants to update the Local Variables. I think another culprit is the line ;; (local-set-key [(control c) f31] 'footnote-delete-footnote) which also gets modified, since footnote-init thinks this is a footnote. To avoid this behaviour I changed the footnote-style to numeric-latin, but then when running footnote-init, xemacs seems to freeze. About the other problem I have with large latex/matlab file I write in the next message. Uwe _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: [Fwd: footnote-init] 14 years, 10 months

Uwe Brauer

Andreas Röhler wrote: > Hi Uwe, > > have rewritten commented footnotes again, in order to make > its behaviour congruent to footnote.el > I.e. just go to the place where a fn should be inserted, then call the > command. > You will easily advice or change this to your needs if necessary. > > It works now with tex and other languages. > > Cheers > > Andreas Hi Andreas, these are great news indeed. I found an error in the last version you released and will now check whether the error has gone away. thanks again for your effort!!! Uwe _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

1 participants
0 comments

[Fwd: footnote-init] 14 years, 10 months

Andreas Röhler

Hi Uwe, have rewritten commented footnotes again, in order to make its behaviour congruent to footnote.el I.e. just go to the place where a fn should be inserted, then call the command. You will easily advice or change this to your needs if necessary. It works now with tex and other languages. Cheers Andreas

1 participants
0 comments

Re: coding system oddity 14 years, 10 months

Stephen J. Turnbull

Richard Zidlicky writes: > On Fri, Jun 05, 2009 at 11:36:04AM +0900, Stephen J. Turnbull wrote: > > > If you don't mind explaining, how are you in this situation frequently > > enough to figure out what happened, let alone care? I don't think > > I've ever edited an existing file with zero-size. If there's a common > > workflow that leads to this, maybe there's more hurry than I thought. > > it is very common for me - I use gnuclient as editor for the mutt > email client. Whenever mutt is asked to compose a new message it > will call gnuclient with a zero-sized temporary file. Ah, that makes sense. All the tools I use that way (version control programs, mostly) initialize the file with some nonempty content. Eg, in the case of mail, I would expect the addressee and subject headers. I guess Mutt has different way of doing that, so the initial buffer is empty. > The temporary file must be created by mutt because otherwise it > would be hard to guarantee uniqueness - in principle other tools > calling an external editor on a newly created temporary file are > likely to hit the same bug. Actually, I think most tools simply use something like tempnam and let the editor create the file, but as that's insecure, I suppose more and more will be using mkstemp, which would have the effect you observe. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

2 participants
1 comments

Can't see help window until I select it 14 years, 10 months

David Karr

Sorry if this isn't the best place to ask this. Comp.emacs.xemacs doesn't seem very active. I installed the latest release of Cygwin and XEmacs on a new box a couple of days ago. I've got almost everything working the way I want it, with a couple of exceptions. When I do something that should show a "help" window, like "describe-function", the only indication I have that help has been presented is "Type q to remove help window, space to scroll the help" appearing in the status area. The help window does not appear. If I then do "switch-to-buffer", I see that the help window that I requested is at the top of the list, so I press Enter, and now I have my help window. What might I be missing that is preventing help windows from automatically presenting themselves in a convenient fashion? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

2 participants
5 comments

footnote-init: problems and suggestions (was: Local Variables: elementary question) 14 years, 10 months

Uwe Brauer

> Nice to hear. It was sent to emacs-devel that time, later the > assignment-question came across. > As its a bug-fix for XEmacs too, maybe it should be taken here. > Should be installed as a hook and always run first, if > footnode-mode is switched on. After a couple of days of testing I found 3 problems and have 2 suggestions. I will attach my setting below, but I turn on footnode-mode in several mayor modes, one of them LaTeX mode and so far the only problematic one. - when opening a typical latex file with all this headers etc footnote-mode is not on, although it should according to the hook setting. Not a big problem I just turn it on manually. - (Footnote-init is called by the footnote-mode-hook) so it runs when turning the mode on, however for some bizarre reason footnote-init gets the footstyle wrong. Although default is numeric[1] in latex mode footnote-init selects roman-upper. When I substitute \documentclass[12pt]{article} by \documentclass{article} and rerun footnote-init the style changes to english upper. So how can I set style correctly? Footnote-cyle-style does not help! - the undo function seems to confuse footnote. Suppose I want to insert a footnote but then call undo, the next time I call footnote-add-footnote the counter has proceed even if I call footnote-init before and this is odd since I thought this function would scan the buffer and set the counter accordingly, but no. - I find the following useful: insert-footnote, that is [2] will be changed to [2] this footenote will be inserted something of this sort. (defun my-insert-footnote () (interactive) (Footnote-delete-footnote nil) (yank 3)) or may be better to work with registers. - the other generalisation would be to insert footnotes with comment syntax, so something like having a (indent-for-comment) before inserting a footnote, which would lead to % [2] Uwe Brauer Footnotes: [1] which I prefer! %%Footnotes: %% [2] with comments Here is my setting (require 'footnote) ;(autoload 'footnote-mode "footnote" "" t) (defun turn-on-my-footnote-mode () (interactive) (footnote-mode nil)) (add-hook 'mail-mode-hook 'turn-on-my-footnote-mode) (add-hook 'message-mode-hook 'turn-on-my-footnote-mode) (add-hook 'matlab-mode-hook 'turn-on-my-footnote-mode) (add-hook 'LaTeX-mode-hook 'turn-on-my-footnote-mode) (add-hook 'text-mode-hook 'turn-on-my-footnote-mode) (add-hook 'emacs-lisp-mode 'turn-on-my-footnote-mode) (setq footnote-narrow-to-footnotes-when-editing t) ;does not work (defun my-set-footnote-keys () (interactive) (local-set-key [(control right)] 'Footnote-add-footnote) (local-set-key [(control c) right] 'Footnote-cycle-style) (local-set-key [(control c) left] 'footnote-init) (local-set-key [(control c) f31] 'footnote-delete-footnote) (local-set-key [(control f30)] 'Footnote-goto-footnote) (local-set-key [(control left)] 'Footnote-back-to-message)) (add-hook 'footnote-mode-hook 'my-set-footnote-keys) (add-hook 'footnote-mode-hook 'footnote-init) (defun my-set-footnote-style () (interactive) (Footnote-set-style 'numeric)) (add-hook 'footnote-mode-hook 'my-set-footnote-style);;[1] (setq footnote-prefix [(control c) (control n)]) (require 'footnote-init) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

2 participants
11 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta June 2009