New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
caml.el #3055
Comments
Comment author: administrator
Je ne comprends pas bien. D'autre part, y a-t-il une facon sure de reproduire le probleme? Jacques Garrigue |
Comment author: administrator Date: Tue, 4 Dec 2001 04:38:23 +0100 (MET)
Maintenant, quel est l'intérêt de ça dans caml-abbrev-hook ? Je ne Bon, à lire le code (caml.el), caml-mode-abbrev-table n'est pas faite Disons que l'utilisateur ne doit pas faire d'abbrevs locales en mode Bruno. |
Original bug ID: 661
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Je propose ce mini-patch à caml.el, car chaque fois que je tape un
espace après _in en mode inferior-caml, ça bipe. Vu le test
(and cached-begin cached-end ...) juste en dessous, je suppose que
c'était l'intention originelle.
Bruno.
*** caml.el~ Thu Apr 26 11:33:48 2001
--- caml.el Wed Nov 28 17:37:01 2001
*** 925,932 ****
;;have to account for that possibility in comments.
(save-excursion
(let* ((cached-pos caml-last-noncomment-pos)
! (cached-begin (marker-position caml-last-comment-start))
! (cached-end (marker-position caml-last-comment-end)))
(cond
((and cached-begin cached-end
(< cached-begin (point)) (< (point) cached-end)) t)
--- 925,934 ----
;;have to account for that possibility in comments.
(save-excursion
(let* ((cached-pos caml-last-noncomment-pos)
! (cached-begin (and caml-last-comment-start
! (marker-position caml-last-comment-start)))
! (cached-end (and caml-last-comment-end
! (marker-position caml-last-comment-end))))
(cond
((and cached-begin cached-end
(< cached-begin (point)) (< (point) cached-end)) t)
Diff finished at Wed Nov 28 17:44:05
The text was updated successfully, but these errors were encountered: